| bio | website | inpursuitoflaziness.blogspot.… |
|---|---|---|
| location | Mumbai, India | |
| age | 19 | |
| visits | member for | 1 year, 3 months |
| seen | 52 mins ago | |
| stats | profile views | 50 |
I am an engineering student who loves the sciences, especially physics.
Security at the expense of usability, comes at the expense of security.
|
19h |
comment |
Known plaintext; What cipher is being used here? @TildalWave: Ah lol. I spend like 15 minutes on a JS console with this cipher. using ASCII as a base didn't work, neither did some other reshufflings. Then I have up :P |
|
19h |
comment |
Known plaintext; What cipher is being used here? @TildalWave: No, it need not be: Like I mentioned, it would have an extended charset. Until we have a notion of an assigned number for each letter and character, we don't know if there is a loop in the above example or not. |
|
1d |
awarded | Nice Answer |
|
2d |
comment |
Is cookie-based XSS exploitable? @AbsoluteERØ: Yes, but that involves a certain degree of stupidity on the victim's behalf. At one point security boild sown to the user, it's hard to make any efforts beyond that. |
|
May 19 |
answered | Is cookie-based XSS exploitable? |
|
May 19 |
comment |
Known plaintext; What cipher is being used here? Also, you have given two different outputs for the same http input |
|
May 19 |
comment |
Known plaintext; What cipher is being used here? It could be one of these with an extended charset. |
|
May 18 |
answered | Is it safer to store the XSRF value inside your JavaScript? |
|
May 18 |
comment |
How secure is using CRAM-MD5 for email authentication, when not using an SSL connection? @e-sushi: You're welcome! No need to apologize for not accepting all, we don't mind :D |
|
May 17 |
answered | How secure is using CRAM-MD5 for email authentication, when not using an SSL connection? |
|
May 15 |
answered | Password storing in Google Chrome content scripts |
|
May 14 |
comment |
CSRF protection with Session Id @ManRow: Hm, true. Still, TildalWave's note about session ids still holds. |
|
May 14 |
comment |
CSRF protection with Session Id @SébastienRenauld: How would you "load up a form"? Same origin policy makes sure that you don't GET x-site forms. |
|
May 14 |
comment |
CSRF protection with Session Id @SébastienRenauld: If someone is sniffing the request, they can just take the session cookie and be done with it. Why attempt CSRF when you have something better? |
|
May 14 |
comment |
CSRF protection with Session Id @TildalWave: Good point, added a note. |
|
May 14 |
revised |
CSRF protection with Session Id added 238 characters in body |
|
May 14 |
comment |
CSRF protection with Session Id @ManRow: I don't see anything wrong with that. |
|
May 14 |
answered | CSRF protection with Session Id |
|
May 14 |
comment |
CSRF protection with Session Id @D3C4FF: Doesn't matter. If your server accepts POST/GET requests without validating the request, it is vulnerable to CSRF. Servers don't care about javascript. |
|
May 14 |
answered | Why isn't open WiFi encrypted? |