Subject: Re: "racoon" installation
To: None <Havard.Eidnes@runit.sintef.no>
From: None <itojun@iijlab.net>
List: tech-security
Date: 03/12/2000 08:34:16
  by redmail.netbsd.org with SMTP; 11 Mar 2000 23:34:40 -0000
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id IAA13894;
	Sun, 12 Mar 2000 08:34:16 +0900 (JST)
To: Havard.Eidnes@runit.sintef.no
cc: mcr@sandelman.ottawa.on.ca, tech-security@netbsd.org
In-reply-to: Havard.Eidnes's message of Sat, 11 Mar 2000 23:40:14 +0100.
      <20000311234014Z.he@runit.sintef.no>
Subject: Re: "racoon" installation 
From: itojun@iijlab.net
Date: Sun, 12 Mar 2000 08:34:16 +0900
Message-ID: <13892.952817656@coconut.itojun.org>



>>   I would rather that we had dummy RSA code that called abort()
>> such that racoon would link and one could use pre-shared
>> secrets. If one happened to have built one's libcrypto with the
>> extra code, then things work.
>
>I agree.  Isn't this primarily a problem for cryptosrc-us and/or
>users in the US?  And the problem will go away later this year when
>the RSA patent expires, right?
>
>Given that, I think we should long-term strive for having a fully-
>functional racoon integrated, and pick an interim solution which
>causes the least amount of pain.

	racoon is still in its infancy.  I expect big changes into it.
	I do prefer installing it as pkgsrc.

itojun