Reputation
387
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 5 14
Impact
~48k people reached

  • 0 posts edited
  • 0 helpful flags
  • 11 votes cast
Jun
12
revised How secure is the SRP that Blizzard uses to protect passwords?
added 9 characters in body
May
26
comment Why don't major browsers currently support TLS above version 1.0?
bugzilla.mozilla.org/show_bug.cgi?id=480514#c86 2013-05-24 21:14:19 "Seems abandoned. Sad really." lol
May
24
comment Why don't wifi managers remember mac addresses for hotspots to defeat the jasager attack?
How about other managers?
May
22
comment How secure is the SRP that Blizzard uses to protect passwords?
@CodesInChaos that doesn't really matter in case of SRP - if you'll find discrete logarithm and find the password hash, you don't need the password anymore, you can use the hash to log in. If you can't find it, you have to calculate modpow() for each password and verifier which is slow enough.
May
22
answered How secure is the SRP that Blizzard uses to protect passwords?
Mar
28
comment Why don't wifi managers remember mac addresses for hotspots to defeat the jasager attack?
No wai under Windows?
Mar
28
comment Why don't wifi managers remember mac addresses for hotspots to defeat the jasager attack?
+1 to the question. Is there a way to connect to an AP with given SSID and MAC? E.g. if you have 2 APs with same SSID and want to be connected to one of them regardless to signal strength.
Mar
28
comment DNS Spoofing vs DNS Cache Poisoning
So is DNS spoofing a result and DNS poisoning - a way to the result?
Mar
27
comment Has the WPS brute-force cracking issue been fixed?
Thank for describing of WPS vulnerability.. oh wait, I already knew it! For some reasons, WPS bruteforce with reaver doesn't work for that people. Wonder why.
Mar
27
comment Has the WPS brute-force cracking issue been fixed?
What the heck? Who downwotes and why? No, I doesn't have a source, but people who hack WPS tell that newer devices are unhackable, that's why I ask.
Mar
27
asked Has the WPS brute-force cracking issue been fixed?
Mar
21
comment Why don't major browsers currently support TLS above version 1.0?
I've heard that Lucky13 was not fixed.
Mar
21
revised Why don't major browsers currently support TLS above version 1.0?
added 26 characters in body
Mar
21
comment Why don't major browsers currently support TLS above version 1.0?
See question update.
Mar
21
revised Why don't major browsers currently support TLS above version 1.0?
added 253 characters in body; edited title
Mar
21
comment Why don't major browsers currently support TLS above version 1.0?
The link only talks about Chrome.
Mar
20
revised Why don't major browsers currently support TLS above version 1.0?
added 108 characters in body
Mar
20
revised Why don't major browsers currently support TLS above version 1.0?
added 1406 characters in body
Mar
19
revised Why don't major browsers currently support TLS above version 1.0?
Expanded the question to make it more clear
Mar
19
comment Why don't major browsers currently support TLS above version 1.0?
<_There has been compatibility problems with servers that has not activated the newer protocols._> - you can still fallback to older versions. The problem is the clients.