Pantek Library
Hosting Provided By
CybrHost
High Speed Hosting

Re: [Design] Re: [Users] multiple ipsec.secrets entries

From: Paul Wouters <paul(at)xtdnet.nl>
Date: Fri Feb 28 2003 - 06:19:57 EST


On Fri, 28 Feb 2003, Andreas Steffen wrote:

> Certificate based connections always find the correct
> private key in ipsec.secret because a link to the
> certificate loaded via the leftcert command is maintained in
> the connection description which allows to match the public
> key contained in the certificate to the public key in the
> private key representation.

I don't think this is always true. The case that Ken and me ran into a few days ago that prompted our question was the Opportunistic Encryption case. It seems that if a roadwarrior initiates a connection to a gatway that uses both a certificate and opportunistic encryption, things get confused. I believe this is happening:

  1. Incoming udp 500 from certificates based road warrior
  2. gateway detects incoming and adds a %shunt(?) eroute, blocking
communication while trying to do opportunistic encryption.
  • opportunistc encryption failed, road warrior doesnt support it and a %pass follows
  • roadwarrior sends its ID, and Pluto disgards it as part of a "previous exchange".

I might be wrong in the inner workings of Pluto, but the OE connection is definately causing it to interfere with the X509 connection. We see interleeaving log entries, suggesting these connectin attempts happen at the same time.

> - Although not mandatory, the local public key can be defined
> in connections based on raw RSA keys by using the leftrsasigkey
> parameter. Since X.509-1.1.6 for freeswan-2.00 alread supports
> both X.509 and OpenPGP certificates, as a thirk class, a link to
> the raw public key could be created in the connection description
> which would allow the private key to be found in ipsec.secrets
> irrespective of its position in the list.

We started experimenting with this, but didn't finish it so far. What needs to be tested is trying to have a 'normal' raw key connectin and an x509 based one work properly using the proper definitions in the ipsec.secrets file, and only then try to add the complexity of Opportunistic Encryption.

> This would also introduce
> support of multiple RSA private keys in roadwarrior connections based
> on raw RSA public keys. I could implement this feature within
> the next month but for freeswan-2.00, only.

I'll leave those decisions up to the people involved. I'm just a volunteer :) (But instinct tells me "go for it" :)

Do you need help?X

I do wonder whether it is possible to distinguish the opportunistic encryption's secret from other secrets more clearly, so that pluto doesn't need to fight with itself if it is supporting OE and X509.

Paul



Users mailing list
Users@lists.freeswan.org
http://lists.freeswan.org/mailman/listinfo/users Received on Fri Feb 28 10:00:57 2003

This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 13:00:23 EDT


Contact Us  Legal Notices  Order Services Online 
Pantek Home  Privacy Policy  IT news  Site Map  Pantek Library