The latter course is the subject of my post (hopefully in the next post(s) I could bring good news too). Openvpn is based on machines authenticating themselves to servers which connect to the Internet securely. I have to build up my public key infrastructure PKI to make this possible. In the wiki, it is recommended that the CA issuing machine be different (more entropy capable) from the server and of course the client machines. This path assumes I have more than one machine. What if I only have one?
Openvpn is a flexible and highly configurable software. It says so in the manual:
"OpenVPN is an open source VPN daemon by James Yonan. Because OpenVPN tries to be a universal VPN tool offering a great
deal of flexibility, there are a lot of options..."
"OpenVPN is a robust and highly flexible VPN daemon. OpenVPN supports SSL/TLS security, ethernet bridging, TCP or UDP tun‐
nel transport through proxies or NAT, support for dynamic IP addresses and DHCP, scalability to hundreds or thousands of
users, and portability to most major OS platforms.
OpenVPN is tightly bound to the OpenSSL library, and derives much of its crypto capabilities from it.
OpenVPN supports conventional encryption using a pre-shared secret key (Static Key mode) or public key security (SSL/TLS)."
But what closed the deal for me is this:
"Sample OpenVPN 2.0 config file for #I hope single machine is what it means and I can make this work.
# multi-client server. #
# This file is for the server side #
# of a many-clients <-> one-server #
# OpenVPN configuration. #
# OpenVPN also supports #
# single-machine <-> single-machine #
# configurations (See the Examples page #
# on the web site for more info).