I made a bug that is relevant to this post here. However, I'm turning to the community now, as I cannot believe that no one else has stumbled on this issue. I'm not using any wild configuration settings, it's just a regular roadwarrior setting using ikev2, tunnel (+ipcomp transport) and authentication using RSA signatures (PKI infra).

This is on an updated Ubuntu 12.04 barebones installation.

However, on the cliënt, when I want to start the connection, I get this:
And this is where things get really weird:

But we are root right... ? Yes we are:

More relevant info can be found in the bugreport. We haven't tried much so far, only the suggestion made by this link. No dice though.

And it is no way my intention to start a flamewar, troll or something... But these settings work on a Gentoo cliënt. I'm one of the few lucky one's who managed to 'convert' my parents to use Linux and Ubuntu was the logical choice (introducing my parents to Gentoo's emerge, USE-flags, CFLAGS, compilation failures, ABI/API compatibility might happen in another 100 years ). It's a really simple setup. Basically it's and alternative installation CD. I simply only installed base and the user-session starts with startx. It has no networkmanager, no display manager and uses XFCE components to work. At boot it uses 93 out of 512 MB of RAM (so that is not an issue I suppose). PAM authentication works, I had to do some fiddling to authenticate the regular user with consolekit but this works now. Power events (shutdown, restart, hibernate) and USB devices (camera's, USB, mounting, umounting) all work flawlessly.

Thanks in advance for *any* suggestions

Run the command under strace, maybe there's something strange in the actual open() call

1 members found this post helpful.

Yes, I did that and indeed something is strange:

[pid 22519] open("/dev/urandom", O_RDONLY) = -1 EACCES (Permission denied)

Which crazy since:

root@Delta:~# ps -p 21021,22515,21020,22514 -o args,group,pgid,ppid,rgroup,ruser,tty,user,gid,rgid,ruid,uid
COMMAND GROUP PGID PPID RGROUP RUSER TT USER GID RGID RUID UID
/usr/lib/ipsec/starter root 21020 1 root root ? root 0 0 0 0
/usr/lib/ipsec/charon --use root 21021 21020 root root ? root 0 0 0 0
/usr/lib/ipsec/starter root 22514 1 root root ? root 0 0 0 0
/usr/lib/ipsec/charon --use root 22515 22514 root root ? root 0 0 0 0

I have a full strace attached in the bug, but I will also attach it here.

Attached Files

starter_strace.txt (78.7 KB, 11 views)

Can't see anything obvious in the trace, do you have selinux installed/enabled?

1 members found this post helpful.

Nope, no nothing. Just Unix Discretionary Access Controls (DAC). No Apparmor, no grsecurity, no pax or anything else LSM related. I disabled this in the kernel, so it is not even possible to be 'accidentally' enabled.

I compiled a custom 4.6.4 version from the strongswan.org website. It fails the same way. I'm currently building with libcap disabled, as that is the only possibility left that I can think of.

If that doesn't work, I'll resort to disabling the 'random' plugin (if that makes Strongswan still function though).

Thanks for your time and dedication . Aside from launchpad, you are the only one responding. Ubuntuforums and linuxforums.org yields NULL responses so far.

Yup, disabling libcap functionality fixes the issue. Strongswan has a 'native' alternative, but I haven't tried that one yet.

Disabling it is not *such* a big deal as this Strongswan installation is a client. Thanks anyway!

Further findings will be placed in bug 1014361.