Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
homakov
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
88 ms
·
931.
▲
by
homakov
13y ago
Vietnam and cambodia are just shit compared to thai.
932.
▲
by
homakov
13y ago
If you dont like sex tourism it is ur mental problem. Feel free to agitate in your europez but please leave my thailand as is. Every girl has a right to do anything and its not your business.
933.
▲
by
homakov
13y ago
Why pay you? Who needs weather info so much - nobody.
934.
▲
by
homakov
13y ago
> I reported a critical bug that affected millions of users > XSS lol
935.
▲
by
homakov
13y ago
As a bug hunter, I think initial problem is bullshit. There is NO POLICY about rewards in Yahoo. Nobody has right to "beg" a reward. Especially for "yet another XSS". Don't like the policy? Go sell that "XSS&qu
936.
▲
Traveling around the world for fun and profit
(egorhomakov.com)
1 points
by
homakov
13y ago
|
0 comments
937.
▲
by
homakov
13y ago
I dont understand what are you trying to say. I traveled around the world and had nonproblem consulting people meanwhile.
938.
▲
by
homakov
13y ago
read the black swan
939.
▲
by
homakov
13y ago
>Believe it, it's possible to not succeed yet want to succeed more than anyone else on the planet absolutely
940.
▲
by
homakov
13y ago
>Invest in me, not my ideas why is it any better just throwing money in a window
941.
▲
by
homakov
13y ago
Lol, i can just find route A to B and then B to C.
942.
▲
by
homakov
13y ago
taking into account fogginess of emails of the researcher and amount of emails FB whitehat receives daily... I am not surprised they said it's not a bug. PROTIP: Reports should have PoC and be concise. No information about your bachelo
943.
▲
by
homakov
13y ago
no, i was dismissed for some other reason. My emails (i reread them a while ago) explained perfectly where's the bug. On this topic: i still have no clue what vulnerability it was. Guy, do you know such terms XSS, CSRF etc? Can't
944.
▲
by
homakov
13y ago
"business" ? dubai ain't no fun
945.
▲
by
homakov
13y ago
ok it's nice but why?
946.
▲
by
homakov
13y ago
> set an iframe's src to "view-source: https://example.com/" , is it possible to frame view-source?
947.
▲
by
homakov
13y ago
also we need a reflector with 'value="' in the beginning https://twitter.com/homakov/status/364872768921165824/photo/...
948.
▲
by
homakov
13y ago
interesting point that CSRF tokens break caching. People can store it in cookie, and not put into the actual HTML.
949.
▲
by
homakov
13y ago
Your UPDATE is right, attacker can probe a..z 2 times, and just choose the letter that was compressed in both of them, ignoring random compressions
950.
▲
by
homakov
13y ago
you're right, also, to make compression work, ASDF is not enough, attacker needs https://domain.tld?q=value="ASDF
951.
▲
by
homakov
13y ago
Oracle padding
952.
▲
by
homakov
13y ago
>The solution is forced TLS with HSTS and includeSubdomains. that's true. Few questions: 1) does django provide HSTS header by default? didn't find it in codebase 2) does django has includeSubdomains? bitbucket doesn't hav
953.
▲
by
homakov
13y ago
hm, how can XSS on subdomain: "steal the session, preform a DoS using the size of the cookie"
954.
▲
by
homakov
13y ago
Offtopic: this is very simple mitigation for any website, requires JS: https://gist.github.com/homakov/6147227
955.
▲
by
homakov
13y ago
The parent said "as well" but I'm still insisting it referrer must not be neither a whole nor a part of CSRF protection.
956.
▲
by
homakov
13y ago
> but off the cuff I believe HSTS will prevent the browser from trusting a plaintext HTTP response at all Cookies are broken (i write about it on my blog like, daily). The essential idea of Forcing is injecting cookies into HTTPS space f
957.
▲
by
homakov
13y ago
> In any case that you can edit the CSRF token you already can execute a much stronger attack (MITM, XSS, etc). MITM is not a problem for HTTPS, but it can force cookies. Subdomain can do same thing. These preconditions are common
958.
▲
by
homakov
13y ago
1) simulate request to http(NOT SECURE)://site.com 2) simulate response with Set-Cookie: csrf_token=123123; > unless it's a subdomain in which you have the more serious issue of session theft or session fixation elaborate
959.
▲
by
homakov
13y ago
XSS? unrelated here I think. Exactly, cookie forcing/tossing = "set" their CSRF token
960.
▲
by
homakov
13y ago
bitbucket is vulnerable > django has a problem if it's not enough: some websites from http://www.djangosites.org/ are vulnerable > django has a problem
More ›