Live data from Hacker News

Viewing profile — 0xad

0xad

HN member
Joined
Wed, May 09, 2018, 1:48 PM UTC
HN karma
73
Public activity
22 items

About 0xad

No profile information was provided.

Recent public activity

  1. comment
    Comment #49067212

    Yes, but (always but !) we also need to take into account what we're aiming at, which is an impact on stock performance. So the company needs to be (1) listed on a stock exchange a…

  2. comment
    Comment #49066271

    [flagged]

  3. story
  4. comment
    Comment #30538747

    If you don't see the difference between proprietatory format like docx and you argue that just because I add double-asterisk with a word in-between then suddenly it's not plain-tex…

  5. comment
    Comment #30538700

    I think it does. By transforming file Foo.docx into file Bar.b64 you get a plain-text file (Bar.b64) but Foo.docx still isn't plain-text. That's actually how email attachments work…

  6. comment
    Comment #30525630

    No. Open up a word document (.docx) in hex editor (head -80 foo.docx | xxd) and you'll see it's not a plain file on a binary level. Now do the same with any python, php, html, and …

  7. comment
    Comment #29263591

    Here's one: If you want your operations to be as easy as they can be (LAMP), go with PHP.

  8. comment
    Comment #26565597

    By original do you mean Hovav's? Then no, it's 2008. But I'd argue that Borrowed Code Chunks exploitation technique paper by stealth from 2005 is the original. But maybe I'm just t…

  9. comment
    Comment #25122805

    You can use grammarinator or any other of myriad grammar fuzzers BUT I'd start with radamsa and its string-related flags. Radamsa is _awesome_, you run it on an input and you get m…

  10. comment
    Comment #25024290

    OP here. I'm planning to do so, however it will require more work (better description of the problem, wider description of viable solutions, additional case studies). Most probably…

  11. comment
    Comment #25023609

    Yes you will, but only because GitHub already recognised this class of problems and came up with their own solution [1]. Bear in mind that it works only for vendors that integrated…

  12. comment
    Comment #25014435

    Hey, OP here. I agree that a blog post would be more readable. In this particular case I just didn't expect that it will catch fire. If I would then I would spend more time on the …

  13. comment
    Comment #25014424

    Cool! Thanks for explanation.

  14. comment
    Comment #25014411

    Greetings fellow Hackers! OP here. I see that my experiment got some traction which means more awareness should be spread about this class of bugs. For starters I recommend reading…

  15. comment
    Comment #25013876

    Awesome, thanks for the background information!

  16. comment
    Comment #25013839

    You mean adversaries? No. For token generation I used https://canarytokens.org/ so the only information I got was abou triggering the token, but not the context in which it was tri…

  17. comment
  18. story
  19. comment
    Comment #17866298

    What AFL needs is _instrumentation_ and of course the easiest way is to get that at compilation step, however you are not constrained by anything to get that part via other means. …

  20. comment
    Comment #17866283

    Great article. Kudos. On a side node, my old project https://github.com/dyjakan/interpreter-bugs along with short presentation I did on WarCon 2017 https://github.com/dyjakan/confe…

  21. comment
    Comment #17177656

    And of course also caused problems there. Check Project Zero advisories (iirc found by jhorn).

  22. story