Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been trying to use OpenVPN to connect to my work network. Using it via the command line works fine:

openvpn user.conf

I haven't bothered to set it up with DNS properly though, and it looks to be a bit of a pain. I'd much rather use it through the network manager like my other VPNs. The problem is this: I store my user.crt, along with ca.crt and user.key in ~/.openvpn/ (which seems like a reasonable place to keep such things. When I try to connect via NetworkManager, it just tells me that the connection has failed. Inspection of /var/logs/messages reveals the reason: SELinux is enforcing some policy somewhere that stops openvpn from reading my certificates. I tried following all the instructions given by the SELinux troubleshooter, but to no avail.

I then, foolishly indeed deleted the openvpn policy from my SELinux config (using the SELinux Management gui, available from the fedora repos). All sorts of hell broke loose (it wouldn't even let it bind a named port anymore).

The problem was pretty urgent, so I've ended up just disabling SELinux for the session (everything works fine with that out of the way). But I'll have to turn it back on again at some point, so my question is this:

How can I first restore my original policy file for openvpn in SELinux, and then second grant openvpn access to certificates in my home directory?

I have also tried the SE Policy Generator tool, but to no apparent avail (it gets stuck on the dialogue where I give the policy a name).

share|improve this question
up vote 2 down vote accepted

To restore the OpenVPN policy module, just run the following command on a terminal as root:

semodule -i /usr/share/selinux/targeted/openvpn.pp.bz2

If for some reason that file is missing (unlikely, but I'm not sure what system-config-selinux does exactly), reinstall the SELinux policy package and try again:

yum reinstall selinux-policy-targeted

Finally, to permit OpenVPN to read files from your home directory, run this command:

setsebool -P openvpn_enable_homedirs 1

You should also be able to set openvpn_enable_homedirs in the list of SELinux booleans in the graphical administration tool.

share|improve this answer
Restoring previous policies works perfectly... setsebool ..., however, I tried already. Will post updates tomorrow. – jelford Sep 30 '11 at 15:18
@jelford: If the boolean isn't working then there is a problem with Fedora's SELinux policy. I suggest that you file a bug against selinux-policy-targeted. – Patches Oct 1 '11 at 0:16
Works perfectly now. Thanks for the help. – jelford Oct 3 '11 at 11:57

Just meet similar problem in Fedora 18

Look there

Place certificates in right place (from Fedora point of view) ~/.pki and make

restorecon -R -v ~/.pki

for sure

Openvpn now work.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.