Re: Cryptography problem

From: Jim Grimmett (cssjwg_at_bath.ac.uk)
Date: 06/23/04 

Date: Wed, 23 Jun 2004 16:04:17 GMT

"Dean Hallman" <deanh@sc.rr.com> wrote in message:
>
> I had hoped I could use an off-the-shelf solution, but was unsure if the
> "known plaintext" and "client in the wild" aspects of this problem would
> go against their assumptions. I'll take a look at OpenSSL.

Well, here's a thought. Get each client to generate a public/private
key pair and email you the public key.

Part of your process could then be to encrypt a 'code' with their
public key and send it to them (across a secure transport) and
wait for them to give you the decrypted code back, again across
the secure transport.

Don't have to worry about the client being in the wild, they can't
use it as they're not registered and you only keep registered
public keys.

Don't have to worry about man in the middle if the transport
is secure.

Don't have to worry about 'tickets' etc, as you can automate
generating and keeping hold and emailing you the public/private
key combinations.

Sorry to miss this one - fairly obvious really.

Jim.

Relevant Pages

  • Re: Basics of key authentication
    ... so everything I've read basically tells me the client creates a public ... The public key gets copied to the server, ... and the client decrypts it with its private key to prove he is who he ... > public/private keys between client and server? ...
    (comp.security.ssh)
  • Re: Cryptography problem
    ... Get each client to generate a public/private ... the secure transport. ... Don't have to worry about the client being in the wild, ...
    (comp.security.misc)