[Full-disclosure] JaPCrypt

[Valdis.Kletnieks at vt.edu]

On Wed, 06 Feb 2008 17:23:49 +0100, Christoph Gruber said:

> If you are able to use PGP/GPG/S/Mime you HAVE already an implemented  
> PKI. Why should someone use PKI to initialize another?

There's this thing called "The Real World", where often you end up doing
stuff like this because something is just plain busticated.  For instance,
https gives us:

a PKI that allows us to use RSA or similar to verify the other end's identity
and exchange a shared-secret to use as a symmetric session key.

Unfortunately, there's cases where you don't *have* https available (as noted
in the original posting).  So what do you do?  You roll-your-own using
PGP or S/MIME to verify identities (if it isn't who it claims to be from,
it won't decrypt) and exchange a shared secret, and then use JaPCrypt to
do the symmetric encryption.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20080206/f50f6b0e/attachment.bin