[strongSwan] ANNOUNCE: strongswan-4.3.4 released

Hi, the latest strongSwan release 4.3.4 is ready for download. Here are the major new features: - IKEv2 daemon ported to FreeBSD and Mac OS X --- With some minor restrictions the IKEv2 charon daemon now runs on the FreeBSD and Mac OS X operating syste

[strongSwan] unable to allocate SPIs from kernel

Hi, I am an ipsec beginner. I installed strongswan 4.3.3 on my FC10/FC11 machines and tried to setup a host-host tunnel. But I get the following error. Googling it and searching for it in strongswan wiki didn't give any results. [r...@localhost ~]# ipsec restart Stopping strongSwan IPsec... St

Re: [strongSwan] BUG: DN with email

Yes, this is actually the real fix which was a corruption of the OID tree. Regards Andreas Dimitrios Siganos wrote: > Yes, it does fix it. Thank you. > > I noticed that you commited some more changes related to email OIDs. Are > they important? Should I get those too? > I am referring to >

Re: [strongSwan] BUG: DN with email

Yes, it does fix it. Thank you. I noticed that you commited some more changes related to email OIDs. Are they important? Should I get those too? I am referring to . Regards, Dimitrios Siganos

[strongSwan] bashism in ipsec script

The ipsec script has the following bashism (line 324 of ipsec script, git commit 333b461aa689c29197dadb2a15abc3ccade0c89a): loop=$(($loop - 1)) This doesn't work on my embedded board running busybox msh. I suggest changing the live above, to: loop=`expr $loop - 1` to make it more portable. R

Re: [strongSwan] BUG: DN with email

Hi Dimitrios, yes, you are right. A recent refactoring of the RDN synthesis function introduced a wrong emailAddress OID (there are at least three of them but in most cases the PKCS#9 definition is still used). The following patch should fix your problem: http://wiki.strongswan.org/repositories/

[strongSwan] BUG: DN with email

Hi, I believe I have found a bug with the latest strongswan. I used strongswan-4.3.3 and also the latest git code (commit 333b461aa689c29197dadb2a15abc3ccade0c89a). They both exhibit the same or similar problem. The problem appears when I add an email address to a certificate DN and then try