if SSL traffic can be sniffed and decrytped by someone in your
subnet or by somone that compromised one of your routers creating
something like a GRE tunnel, then you're f*****
Whilst this is true, MITM and sniffing both rely on something else to be
broken before they are of any practical use (keys already obtained, a
fake trust hierarchy to be accepted by a client etc.). SSL works fine
when implemented properly.
About how to store password in the db:
A salt is always recommended, but if you store password hashed with
sha-256 or even 512 you're almost safe, despite the rainbow tables
;)
The salt is the thing that makes the rainbow tables ineffective; all
common hash algorithms are prone to rainbow tables, because they are
*common* and designed for general data throughput, not as password
specific hashes.
Martin...
----------------------------------------------------------------------
CONFIDENTIALITY: This e-mail and any files transmitted with it are
confidential and intended solely for the use of the recipient(s) only.
Any review, retransmission, dissemination or other use of, or taking
any action in reliance upon this information by persons or entities
other than the intended recipient(s) is prohibited. If you have
received this e-mail in error please notify the sender immediately
and destroy the material whether stored on a computer or otherwise.
----------------------------------------------------------------------
DISCLAIMER: Any views or opinions presented within this e-mail are
solely those of the author and do not necessarily represent those
of Corsaire Limited, unless otherwise specifically stated.
----------------------------------------------------------------------
Corsaire Limited, registered in England No. 3338312. Registered
office: Portland House, Park Street, Bagshot, Surrey GU19 5PG.
Telephone: +44 (0)1483-746700