homakov

94 ms·

841.
Header injection in Sinatra/Rack(homakov.blogspot.com)
5 points by homakov 13y ago|0 comments
842.
by homakov 13y ago
You're welcome :)
843.
by homakov 13y ago
>I haven't taken a look at it, but would it make sense to add dynamic <original>.translate.googleusercontent.com subdomains for translated sites and add the base domain to the public suffix list? random hash as a sandbox.<h
844.
by homakov 13y ago
Nobody hires egor in fact. Not wow.
845.
by homakov 13y ago
Wow, Thanks!
846.
by homakov 13y ago
just homakov@gmail.com on coinbase
847.
by homakov 13y ago
No rewards
848.
by homakov 13y ago
Works in Chrome. Actual "bombing" works in FF too, but doesn't affect top-level domain. That's semi-solution. How is it going to help mysite.cdn.com/file1 to bomb mysite.cdn.com/other-files... Also look at tran
849.
by homakov 13y ago
Yes, now I see. Weird it stayed not fixed, Public suffix list is not implemented in Chrome. Anyway, the list is not even close to real solution (just had long discussion with @titanius on twitter why not). So many quirks and use cases of
850.
by homakov 13y ago
I read that post before, maybe I missed, but where he says about DoS possibilities of cookie tossing?
851.
Why you're likely vulnerable to open redirect.(homakov.blogspot.com)
3 points by homakov 13y ago|0 comments
852.
Using Content-Security-Policy for Evil(homakov.blogspot.com)
4 points by homakov 13y ago|0 comments
853.
by homakov 13y ago
Depends how 2FA is used. If on per/action basis it could save (you know the SID but don't know the OTP/token)
854.
by homakov 13y ago
Content-Security-Policy: can-set-cookies: no! BTW if JS is of we can use <meta http-equiv Set Cookie>
855.
by homakov 13y ago
Cookie tossing are not always helpful. If session is properly tied with csrf token there's not much you can do with it.
856.
by homakov 13y ago
No, not like this. You can block some path, but you cant set domain=dontlike.host.com; Only entire *.network.
857.
by homakov 13y ago
not amount, but total Length of the Cookie header. Otherwise number of cookies will be ~5. Yes I recall filldisk.com, but that one doesn't seem harmful to user (he knows where it comes from & exploit is quite slow). Cookie bomb can
858.
Account hijacking on MtGox(homakov.blogspot.com)
117 points by homakov 13y ago|37 comments
859.
///host.com or Evolution of Open Redirect Vulnerability(homakov.blogspot.com)
6 points by homakov 13y ago|0 comments
860.
Using Content-Security-Policy for Evil(homakov.blogspot.com)
5 points by homakov 13y ago|0 comments
861.
by homakov 13y ago
Condescending tone? Where omg
862.
by homakov 13y ago
How i belttile target and whats wrong with disclosure after paypal refuses to fix?
863.
Token Fixation in Paypal(homakov.blogspot.com)
3 points by homakov 13y ago|0 comments
864.
Path Encoding Vulnerability in https/www redirects(homakov.blogspot.com)
7 points by homakov 13y ago|0 comments
865.
by homakov 13y ago
it works of course, but to be compatible with many environments we need something more reliable than Referrer.
866.
by homakov 13y ago
This is joev's article. His explanations of the issue are better than mine ;)
867.
by homakov 13y ago
exactly. since normal script-tag cannot drop new X-Requested-With header, there's no need to add some "while(1)" things which look ugly. There's downside, though - you can't inspect JSONs by simply opening them in a
868.
by homakov 13y ago
my solution is request.xhr? check. the link above is only to explain what rails-bug was. I don't think checking referrer is a good idea there.
869.
by homakov 13y ago
it does, but it's worst workaround. we chose request.xhr? check
870.
by homakov 13y ago
bug doesn't exist anymore

More ›