Viewing profile — MajesticHobo2
MajesticHobo2
HN member- Joined
- Fri, Aug 10, 2018, 1:59 AM UTC
- HN karma
- 182
- Public activity
- 43 items
- HN profile
- View on Hacker News ↗
About MajesticHobo2
No profile information was provided.
Recent public activity
-
comment
Comment #48927590
Browser sandboxing is now fully solved.
-
comment
Comment #48740145
It's the same style I see on Twitter and LinkedIn a lot.
-
comment
Comment #48740102
Why does it have to be deliberate? It's not surprising that people exposed to output from LLMs will unconsciously pick up their linguistic habits.
-
comment
Comment #47943184
I'd say also add a test that shows the HTML injection (which spurred the PR) isn't possible. Given an attacker-controlled URL of: foo onclick the following shouldn't render: The fo…
-
comment
Comment #47580266
It was definitely partially about model quality. The frontier models are capable of producing valid findings with (reasonably) complex exploit chains on the first pass (or with lim…
-
comment
Comment #47579594
> With decompilation I think there's a higher risk of it missing the intention of the code. I'm not sure but suspect the lack of comments and documentation might be an advantage to…
-
comment
Comment #47579372
That was then, this is now. The new models are scarily good. If you're skeptical, just take an hour to replicate the strategy the article references. Point Claude at any open-sourc…
-
comment
Comment #46931232
Third or fourth, maybe, not first.
-
comment
Comment #46785535
Yes, but it would likely have to be chained with other bugs - at minimum, something that gives you an info leak.
-
comment
Comment #46548863
Yeah, somebody came up with one here: https://news.ycombinator.com/item?id=46469897
-
comment
Comment #46439902
It’s a phase 1 clinical trial designed only to assess safety and determine the appropriate dosage. Future trials will focus on efficacy.
-
comment
Comment #46320343
Wouldn't platforms see the supposed XSS payloads in their logs and publish analyses of them, or at the very least, announce that they happened?
-
comment
Comment #46186395
I'm sure they can store far more than 20 TB now, but it is true that the content pool is much larger. I would guess it's not a favorable ratio.
-
comment
Comment #45676276
Thanks for making this! I've been looking for something like this for a while.
-
comment
Comment #45041330
xxd IMGP0847.DNG | grep 03e400: 0003e400: ffd8 ffc3 000e 0e10 800c 5002 0011 0001 ..........P..... Look at the byte at offset 11 (0xb), it's there.
-
comment
Comment #45034939
Yes: dd status=none if=IMGP0847.DNG bs=1 skip=0x3e40b count=1 | xxd 00000000: 02
-
comment
Comment #45034861
You need to click the link that says "RAW (33.0MB)". The filename should be "IMGP0847.DNG".
-
comment
Comment #45029630
I AirDropped the PoC to my vulnerable iPhone. It didn't cause a crash until I tried to edit it in the Photos app.
-
comment
Comment #44904212
That's exactly why I don't agree that GETs should be broadly exempted from CSRF protections. I'm not talking about CORS at all.
-
comment
Comment #44892619
The problem boils down to the lack of equivalence between a site and an origin. The article explains how https://app.example.com and https://marketing.example.com may sit at very d…
-
comment
Comment #44892547
Not sure I agree with this part: > Allow all GET, HEAD, or OPTIONS requests. > These are safe methods, and are assumed not to change state at various layers of the stack already. P…
-
comment
Comment #44694779
XFF handling is the bug that keeps on giving. I'd estimate I've seen incorrect parsing of it in at least half of the web applications I've audited professionally. The funniest is w…
-
comment
Comment #44476732
You can use FTP and SVN.
-
comment
Comment #44185915
There doesn't need to be any kind of "polyglot payload". Local network services and devices that accept only simple HTTP requests are extremely common. The request will go through …
- story