You Want Salt With That? Part One: Security vs Obscurity  You
Want Salt With That? Part One: Security vs Obscurity    •
Comments 10              • There's nothing like adding a little
bit of obscurity to a known-secure scheme. Suppose, for
instance, that you're using SSL in a system where both ends of
the communications link are under your control. Then there's
nothing to stop you flipping a couple of bits in the input to
one of the hashes: it takes you no time at all, and it provably
doesn't weaken the security; but it'll confuse the hell of
someone trying to reverse-engineer your protocol. The more human
time you can waste, without wasting computer time or
compromising security, the better.   • Off-topic, but still
related (security after all). I've created an ActiveX that
downloads data from a web server, using async monikers et al. I
understand that in order to support download from sites that
require authentication, I need to implement IAuthenticate. Thing
is, the download will most likely occur from the