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

RE: XAUTH is broken

To: "'Dan Harkins'" <dharkins@network-alchemy.com>
Subject: RE: XAUTH is broken
From: Greg Carter <greg.carter@entrust.com>
Date: Tue, 27 Jul 1999 11:06:35 -0400
Cc: ipsec@lists.tislabs.com
Sender: owner-ipsec@lists.tislabs.com

What about Config Mode and the Exchange Type?
Shouldn't it specify a number in the private use range instead of '6' as
selected by the draft?

Bye.
-----Original Message-----
From: Dan Harkins [mailto:dharkins@network-alchemy.com]
Sent: Monday, July 26, 1999 2:38 PM
To: Scott G. Kelly
Cc: Paul Koning; joern.sierwald@datafellows.com; ipsec@lists.tislabs.com
Subject: Re: XAUTH is broken 

  It also prevents conflicts. The first rev of the GSS-API draft used
the value 13 to represent the GSS-API Token Payload since that was

Prev by Date: RE: XAUTH is broken
Next by Date: xauth requirements: vulnerabilities
Prev by thread: RE: XAUTH is broken
Next by thread: RE: KISS for PKIX. (Was: RE:Asymmetric authentication
Index(es):
- Main
- Thread