Changes

From SME Server
Jump to navigationJump to search
111 bytes added ,  23:14, 22 March 2009
Line 67: Line 67:  
=== Create a certificate for the server ===
 
=== Create a certificate for the server ===
   −
Now you need to create a certificate for OpenVPN on the server. For this, go in PHPki interface, then "create a new certificate". Here, you'll have to enter some informations about the certificate:
+
Now you need to create a certificate for OpenVPN on the server. For this, go in [[PHPki]] interface, then "create a new certificate". Here, you'll have to enter some informations about the certificate:
   −
**Common Name: this is the name of the certificate. You can enter what you want, for example "openvpn-bridge"
+
**'''Common Name''': this is the name of the certificate. You can enter what you want, for example "openvpn-bridge"
**Email address: the email address of the technical contact (this field is not used, you can enter what you want as long as it's a valid email address), for example admin@domain.tld
+
**'''Email address''': the email address of the technical contact (this field is not used, you can enter what you want as long as it's a valid email address), for example admin@domain.tld
**Organization, Department, Locality, State and Country fields should have the values you entered when you have created your PKI. You can let those values.
+
**'''Organization''', '''Department''', '''Locality''', '''State and Country''' fields should have the values you entered when you have created your PKI. You can let those values.
**Password: '''This field must be blank'''. Remember that OpenVPN daemon starts without human intervention when the server boots, so it need to have access to the certificate key without being prompted for a password.
+
**'''Password''': '''This field must be blank'''. Remember that OpenVPN daemon starts without human intervention when the server boots, so it need to have access to the certificate key without being prompted for a password.
{{Note box|Not filling in a password is NOT possible for all certificate use. Only for VPN Server Only, VPN Client Only, VPN Client or Server and SSL Server}}
+
**'''Certificate life''': How-long the certificate will be valid. Enter what you want, but remember, when the certificate expires, you'll have to create another one, and update it in OpenVPN Bridge panel.
**Certificate life: How-long the certificate will be valid. Enter what you want, but remember, when the certificate expires, you'll have to create another one, and deploy it on each client.
+
**'''Key size''': you can enter what you want (I use 2048 in general). The bigger, the stronger, but will use a bit more CPU power when the session key is negotiated (at the connection, and once an hour)
**Key size: you can enter what you want (I use 2048 in general). The bigger, the stronger, but will use a bit more CPU power when the session key is negotiated (at the connection, and once an hour)
+
**'''Certificate Use''': you should use "VPN Server Only". '''This is important'''. If you don't choose this type of certificates, clients may be enable to connect, or may be enable to proceed as some other certificate uses won't allow an empty password.
**Certificate Use: you should use "VPN Server Only"
      
=== Configure openvpn with the newly created certificates ===
 
=== Configure openvpn with the newly created certificates ===

Navigation menu