[Openswan Users] OpenSwan to Strongswan RSA Problem
andy
andy at andynet.net
Wed Jul 5 08:24:00 EDT 2017
On Tue, Jul 04, 2017 at 07:13:08PM +0000, Matt Killock wrote:
..snip..
> 000 "test": 10.2.0.0/24===192.168.100.37<192.168.100.37>[0x3068310B300906035504061302434831133011060355040A130A7374726F6E675377616E3110300E06035504031307636F76617A667700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000,+S=C]...192.168.100.38<192.168.100.38>[0x3066310B300906035504061302434831133011060355040A130A7374726F6E675377616E310F300D06035504031306617370667732000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000,+S=C]===10.1.0.0/24; prospective erouted; eroute owner: #0
Hmm - this is weird! Looks to me that maybe your config hasn't loaded properly - I'd expect to see the left/rightids inside the
square brackets here, not these long hex strings. I've never seen that before.
But maybe something has changed in recent versions of Openswan - it's beeen a while since I used it.
I was expecting to see something like:
"test": 10.2.0.0/24===192.168.100.37<192.168.100.37>[C=CH, O=strongSwan, CN=covazfw]...192.168.100.38<192.168.100.38>[C=CH, O=strongSwan, CN=aspfw2]===10.1.0.0/24
If it's getting the IDs wrong somehow, that would explain why it can't find a matching connection.
Perhaps there are more clues in the logs? Does it mention if it's loaded the CA cert? Perhaps you could post all of /var/log/auth.log
while restarting Openswan? I'm not sure what else to suggest atm.
> 000 "test": myip=unset; hisip=unset;
> 000 "test": ike_life: 3600s; ipsec_life: 28800s; rekey_margin: 540s; rekey_fuzz: 100%; keyingtries: 0
> 000 "test": policy: RSASIG+ENCRYPT+TUNNEL+PFS+UP+IKEv2ALLOW+SAREFTRACK; prio: 24,24; interface: eth0;
> 000 "test": dpd: action:clear; delay:15; timeout:50;
> 000 "test": newest ISAKMP SA: #0; newest IPsec SA: #0;
> 000 "test": IKE algorithms wanted: AES_CBC(7)_128-SHA1(2)_000-MODP2048(14); flags=-strict
> 000 "test": IKE algorithms found: AES_CBC(7)_128-SHA1(2)_160-MODP2048(14)
> 000 "test": ESP algorithms wanted: AES(12)_128-SHA1(2)_000; flags=-strict
> 000 "test": ESP algorithms loaded: AES(12)_128-SHA1(2)_160
> 000
> 000 #122: "test":500 STATE_MAIN_I1 (sent MI1, expecting MR1); EVENT_RETRANSMIT in 2s; nodpd; idle; import:admin initiate
> 000 #122: pending Phase 2 for "test" replacing #0
> 000
>
> Thanks
> Matt
>
>
> -----Original Message-----
> From: andy [mailto:andy at andynet.net]
> Sent: 04 July 2017 17:36
> To: Matt Killock <matt.killock at praemium.com>
> Cc: users at lists.openswan.org
> Subject: Re: [Openswan Users] OpenSwan to Strongswan RSA Problem
>
> Hi Matt -
> can you post the Openswan output from 'ipsec auto --status' please?
>
> Thanks
> Andy
>
> On Tue, Jul 04, 2017 at 03:51:32PM +0000, Matt Killock wrote:
> > Hello,
> >
> >
> >
> > I managed to make a working connection between two linux machines, one running
> > OpenSwan and the other running StrongSwan using PSK. The config on the Openswan
> > side was as follows:
> >
> >
> >
> > conn test
> >
> > authby=secret
> >
> > type=tunnel
> >
> > left=192.168.100.37
> >
> > leftsubnet=10.2.0.0/24
> >
> > right=192.168.100.38
> >
> > rightsubnet=10.1.0.0/24
> >
> > auto=start
> >
> > esp=aes128-sha1
> >
> > ike=aes128-sha1-modp2048
> >
> > rekey=yes
> >
> > dpdaction=clear
> >
> > dpddelay=15
> >
> > dpdtimeout=50
> >
> > compress=no
> >
> >
> >
> > However, after attempting to change this to work with RSA certs, I have run
> > into a problem. The Openswan config now looks like this:
> >
> >
> >
> > conn test
> >
> > authby=rsasig
> >
> > type=tunnel
> >
> > left=192.168.100.37
> >
> > leftsubnet=10.2.0.0/24
> >
> > right=192.168.100.38
> >
> > rightsubnet=10.1.0.0/24
> >
> > auto=start
> >
> > esp=aes128-sha1
> >
> > ike=aes128-sha1-modp2048
> >
> > rekey=yes
> >
> > dpdaction=clear
> >
> > dpddelay=15
> >
> > dpdtimeout=50
> >
> > compress=no
> >
> > leftcert=/etc/ipsec.d/certs/covazfw.pem
> >
> > rightcert=/etc/ipsec.d/certs/aspfw2.pem
> >
> > leftid="C=CH, O=strongSwan, CN=covazfw"
> >
> > rightid="C=CH, O=strongSwan, CN=aspfw2"
> >
> >
> >
> > All the relevant public certs are in the ipsec.d subfolder hierarchy, along
> > with the private key for the OpenSwan side covazfw.pem.
> >
> >
> >
> > Ipsec.secrets is as follows:
> >
> >
> >
> > : RSA /etc/ipsec.d/private/covazfw.pem
> >
> >
> >
> > The auth.log shows this:
> >
> >
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: packet from 192.168.100.38:500:
> > received Vendor ID payload [XAUTH]
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: packet from 192.168.100.38:500:
> > received Vendor ID payload [Dead Peer Detection]
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: packet from 192.168.100.38:500:
> > received Vendor ID payload [RFC 3947] method set to=109
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: packet from 192.168.100.38:500:
> > received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] meth=106, but
> > already using method 109
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: "test" #14: responding to Main Mode
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: "test" #14: transition from state
> > STATE_MAIN_R0 to state STATE_MAIN_R1
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: "test" #14: STATE_MAIN_R1: sent MR1,
> > expecting MI2
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: "test" #14: NAT-Traversal: Result using
> > RFC 3947 (NAT-Traversal): no NAT detected
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: "test" #14: transition from state
> > STATE_MAIN_R1 to state STATE_MAIN_R2
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: "test" #14: STATE_MAIN_R2: sent MR2,
> > expecting MI3
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: "test" #14: Main mode peer ID is
> > ID_DER_ASN1_DN: 'C=CH, O=strongSwan, CN=aspfw2'
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: "test" #14: no suitable connection for
> > peer 'C=CH, O=strongSwan, CN=aspfw2'
> >
> > Jul 4 16:37:43 covtestvpn pluto[7623]: "test" #14: sending encrypted
> > notification INVALID_ID_INFORMATION to 192.168.100.38:500
> >
> > Jul 4 16:37:47 covtestvpn pluto[7623]: "test" #14: Main mode peer ID is
> > ID_DER_ASN1_DN: 'C=CH, O=strongSwan, CN=aspfw2'
> >
> > Jul 4 16:37:47 covtestvpn pluto[7623]: "test" #14: no suitable connection for
> > peer 'C=CH, O=strongSwan, CN=aspfw2'
> >
> > Jul 4 16:37:47 covtestvpn pluto[7623]: "test" #14: sending encrypted
> > notification INVALID_ID_INFORMATION to 192.168.100.38:500
> >
> >
> >
> > It seems that it cannot / will not authenticate the certificate from the
> > Strongswan side. Could someone tell me what I’m doing wrong please?
> >
> >
> >
> > Thanks
> >
> >
> >
> > Matt
> >
> >
> > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> >
> > Plum Software is a fully owned subsidiary of Praemium Limited.
> >
> > This e-mail is confidential. It may also be legally privileged. If you are not
> > the addressee, you may not copy, forward, disclose or use any part of it. If
> > you have received this message in error, please delete it and all copies from
> > your system and notify the sender immediately by return email. Internet
> > communications cannot be guaranteed to be timely, secure, or error or virus
> > free. The sender does not accept liability for any errors or omissions.
> >
> > In the UK the Praemium Group is: Praemium Portfolio Services Ltd (Company
> > Number: 05362168), Praemium (UK) Ltd (Company Number: 05362153), Praemium
> > Administration Ltd (Company Number: 06016828) and Smartfund Nominees Ltd
> > (Company Number: 07153417) each having its registered office at 4th Floor,
> > Suite 643-659, Salisbury House, London Wall, London, EC2M 5QQ, United Kingdom.
> > Praemium Administration Ltd is authorised and regulated by the Financial
> > Conduct Authority under reference 463566. See http://www.fca.org.uk/register
> > for more details.
> >
> > In Jersey the Praemium Group is: Praemium International Ltd (Company Number:
> > 107624) which has its registered office at 3rd Floor East, Salisbury House, 1-9
> > Union Street, St Helier, JE2 3RF and is regulated under the Financial Service
> > (Jersey) Law 1998 by the Jersey Financial Services Commission for the conduct
> > of investment business in Jersey. See http://www.jerseyfsc.org for more
> > details.
> >
> > Thank you for your cooperation. Please contact us on +44 (0)207 5622 450 if you
> > require assistance.
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
>
> > _______________________________________________
> > Users at lists.openswan.org
> > https://lists.openswan.org/mailman/listinfo/users
> > Micropayments: https://flattr.com/thing/38387/IPsec-for-Linux-made-easy
> > Building and Integrating Virtual Private Networks with Openswan:
> > http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155
>
>
> ________________________________
>
> Plum Software is a fully owned subsidiary of Praemium Limited.
>
> This e-mail is confidential. It may also be legally privileged. If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return email. Internet communications cannot be guaranteed to be timely, secure, or error or virus free. The sender does not accept liability for any errors or omissions.
>
> In the UK the Praemium Group is: Praemium Portfolio Services Ltd (Company Number: 05362168), Praemium (UK) Ltd (Company Number: 05362153), Praemium Administration Ltd (Company Number: 06016828) and Smartfund Nominees Ltd (Company Number: 07153417) each having its registered office at 4th Floor, Suite 643-659, Salisbury House, London Wall, London, EC2M 5QQ, United Kingdom. Praemium Administration Ltd is authorised and regulated by the Financial Conduct Authority under reference 463566. See http://www.fca.org.uk/register for more details.
>
> In Jersey the Praemium Group is: Praemium International Ltd (Company Number: 107624) which has its registered office at 3rd Floor East, Salisbury House, 1-9 Union Street, St Helier, JE2 3RF and is regulated under the Financial Service (Jersey) Law 1998 by the Jersey Financial Services Commission for the conduct of investment business in Jersey. See http://www.jerseyfsc.org for more details.
>
> Thank you for your cooperation. Please contact us on +44 (0)207 5622 450 if you require assistance.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
More information about the Users
mailing list