Making OpenVPN key creation easier until we get a GUI

gmckinney

Maybe in the next 3-4 months… Stay tuned!

Let me know if there is anything I can do to help out - this would be a very nice addition but I keep getting side-tracked with other RL items. Any thoughts on "how" to maintain the key sets - should there be multiple CA keys or just limit to one CA and everything builds/tests off of that one keyset???

I have some ideas but get really gummed up in the details (grin)…

gm...

sullrich

Most likely only one CA. But I am open to ideas.

gmckinney

I suppose your target is for both the embedded and the HD install version for the OpenVPN stuff…

Probably one CA would be a good starting point - keeps the internal side of things less complex - at least in the beginning for a GUI interface otherwise you need a method to keep track of what CA is used for which server and client keys. I realize that is not too difficult to do but if you have one CA to each server instance or client instance and someone decides they want to have 100+ VPN clients then things get a little big in terms of the storage for all the keys involved. This would especially be true in an embedded environment.

One other question - are you still looking at an auto installer for say Windows clients using NSIS ? It looks rather interesting but I have just started looking at it myself - have you done anything with it yet?

addendum...

It looks like compiling the makensis for pfsense will be a little involved - If I am following the general instructions correctly (http://nsis.sourceforge.net/Docs/AppendixG.html#G) it looks like a pre-compiled version originally for Windows is picked apart so the makensis has access to the Windows specific pieces when the nsis script is "compiled". From what I have figured out this is what is needed to allow creating a Windows installer for an OpenVPN client configuration on a Windows OS based machine - is this a correct interpretation on my part???
It seems this would be the only way to have the installer program create the installation exe with all the parts needed for an OpenVPN client installer.

gm...

sullrich

@gmckinney:

I suppose your target is for both the embedded and the HD install version for the OpenVPN stuff…

Yep.

@gmckinney:

Probably one CA would be a good starting point - keeps the internal side of things less complex - at least in the beginning for a GUI interface otherwise you need a method to keep track of what CA is used for which server and client keys. I realize that is not too difficult to do but if you have one CA to each server instance or client instance and someone decides they want to have 100+ VPN clients then things get a little big in terms of the storage for all the keys involved. This would especially be true in an embedded environment.

Good points. Might just start out with one CA and work our way up. I need to view the project specs again, however.

@gmckinney:

One other question - are you still looking at an auto installer for say Windows clients using NSIS ? It looks rather interesting but I have just started looking at it myself - have you done anything with it yet?

Yep.

@gmckinney:

addendum…

It looks like compiling the makensis for pfsense will be a little involved - If I am following the general instructions correctly (http://nsis.sourceforge.net/Docs/AppendixG.html#G) it looks like a pre-compiled version originally for Windows is picked apart so the makensis has access to the Windows specific pieces when the nsis script is "compiled". From what I have figured out this is what is needed to allow creating a Windows installer for an OpenVPN client configuration on a Windows OS based machine - is this a correct interpretation on my part???
It seems this would be the only way to have the installer program create the installation exe with all the parts needed for an OpenVPN client installer.

gm...

I guess. I haven't really looked too closely at it. Sounds like you know more than I do at this point about this portion :)

Accounts

@sullrich:

to utilize it, simply run this command from a shell:

fetch -o - http://www.pfsense.com/~sullrich/tools/easyrsa.txt | /bin/sh

404 file not found…..

sullrich

fetch -o http://files.pfsense.org/extras/easyrsa.txt | /bin/sh

videoman

Has there been any update to this?

I looks like there is a project that may be easy to integrate into PFSense…

http://sourceforge.net/projects/php-ca

Just wondering...

-VideoMan

cwfnetman

What would be very nice would be if someone could port the "Zerina" OpenVPN admin gui package to pfSense. If you don't know what Zerina is, it's a web interface ad-in package for the IPCop and Smoothwall Linux based firewall distros. Zerina makes the creating and managing of OpenVPN road warrior configs, including all the certificates, ip addressing and routing tasks, and all that stuff, trivially easy.

nosborne

Thanks for these scripts, this is working great. Can you include a revoke-full script too? Or is there a revoke option in the pkitool that I'm not seeing?

Thanks!

running

I have finally found how to make that work… took a long time to understand but now i am good (bether) :)

The question of how to revoke is not answered yet can anyone help on how to do that since there is not anything in pkitool and there is no revoke option.

Tank you for your help and patience!

johii

No expert but i think your right, it does look exactly the same as what was in my mind when i read gui for openVPN in pfsense. But with out the pfsense colors ;)

I wouldn't mind working on it, but i wouldn't know where to start :D

running

Anyone as a fix for that? Master sullrich surely as an idea ;)

Thank's

running

Can anyone help? If not in command line can i do it in windows using the revoke-full.bat in windows

Thank you!

nosborne

Updated - I had the syntax wrong, and didn't include my changes to vars. This should be complete now.
–-----------------
I've got this working now, using a revoke-full script and some changes to the vars file. Steps to revoke are: run 'source ./vars' first, then ./revoke-full username, then post the new keys/crl.pem file to the configuration through the GUI.

Here is the script:


#!/bin/sh

# revoke a certificate, regenerate CRL,
# and verify revocation

CRL="crl.pem"
RT="revoke-test.pem"

if [ $# -ne 1 ]; then
    echo "usage: revoke-full <common-name>";
    exit 1
fi

if [ "$KEY_DIR" ]; then
    cd "$KEY_DIR"
    rm -f "$RT"

    # set defaults
    export KEY_CN=""
    export KEY_OU=""

    # revoke key and generate a new CRL
    $OPENSSL ca -revoke "$1.crt" -config "$KEY_CONFIG"

    # generate a new CRL -- try to be compatible with
    # intermediate PKIs
    $OPENSSL ca -gencrl -out "$CRL" -config "$KEY_CONFIG"
    if [ -e export-ca.crt ]; then
        cat export-ca.crt "$CRL" >"$RT"
    else
        cat ca.crt "$CRL" >"$RT"
    fi
fi</common-name>

And the changes to vars:


.
.
# Changes to allow for revoke-full option
setenv KEY_OU "$KEY_ORG"
setenv KEY_CN "my.servername.com"  #This should match the servername in your server cert
setenv PKCS11_MODULE_PATH "$PKCS11TOOL"
setenv PKCS11_PIN "dummy"