New book by Joel McNamara who runs the Tempest website:
http://www.eskimo.com/~joel/tempest.html
http://www.wiley.com/legacy/compbooks/mcnamara/
Secrets of Computer Espionage: Tactics and Countermeasures
by Joel McNamara
Covers electronic and wireless eavesdropping, computer surveillance,
Sunder [EMAIL PROTECTED] writes:
The worst trouble I've had with https is that you have no way to use host
header names to differentiate between sites that require different SSL
certificates.
i.e. www.foo.com www.bar.com www.baz.com can't all live on the same IP and
have individual ssl
At 10:56 AM 6/11/2003 -0400, Sunder wrote:
In either case, we wouldn't need to worry about paying Verisign or anyone
else if we had properly secured DNS. Then you could trust those pop-up
self-signed SSL cert warnings.
actually, if you had a properly secured DNS then you could trust DNS
to
somewhat related to the early posting in this m.l. about distributed
computing systems conference and possible interest from security and
cryptography sections.
when my wife and I were doing ha/cmp
http://www.garlic.com/~lynn/subtopic.html#hacmp
we were working with two people in the following
To try to reflect some of David's points with a real-world situation. I
was at work, with a brand new installation of PGP. I wanted to send some
confidential data home so I could work with it. However I didn't have my
home key at work, so I didn't have a secure way to send either the data, or
