OH7LZB VPN: Difference between revisions
(KC8QBA suggests bolding the sentence about the OH7LZB VPN being down.) |
|||
(7 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
The OH7LZB VPN was an experimental method to access the IPIP Mesh using a VPN from anywhere on the Internet. The VPN was openly available to any amateur radio operators who had successfully applied for an X.509 certificate from one of the following Certificate Authorities: | |||
* [http://www.arrl.org/logbook-of-the-world ARRL Logbook of the World (LoTW)] | * [http://www.arrl.org/logbook-of-the-world ARRL Logbook of the World (LoTW)] | ||
<b>As of May, 2024, the OH7LZB VPN appears to no longer be operational.</b> | |||
If and when other organisations start to give out X.509 certificates, after sufficient amateur radio license validation, the | The Certificate Authority (CA) validates using a relatively strong method that the operator is actually licensed, and gives the operator a cryptographic certificate to prove that. Other services, such as this VPN can then check that the operator possesses a valid amateur radio operator certificate (and the accompanying private key), without any manual work being performed by the operators of those services. The operator can use his private key to sign LoTW log files, or any other information he wishes to communicate, and other parties trusting the CA can use the certificate to check that they have been transmitted by someone who has a private key and a certificate for a callsign from the CA. | ||
If and when other organisations start to give out X.509 certificates, after sufficient amateur radio license validation, the VPN will be configured to accept those in addition to the LoTW. If you're not willing to obtain a LoTW certificate, please set up a CA for your local club or association, document the method of license validation you're using, and I'll be happy to trust your certificates. | |||
The VPN operator (Hessu, OH7LZB) does not have time to run a CA and validate licenses manually, so please don't ask for a certificate from anywhere else than the CAs listed above. Thanks! | The VPN operator (Hessu, OH7LZB) does not have time to run a CA and validate licenses manually, so please don't ask for a certificate from anywhere else than the CAs listed above. Thanks! | ||
The | The VPN is only used to access the IPIP Mesh. While you're connected to the VPN, the VPN client will only transmit packets from you to the IPIP Mesh via the VPN. Packets from you to the rest of the Internet will not go via the VPN - they'll flow out from your local network connection as before. This is called a [http://en.wikipedia.org/wiki/Split_tunneling split tunnel VPN configuration]. | ||
The setup is still a bit complicated - it can be made easier and more automatic with a little additional software in a later phase. | The setup is still a bit complicated - it can be made easier and more automatic with a little additional software in a later phase. | ||
The | The VPN is an experimental service. It might be shut down for technical or political reasons - we'll see if it's a feasible idea or not. | ||
= Getting a certificate from LoTW = | = Getting a certificate from LoTW = | ||
Go through [ | Go through [https://lotw.arrl.org/lotw-help/getting-started/ these simple steps]. After step 4 you're ready to continue with the VPN. | ||
It's going to take some time to validate, and you'll have to do some manual work (especially if you're outside the USA), but that is intentional. It significantly reduces abuse of the system, and increases its security. | It's going to take some time to validate, and you'll have to do some manual work (especially if you're outside the USA), but that is intentional. It significantly reduces abuse of the system, and increases its security. | ||
Line 74: | Line 76: | ||
Copy-paste that block to a separate file named '''client.key'''. If you're going to open up the original private key file in a text editor, it's a good idea to make a backup copy of that file first in case of an accidental corruption of its contents. | Copy-paste that block to a separate file named '''client.key'''. If you're going to open up the original private key file in a text editor, it's a good idea to make a backup copy of that file first in case of an accidental corruption of its contents. | ||
= Configuring | = Configuring the VPN = | ||
== Windows: OpenVPN == | == Windows: OpenVPN == | ||
Line 93: | Line 95: | ||
== Linux: OpenVPN == | == Linux: OpenVPN == | ||
... | === Ubuntu 15.10 === | ||
Here is steps to install the VPN to Ubuntu 15.10 destop. Install OpenVPN plugin to network manager. | |||
Open terminal and type | |||
sudo apt-get install network-manager-open vpn-gnome | |||
Then add VPN-connection information to NetworkManager | |||
# Click network manager icon on taskbar | |||
# Edit connections | |||
# Add | |||
# OpenVPN | |||
# Create | |||
#* Connection name: AMPRNet | |||
#* Gateway: amprnet-vpn1.aprs.fi | |||
#* Select proper files to User Certificate, CA certificate and Private key | |||
#* Optionally enter private key password if you are set one | |||
# Click Advanced | |||
#* [x] Use custom gateway port: 1773 | |||
#* [x] Use LZO data compression | |||
# Click OK | |||
# Click Save | |||
# Click Close | |||
Now you can connect to VPN | |||
# Click network manager icon on taskbar | |||
# VPN connections -> AMPRNet | |||
# Connection should be established | |||
== Linux (Raspberry PI): OpenVPN == | == Linux (Raspberry PI): OpenVPN == | ||
Line 129: | Line 160: | ||
== Mac OS X: Tunnelblick == | == Mac OS X: Tunnelblick == | ||
# [ | # [https://tunnelblick.net/ Download Tunnelblick], it's free and open source, and works like a charm. It's based on OpenVPN. | ||
# [http://he.fi/amprnet-vpn/amprnet-vpn-tblk.zip Download the | # [http://he.fi/amprnet-vpn/amprnet-vpn-tblk.zip Download the VPN configuration for Tunnelblick], it's a zip file containing a directory with a couple files | ||
# Double-click the downloaded zip file to extract it, you'll get a directory named '''amprnet-vpn.tblk''' | # Double-click the downloaded zip file to extract it, you'll get a directory named '''amprnet-vpn.tblk''' | ||
# Move the '''private key''' (in a file which was named '''client.key''' in the previous step) to that directory | # Move the '''private key''' (in a file which was named '''client.key''' in the previous step) to that directory |
Latest revision as of 12:03, 4 May 2024
The OH7LZB VPN was an experimental method to access the IPIP Mesh using a VPN from anywhere on the Internet. The VPN was openly available to any amateur radio operators who had successfully applied for an X.509 certificate from one of the following Certificate Authorities:
As of May, 2024, the OH7LZB VPN appears to no longer be operational.
The Certificate Authority (CA) validates using a relatively strong method that the operator is actually licensed, and gives the operator a cryptographic certificate to prove that. Other services, such as this VPN can then check that the operator possesses a valid amateur radio operator certificate (and the accompanying private key), without any manual work being performed by the operators of those services. The operator can use his private key to sign LoTW log files, or any other information he wishes to communicate, and other parties trusting the CA can use the certificate to check that they have been transmitted by someone who has a private key and a certificate for a callsign from the CA.
If and when other organisations start to give out X.509 certificates, after sufficient amateur radio license validation, the VPN will be configured to accept those in addition to the LoTW. If you're not willing to obtain a LoTW certificate, please set up a CA for your local club or association, document the method of license validation you're using, and I'll be happy to trust your certificates.
The VPN operator (Hessu, OH7LZB) does not have time to run a CA and validate licenses manually, so please don't ask for a certificate from anywhere else than the CAs listed above. Thanks!
The VPN is only used to access the IPIP Mesh. While you're connected to the VPN, the VPN client will only transmit packets from you to the IPIP Mesh via the VPN. Packets from you to the rest of the Internet will not go via the VPN - they'll flow out from your local network connection as before. This is called a split tunnel VPN configuration.
The setup is still a bit complicated - it can be made easier and more automatic with a little additional software in a later phase.
The VPN is an experimental service. It might be shut down for technical or political reasons - we'll see if it's a feasible idea or not.
Getting a certificate from LoTW
Go through these simple steps. After step 4 you're ready to continue with the VPN.
It's going to take some time to validate, and you'll have to do some manual work (especially if you're outside the USA), but that is intentional. It significantly reduces abuse of the system, and increases its security.
Extracting the certificate from LoTW
LoTW uses a custom file format (.TQ*) to exchange certificates, but after the LoTW certificate process is done and the TrustedQSL software has your certificates, they can be easily copied from TrustedQSL's directories. You'll need three files: your user certificate, an intermediate certificate that was used to sign it, and your private key. The only secret piece of information is the private key - you should not reveal it to anyone at any point, as they could then use services on your behalf, using your callsign.
Windows
- C:\Documents and Settings\your-username\Application Data\TrustedQSL contains two directories, certs and keys.
- certs\user contains the user certificate
- certs\authorities contains an intermediate certificate
- keys\YOURCALL contains, within some XML, your private key
Make copies of those files in another directory, and work on those copies in order to avoid breaking the originals.
The user and intermediate certificates need to be concatenated to a single file named client.crt. The user certificate must be first, followed by the intermediate certificate. That can be done by an ascii editor such as Notepad (Wordpad or Word is likely to mess it up in a big way).
The private key needs to be extracted from the YOURCALL file. The file is a regular ASCII text file, and contains a block which looks something like this (just longer):
-----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,0C7B5495F6A91F31 0xmWfliK/v9U88MFyYtUbteRoAkfVMK6BllcdID3pZzmdykHaPLZUjXOCUh3vFUX 1bjnYwXpLX/CxgZ6NIxQIk7jMjL3iaP5SkWzCswqi9mCO+zHxuS6PWq7YwbWNFgo 7smNcko1yTp7f/VbS4CZ5kgIF9kCgNaiqdxq+v0IcphQHRR4xjfLpBQ4ckYOi4nC jqFR1BitwBL4K2JeE9PGUkkUBwvU4oOi9PGChuoxMXs8PwKi/dZTmSWM7kOfMiBw -----END RSA PRIVATE KEY-----
Copy-paste that block to a separate file named client.key.
Linux and Mac
- ~/.tqsl/certs/user contains the user certificate
- ~/.tqsl/certs/authorities contains an intermediate certificate
- ~/.tqsl/keys/YOURCALL contains, within some XML, your private key
The user and intermediate certificates need to be concatenated to a single file named client.crt. The user certificate must be first, followed by the intermediate certificate. That can be done by a single command:
cat ~/.tqsl/certs/user ~/.tqsl/certs/authorities > client.crt
The private key needs to be extracted from the YOURCALL file. The file is a regular ASCII text file, and contains a block which looks something like this (just longer):
-----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,0C7B5495F6A91F31 0xmWfliK/v9U88MFyYtUbteRoAkfVMK6BllcdID3pZzmdykHaPLZUjXOCUh3vFUX 1bjnYwXpLX/CxgZ6NIxQIk7jMjL3iaP5SkWzCswqi9mCO+zHxuS6PWq7YwbWNFgo 7smNcko1yTp7f/VbS4CZ5kgIF9kCgNaiqdxq+v0IcphQHRR4xjfLpBQ4ckYOi4nC jqFR1BitwBL4K2JeE9PGUkkUBwvU4oOi9PGChuoxMXs8PwKi/dZTmSWM7kOfMiBw -----END RSA PRIVATE KEY-----
Copy-paste that block to a separate file named client.key. If you're going to open up the original private key file in a text editor, it's a good idea to make a backup copy of that file first in case of an accidental corruption of its contents.
Configuring the VPN
Windows: OpenVPN
- Download the Windows Installer, it's free and open source.
- Run the installer to install it.
- Download the AMPRNet VPN configuration files for Windows
- Open up the zip file, it contains two files: amprnet-vpn.ovpn and amprnet-vpn-ca.crt.
- In Start menu, under OpenVPN => Shortcuts you'll find an entry named OpenVPN configuration file directory. Open it, and move the two files from the zip to the configuration file directory.
- Place client.crt and client.key, which were created previously, in the configuration file directory.
- Run the OpenVPN GUI from the desktop icon or start menu. A new icon will appear in the lower right corner (two computers with red screens + a globe on the side).
- Right-click the OpenVPN toolbar icon and select Connect.
If you chose to encrypt your private key with a password (or passphrase) when initially applying for a LoTW certificate and generating the Certificate Request, OpenVPN will ask you for that password when connecting.
To rephrase: When OpenVPN says "Enter Password", the password being asked is the one you picked when you first applied for a LoTW certificate. It's not something the VPN operator knows (or should know). It's not the one you got on a postcard. Only you have ever been aware of that password (hopefully).
Linux: OpenVPN
Ubuntu 15.10
Here is steps to install the VPN to Ubuntu 15.10 destop. Install OpenVPN plugin to network manager. Open terminal and type
sudo apt-get install network-manager-open vpn-gnome
Then add VPN-connection information to NetworkManager
- Click network manager icon on taskbar
- Edit connections
- Add
- OpenVPN
- Create
- Connection name: AMPRNet
- Gateway: amprnet-vpn1.aprs.fi
- Select proper files to User Certificate, CA certificate and Private key
- Optionally enter private key password if you are set one
- Click Advanced
- [x] Use custom gateway port: 1773
- [x] Use LZO data compression
- Click OK
- Click Save
- Click Close
Now you can connect to VPN
- Click network manager icon on taskbar
- VPN connections -> AMPRNet
- Connection should be established
Linux (Raspberry PI): OpenVPN
Log in to Raspberry Pi console. Install openvpn software.
sudo apt-get install openvpn
Create openvpn client configuration file with your favourite editor to /etc/openvpn/client.conf
client dev tun proto udp remote amprnet-vpn1.aprs.fi 1773 resolv-retry infinite persist-key persist-tun ca amprnet-vpn-ca.crt cert client.crt key client.key comp-lzo verb 3
Extract your client certificate and key as explained above section Extracting the certificate from LoTW. Copy your certificate files client.crt and client.key to /etc/openvpn/ . You also need amprnet-vpn-ca.crt which can be found inside this archive http://he.fi/amprnet-vpn/amprnet-vpn-win.zip . Extract it and copy to /etc/openvpn/
Restart openvpn
service openvpn restart
All done.
Mac OS X: Tunnelblick
- Download Tunnelblick, it's free and open source, and works like a charm. It's based on OpenVPN.
- Download the VPN configuration for Tunnelblick, it's a zip file containing a directory with a couple files
- Double-click the downloaded zip file to extract it, you'll get a directory named amprnet-vpn.tblk
- Move the private key (in a file which was named client.key in the previous step) to that directory
- Move the certificates (in a file which was named client.crt in the previous step) to that directory
- Double-click the amprnet-vpn.tblk directory - this will launch Tunnelblick and install the VPN configuration
You should now see a "tunnel" icon in the top right corner of the screen. Click it to see a few menu items allowing you to connect and disconnect the VPN.
If you chose to encrypt your private key with a password (or passphrase) when initially applying for a LoTW certificate and generating the Certificate Request, Tunnelblick will ask you for that passphrase when connecting.
To rephrase: When Tunnelblick says "A passphrase is required to connect to amprnet-vpn", the passphrase being asked is the one you picked when you first applied for a LoTW certificate. It's not something the VPN operator knows (or should know). Only you have ever been aware of that passphrase (hopefully).