Re: kern/13905 (IPsec: Our ESP "NULL" cipher doesn't interoperate with the one in Win2K even in configurations where DES and 3DES do.)

[Thor Lancelot Simon <tls%panix.com@localhost>]

The following reply was made to PR kern/13905; it has been noted by GNATS.

From: Thor Lancelot Simon <tls%panix.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
	gnats-admin%netbsd.org@localhost, maxv%NetBSD.org@localhost, tls%rek.tjls.com@localhost
Subject: Re: kern/13905 (IPsec: Our ESP "NULL" cipher doesn't interoperate
 with the one in Win2K even in configurations where DES and 3DES do.)
Date: Sun, 25 Feb 2018 16:39:45 -0500

 Beats me.  I thankfully don't have Win2k available any longer to test.
 
 On Sun, Feb 25, 2018 at 06:02:54PM +0000, maxv%NetBSD.org@localhost wrote:
 > Synopsis: IPsec: Our ESP "NULL" cipher doesn't interoperate with the one in Win2K even in configurations where DES and 3DES do.
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: maxv%NetBSD.org@localhost
 > State-Changed-When: Sun, 25 Feb 2018 18:02:54 +0000
 > State-Changed-Why:
 > The IPsec code has been fixed many times since. Does the issue still
 > occur? (While here I put "IPsec" in the title for clarity.)
 > 
 > 
 
 -- 
   Thor Lancelot Simon	                                     tls%panix.com@localhost
  "The two most common variations translate as follows:
 	illegitimi non carborundum = the unlawful are not silicon carbide
 	illegitimis non carborundum = the unlawful don't have silicon carbide."