[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: CRACK

Hi Dan,

Looks good. 

Where did CRACK come from? A dubious name in a security protocol.

Can the client's private/public key be unique for each connection?

For the case where the legacy authentication is something a typical client
could deal with (password or chap-thing), should this support symmetric
trust of the public keys used - e.g. the client trusts the gateway based on
the client holding legacy authentication information for the server?


Steve.

-----Original Message-----
From: Dan Harkins [mailto:dharkins@network-alchemy.com]
Sent: Thursday, October 21, 1999 7:36 PM
To: ipsec@lists.tislabs.com
Subject: Re: CRACK 


  Double-oops. I fat-fingered the reply to the IPSec list....

  Dan.

On Thu, 21 Oct 1999 10:58:00 PDT you wrote
>   Oops. You have to put a "/" after that url. That or just append a "/"
> and the draft name. That should do it. It's out there, really. :-)
> 
>   Dan.
> 
> On Thu, 21 Oct 1999 10:14:28 PDT you wrote
> > Is there a time delay between submitting the draft and when it will
appear
> > on ietf web site? I tried to follow the link - also did a search
> > on ietf website, but could not find the draft.
> > 
> > Any pointers to where I can get a copy?
> > 
> > Thanks,
> > -- sankar --
> > 
> > 
> > -----Original Message-----
> > From: Dan Harkins [mailto:dharkins@network-alchemy.com]
> > Sent: Thursday, October 21, 1999 9:19 AM
> > To: ipsec@lists.tislabs.com
> > Cc: ietf-ipsra@vpnc.org
> > Subject: CRACK
> > 
> > 
> >   A few weeks ago I was alluding to a draft which would address the
> > desire to do token card authentication in IKE (and do it securely).
> > The draft is out but is an individual I-D submission due to the fact
> > that remote access is going to be the responsibility of IPSRA which
> > does not yet formally exist. Please check it out and comment. It's
> > called draft-harkins-ipsec-ike-crack-00.txt and can be found with the
> > others at http://www.ietf.cnri.reston.va.us/internet-drafts.
> > 
> >   Dan.
> >
Follow-Ups: