News for hackers. Stuff that matters.
Re:Hack of Cupid Media dating website exposes 42 million pla... by nly on Wednesday November 20, 2013 @08:05AM (#6767724)
The first step in the SRP protocol is to retrieve the cryptographic salt from the server, so you're essentially free to roam.

This step has concerns of its own though... for one thing the request itself reveals that the username/id is valid, and if you cache the userid / salt pair on the client machine it's vulnerable to snooping by other people with physical access. There are some fairly straightforward tweaks that can be made to the protocol to work around these issues though, since the salt isn't sensitive. In fact, I'm pretty confident storing the salt server side can be eliminated.

Re:Hack of Cupid Media dating website exposes 42 million pla... by vidarh on Wednesday November 20, 2013 @08:16AM (#6767759)
> This step has concerns of its own though... for one thing the request itself reveals that the username/id is valid

Does it have to? Can you not have an implementation that always responds with a fake salt if the username is not valid?

Re:Hack of Cupid Media dating website exposes 42 million pla... by nly on Wednesday November 20, 2013 @08:31AM (#6767820)
Yes, or you can just use a deterministic salt like H ( service id || user id )