On Thu, Jun 21, 2012 at 10:53 AM, Issac Goldstand <[email protected]> wrote: > On 21/06/2012 12:40, Ben Laurie wrote: >> 4. Use something that is hard to optimise in hardware (ideally). > And what about massive sites that need the crypto HW to manage the > concurrent logins?
I have never come across a site where login causes significant load. They may exist, but I figure they can do their own thing for passwords... > Yes, you're making it harder on the hackers, but also potentially on our > users. > > ...Or did I just put my foot in my crypto-clueless-mouth? > > Issac >
