Re: [Swan] IKEv2 connection "no RSA public key known for" and "RSA authentication failed"

2015-11-15 Thread Tom Robinson
On 16/11/15 11:05, Tom Robinson wrote: > On 15/11/15 01:50, Tom Robinson wrote: >> On 14/11/15 22:58, Tuomo Soini wrote: >>> On Sat, 14 Nov 2015 21:56:54 +1100 >>> Tom Robinson wrote: >>> >>> My apologies, I should have said earlier. We're running

Re: [Swan] IKEv2 connection "no RSA public key known for" and "RSA authentication failed"

2015-11-14 Thread Tom Robinson
On 14/11/15 01:50, Matt Rogers wrote: > - Original Message - >> From: "Tom Robinson" <tom.robin...@motec.com.au> >> To: swan@lists.libreswan.org >> Sent: Thursday, November 12, 2015 4:24:10 PM >> Subject: Re: [Swan] IKEv2 connection "no RSA p

Re: [Swan] IKEv2 connection "no RSA public key known for" and "RSA authentication failed"

2015-11-14 Thread Tuomo Soini
On Sat, 14 Nov 2015 21:56:54 +1100 Tom Robinson wrote: > My apologies, I should have said earlier. We're running > libreswan-3.9-1 on CentOS 5. That is all too old version. It doesn't have any support for this config. Upgrade to 3.13 which is last version which will

Re: [Swan] IKEv2 connection "no RSA public key known for" and "RSA authentication failed"

2015-11-14 Thread Tom Robinson
On 14/11/15 22:58, Tuomo Soini wrote: > On Sat, 14 Nov 2015 21:56:54 +1100 > Tom Robinson wrote: > > >> My apologies, I should have said earlier. We're running >> libreswan-3.9-1 on CentOS 5. > > That is all too old version. It doesn't have any support for this >

Re: [Swan] IKEv2 connection "no RSA public key known for" and "RSA authentication failed"

2015-11-13 Thread Matt Rogers
- Original Message - > From: "Tom Robinson" <tom.robin...@motec.com.au> > To: swan@lists.libreswan.org > Sent: Thursday, November 12, 2015 4:24:10 PM > Subject: Re: [Swan] IKEv2 connection "no RSA public key known for" and "RSA > authenticatio

Re: [Swan] IKEv2 connection "no RSA public key known for" and "RSA authentication failed"

2015-11-11 Thread Tom Robinson
Hi Matt, Thanks for your response. On 12/11/15 01:15, Matt Rogers wrote: > You should set rightid=%fromcert so it will use the received cert subject > as the ID here. > I've added rightid=%fromcert to the connection but it still fails as follows: Nov 12 08:15:38 fw2 pluto[26342]: