"arguing that you don’t care about the right to privacy because you have nothing to hide is no different than saying you don’t care about free speech because you have nothing to say."
– solar charged – battery powered – low temp Li-ion charge cutoff – low power – no gps module due to fixed location – advantageous location – reliable/durable – medium gain antenna
Materials:
Soldering iron. Whatever you have should work, no fancy soldering required
JST ZH1.5mm 2PIN Micro Electrical Male and Female Connector Plug with 150mm Wire Cables **this is only needed if you want to bypass the low temp charge controller and plug in direct to the onboard RAK solar plug** https://www.amazon.com/dp/B0B58M7D49
The Rak Wisblock is the perfect choice for a repeater. Its low power, modular and extremely reliable. You can purchase the starter kit which comes with the base board (RAK19007) and the Lora + bluetooth chip (RAK4631). It comes with PCB antennas (0.8dBi) that we won’t use for this fixed repeater. Always keep the antennas connected before powering the radio! Lack of antenna load will result in damage to the radio chip.
Lets start by setting up the Rak wisblock for Meshtastic firmware
locate the firmware file for the wisblock 4631. Its called “firmware-rak4631-2.3.10.d19607b.uf2” (replace the 2.3.10…. with whatever fw version your using)
plug the wisblock into your computer and double tap the button shown below.
This will expose a mountable filesystem that you can copy the firmware image into.
copy “firmware-rak4631-2.3.10.d19607b.uf2” onto the RAK4631 mount point. It might have current.uf2, index.htm and info_uf2.txt, don’t mess with those. Just copy and paste the “firmware-rak4631-2.3.10.d19607b.uf2” file into the RAK4631 partition. The green light will flash while its transferring and it will reboot when done. The firmware is now loaded and we move onto programming the radio with meshtastic software.
We will use pip to install meshtastic and create a python virtual environment to control the version of binaries and all the dependencies needed. These instructions are for Debian, of course ;-)
Enter the virtual environment and install meshtastic esptool and all its dependencies
source python/bin/activate
pip install --upgrade esptool meshtastic
Anytime in the future when you need to use meshtastic you will enter the python virtual environment with
source meshtastic/python/bin/activate
This way you can control the versions of meshtastic and esptool without affecting any other versions of the python scripts, binaries and dependencies on your system.
Now we can program the RAK radio
to see whats currently programmed run
meshtastic --info
If this radio has been used before or you want to be sure of a blank slate run a factory reset
meshtastic --factory-reset
Now the radio can be setup from scratch. “Region US” sets the radio up for use in the USA at 915mhz
meshtastic --set lora.region US
set the name of this node
meshtastic --set-owner [name]
I like to set a preset bluetooth pin so I can easily access it locally over bluetooth from android phone using the meshtastic app.
Since this wisblock does not have the gps module (since its fixed location and conserves power) you will need to set its location manually. You can add a GPS module with the RAK12500 GNSS GPS Location Module.
Add a admin channel to this repeater so you can remotely administer the hardware. Unfortunately, this admin channel needs to be added to both nodes in order for administration features to work. This means that if someone physically gains access to this device they will have access to your channels encryption key and the admin key. So communications can be decrypted and they can remotely administer other nodes that have this admin channel.
And finally the channels URL. These URL’s hold the encryption key and name of the channel. Use these to add future devices to the mesh. The last “Complete URL” additionally contains the admin channel so only use that for nodes that you want to use for remote administration and devices that you want to be able to remotely administer. I will go over client configs later in this post using a tbeam.
Primary channel URL: https://meshtastic.org/e/#Ci4SIDHMn8GX074n_yIOik3-c1l9CccxXWCzyXimIvdZYcaQGgZmYW1pbHk6AgggEgoIAUADSAFQHmgB
Complete URL (includes all channels): https://meshtastic.org/e/#Ci4SIDHMn8GX074n_yIOik3-c1l9CccxXWCzyXimIvdZYcaQGgZmYW1pbHk6AgggCikSIMOYnWI3socNXuYxy-RI40Lg8BB-oqmXJEm814GTUnxgGgVhZG1pbhIKCAFAA0gBUB5oAQ
copy and paste the channel URL’s into your notes, for later.
Now we move on to the hardware needed to turn this into a robust, long term outdoor repeater
The RAK repeater is very tolerant to extreme temperatures but the li-ion battery is not so forgiving. It is sensitive to very hot and cold conditions. The most limiting factor is charging li-ion in freezing conditions. This will quickly destroy a battery. To help minimize temperature swings I opted for a larger container with some insulation to smooth out the hot and cold transitions. This case was cheap, insulated and decent quality. So far its survived a few years in the harshest of conditions. https://www.harborfreight.com/brands/apache/1800-weatherproof-protective-case-small-black-64550.html
This case is not enough to keep the battery above freezing. Winter months are long and very cold and my batteries would get trashed within a few months of use in winter conditions. To solve this problem I used a low temp-cutoff charge controller from adafruit. https://www.adafruit.com/product/4755 in conjunction with a 10k thermistor https://www.adafruit.com/product/372
This charge controller is far superior to the internal charge controller of the RAK and with the added low temp cutoff I haven’t had to replace a battery since.
== Roaming mobile nodes ==
Requisites:
– Small/portable – low power – battery powered – GPS – waterproof – low gain antenna – easily re-charged (usb)
Wireguard is a wonderfully superior VPN. Its simple, fast, lightweight, modern, GPL licensed and very secure. Read more at Wireguard.com
Here is the setup:
10.11.13.0/24 is the home lan subnet with 10.11.13.1 as the OpenWRT gateway/router (v19.07.4). 172.21.13.0/24 is a public vlan that we will setup to route over the vpn. 10.11.14.0/24 is the wireguard subnet with 10.11.14.1 as the Wireguard interface (wg0). Each wireguard client will be assigned an address between 10.11.13.2-254
Begin by installing the required packages on the OpenWRT gateway (Alternately, this can be done from Luci. System -> Software) ssh root@10.11.13.1 opkg update opkg install luci-app-wireguard wireguard wireguard-tools Add a new interface for Wireguard. From the Luci interface go to “Network -> Interfaces -> Add New interface”. Call it wg0
Generate a public/private key for the server using the wg utility wg genkey | tee [name].privatekey | wg pubkey > [name].publickey For example: wg genkey | tee mywgserver.privatekey | wg pubkey > mywgserver.publickey
Create the Wireguard interface. Add the private key from above listen port 51820 ip 10.11.14.1/24 keep alive of 25
Optionally, add the following to /etc/config/network
config interface 'wg0'
option proto 'wireguard'
option private_key 'QFLJ9p7MFz31DxTqNKCTu2ARhxLvN0lWhvoKarBT2Vg='
option listen_port '51820'
list addresses '10.11.14.1/24'
Create a firewall zone for the wg0 interface and allow forwarding to and from the lan and public zones. As well as allow it to forward to the wan zone. This is needed when routing all traffic through the vpn. Network -> Firewall -> Add (zone)
Optionally, add the following to /etc/config/firewall
config zone
option name 'wg'
option input 'ACCEPT'
option network 'wg0'
option output 'ACCEPT'
option forward 'REJECT'
config forwarding
option dest 'lan'
option src 'wg'
config forwarding
option dest 'public_zone'
option src 'wg'
config forwarding
option dest 'wg'
option src 'lan'
config forwarding
option dest 'wg'
option src 'public_zone'
config forwarding
option dest 'wan'
option src 'wg'
We need to open up the Wireguard port in the firewall. You can use any port you like. I’m using the default (51820). Network -> Firewall -> Traffic Rules -> Add Change the following, leaving everything else default Name: wan-local-wg Protocol: UDP Source zone: wan Destination zone: Device Destination port: 51820
Optionally, add a firewall rule to /etc/config/firewall
config rule
option dest_port '51820'
option src 'wan'
option name 'wan-local-wg'
option target 'ACCEPT'
list proto 'udp'
Now lets setup a peer (client).
Generate a public private keypair wg genkey | tee jason.privatekey | wg pubkey > jason.publickey
– Add a description: jason – Paste the public key: N6bm45DTywv+dvTK5FRk47Agil+n+k5N0JyaOvfL7iw= – Add a Preshared Key if you are worried about quantum computing compromising your keypair sometime in the future. – Set “Allowed IPs” to an ip inside the wireguard subnet (10.11.14.0/24). For this peer we will use 10.11.14.10/32. If you add another peer this address will need to be unique. So the next peer can use .11/32. Wireguard uses a ip to pubkey mechanism called cryptokey routing. In this case any traffic destined for 10.11.14.10 will be encrypted with this peers public key “…L7iw=” and sent to its most recent endpoint address. – Change the “Persistent Keep Alive” to 25 seconds, which is recommended for traversing NAT. If your not behind NAT leave it blank.
Optionally, you can add a peer directly to /etc/config/network
After adding a peer the wg0 interface needs to be restarted!
Now we are ready connect as a peer to this server. This can be done a number of ways. Wireguard has adopted a modular model like most GNU projects. They don’t concern themselves with the configuration or key distribution. Here is a quote from the project “WireGuard securely encapsulates IP packets over UDP. You add a WireGuard interface, configure it with your private key and your peers’ public keys, and then you send packets across it. All issues of key distribution and pushed configurations are out of scope of WireGuard; these are issues much better left for other layers, lest we end up with the bloat of IKE or OpenVPN“
There are a few client connection options. You can do this manually (or scripted) using ip and wg or there is a helper script called wg-quick. This is part of the wireguard-tools package on Debian. I recommend wg-quick because its easy and slick. Create a config file called something like jasonvpn.conf either in your home directory someplace or in /etc/wireguard/ I prefer the vpn config in my home directory. I place mine in a directory called ~/wg/ Here is the client config with some options commented out (#) for reference. Save this to a file called whatever.conf and run wq-quick up whatever.conf
[Interface]
Address = 10.11.14.10/32
PrivateKey = OHs907NqGJD1NWY2yvrGjhYvNju48Q+E8/nnSy4jKmE=
#DNS = 10.11.14.1
[Peer]
PublicKey = LOXb3qL66NfFMWim9tQP+RhWsEVpnlQpm1kpcpJsYHU=
Endpoint = [wireguard server IP or hostname]:51820
#AllowedIPs = 0.0.0.0/0, ::/0
AllowedIPs = 10.11.13.0/24, 172.21.13.0/24
# This is for if you're behind NAT
PersistentKeepalive = 25
Take note that the [Peer] PublicKey is the servers (openwrt gateway) public key and the [Interface] PrivateKey is the private key we generated for Jason. The corresponding public key for Jason is what we added to the servers Peer section.
The above “AllowedIPs” will allow for split tunnel, where the client can connect to remote subnet 10.11.13.0/24 and 172.21.13.0/24 and any other traffic will route out of their default gateway. If you want to route all traffic through the vpn then set “AllowedIPs = 0.0.0.0/0, ::/0”
Wireguard uses some fancy routing features of iproute2. Containers, Namespaces, and using fwMark to solve deficiencies of the old routing methods. Lets test the above whatever.conf connection. Instead of calling it whatever.conf I have called it vv.conf and saved it in ~/wg/ Now lets start the vpn
sudo wg-quick up wg/vv.conf
Warning: `/home/jason/wg/vv.conf' is world accessible
[#] ip link add vv type wireguard
[#] wg setconf vv /dev/fd/63
[#] ip -4 address add 10.11.14.10/32 dev vv
[#] ip link set mtu 1420 up dev vv
[#] ip -4 route add 172.21.13.0/24 dev vv
[#] ip -4 route add 10.11.13.0/24 dev vv
This is a concise tutorial, it is not meant to be a hand holding step by step guide. Please comment or contact me if you find errors.
Prerequisites: Setup a domain/sub domain with an A record to the ip of the server or a CNAME to a “dynamic DNS” hostname. I recommend https://freedns.afraid.org. The server needs to have ports 80 and 443 reachable to the public. The DNS must be propagated for letsencrypt to be successful.
Make sure the md5 matches md5sum latest-22.tar.bz2 curl https://download.nextcloud.com/server/releases/latest-22.tar.bz2.md5
Extract the tar file and change permissions tar xfv nextcloud-22.x.tar.bz2 mv nextcloud/ /var/www/example.com/ chown www-data:www-data -R /var/www/example.com/
Setup Apache
Create a apache virtual site cp /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/example.com.conf
edit /etc/apache2/sites-available/example.com.conf uncomment and change “ServerName example.com“
change the document root DocumentRoot /var/www/html/example.com
change log location if you would like ErrorLog ${APACHE_LOG_DIR}/example.com_error.log
CustomLog ${APACHE_LOG_DIR}/example.com_access.log combined
a2ensite example.com
a2enmod php7.4 rewrite headers env dir mime userdir dav ssl
<Directory /var/www/example.com/>
Require all granted
AllowOverride All
Options FollowSymLinks MultiViews
<IfModule mod_dav.c>
Dav off
</IfModule>
</Directory>
To avoid certain race conditions between the /etc/apache2/sites-available/example.com.conf and /etc/apache2/sites-available/000-default.conf I prefer to remove example.com.conf and move the http->https redirect into the 000-default.conf
cat /etc/apache2/sites-available/example.com.conf
….snip… # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with “a2disconf”. #Include conf-available/serve-cgi-bin.conf RewriteEngine on RewriteCond %{SERVER_NAME} =example.com RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
copy the rewrite rule at the bottom:
RewriteEngine on
RewriteCond %{SERVER_NAME} =example.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
edit and paste into the default conf
vi /etc/apache2/sites-enabled/000-default.conf
Create a database, user and password for nextcloud
mariadb -uroot
CREATE USER 'nextcloud'@'localhost' IDENTIFIED BY 'PASSWORD';
CREATE DATABASE IF NOT EXISTS nextcloud;
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES ON nextcloud.* TO 'nextcloud'@'localhost';
FLUSH privileges;
The reason I use x11vnc is that it connects to the existing graphical session. Most other vnc servers will spawn an entirely new graphical session. While that is super cool, I don’t want that feature. This is for remote support, where I want the user and the supporter to share the same session. I use the ‘-auth guess’ to have x11vnc guess the XAUTHORITY file‐name and use it appropriately. This avoids the annoying hard coding of gdm, lightdm, xdm or specific users .Xauthority.
Install x11vnc # apt-get install x11vnc
The following should work for any distro that uses systemd, just the apt bits are Debian specific.
Generate the password and store it under etc so no users can change this password, only root. You can do this under your users home so that its not managed by root. In my case I didn’t want the user to be able to change or accidentally delete the password. # x11vnc -storepasswd /etc/x11vnc.pwd
edit (create new) the following file use whatever text editor you prefer, here I use vi # vi /etc/systemd/system/x11vnc.service
And add the following, making any changes you want to the x11vnc ExecStart See the man page for explanations of the switches
The new versions of OpenWRT (18 and newer) have the ability to add vlan interfaces directly from LuCI (web gui). You can now skip the manual editing of the /etc/config/network file.
Using 802.1q in OpenWRT is very difficult when working on a device that doesn’t have a built-in switch or the when the switch chipset isn’t supported.
Creating VLANS is not possible via the web interface (luci) or using the “config switch_port” options in /etc/config/network. The Luci web gui will not have the “Network -> Switch” option available.
In this example, we add a public interface and vlan 2 on ports eth0 and eth1.
Start by getting into the device: ssh root@192.168.1.1 vi /etc/config/network
config interface 'public'
option type 'bridge'
option proto 'static'
option ifname 'eth0.2 eth1.2'
option ipaddr '172.168.1.1'
option netmask '255.255.255.0'
config device 'eth0_2'
option name 'eth0.2'
config device 'eth1_2'
option name 'eth1.2'
This creates three interfaces eth0.2, eth1.2 and both are bridged into the interface br-public.
You can use luci to configure the interface if you use the “custom interface” and manually refer to the vlan like this:
Just be sure you’ve already added the necessary VLAN to /etc/config/network:
config device 'eth0_2'
option name 'eth0.2'
After this, the VLAN will be defined but not show up in luci. You will need to specify it using the “custom interface” as shown in the red circle above.
I have many open-mesh OM1P units laying around from failed wireless projects. Needless to say I’m not a big fan of open-mesh and have some other projects in mind for this hardware. It was a painful process but well worth it. Now I have nice little OpenWRT units for any hacking pleasure.
I have made a concise synopsis of the openwrt wiki page for flashing proper firmware on the OM1p/Fon/Fonera/Accton/etc. Please visit http://wiki.openwrt.org/toh/fon/fonera#openwrt for more detail.
download linux onto the om1p:
RedBoot> load -r -b %{FREEMEMLO} openwrt-atheros-vmlinux.lzma
Using default protocol (TFTP)
Raw file loaded 0x8003f800-0x8011f7ff, assumed entry at 0x8003f800
initialize the current flash partition, this will erase openmesh firmware, yay!:
RedBoot> fis init
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
Now flash the kernel image to memory:
RedBoot> fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7
... Erase from 0xa8030000-0xa8110000: ..............
... Program from 0x8003f800-0x8011f800 at 0xa8030000: ..............
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
Now load the rootfs:
RedBoot> load -r -b %{FREEMEMLO} openwrt-atheros-root.squashfs
Using default protocol (TFTP)
Raw file loaded 0x8003f800-0x8021f7ff, assumed entry at 0x8003f800
And then flash the rootfs:
RedBoot> fis create rootfs
... Erase from 0xa8110000-0xa82f0000: ..............................
... Program from 0x8003f800-0x8021f800 at 0xa8110000: ..............................
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
Reboot the om1p:
RedBoot> reset
You will see OpenWRT booting and creating filesystems and such.
...
jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
jffs2_build_filesystem(): unlocking the mtd device... done.
jffs2_build_filesystem(): erasing all blocks after the end marker... done.
mini_fo: using base directory: /
mini_fo: using storage directory: /overlay
BusyBox v1.15.3 (2011-11-24 02:38:24 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
Backfire (10.03.1, r29592) ------------------------
* 1/3 shot Kahlua In a shot glass, layer Kahlua
* 1/3 shot Bailey's on the bottom, then Bailey's,
* 1/3 shot Vodka then Vodka.
---------------------------------------------------
root@OpenWrt:/#
Now we need to set a heartbeat for the hardware watchdog otherwise the om1p reboots every 5 minutes.
In this scenario we will be implementing a openWRT as a wireless access point only. One wireless essid will be LAN accessible and the other will be segregated from the LAN but able to access the WAN. The openWRT in this example will not be the gateway to the network. Another device is the gateway and there is an existing dhcp server.
PUBLIC wifi
172.16.134.0/24
|
public gateway and dhcp server
172.16.134.1
\
Source NAT to 10.101.101.10
\
ISP <-Gateway-> LAN wired 10.101.101.0/24 <-openWRT->
/
LAN wifi (wpa2+aes)
10.101.101.0/24
1. Add a new wireless access point
2. Settings for the new wireless access point. Create a new network interface of “public”. Don’t use any encryption, as this is for general public use.
3. Edit network interface for the public network
4. Edit PUBLIC interface settings. Set to static address and enable DHCP server for this new network.
5. Edit the LAN interface. Set the lan interface to an un-used ip of the existing network. Don’t set to “dhcp client” as you will lose connectivity and need to perform a recovery on your openwrt device. Be sure to disabled the DHCP server as the existing network already has one.
6. Add a new zone and call it “public_zone”. Masquarade it and put it in the public network. Allow forwarding to and from “lan” zone. We will limit this later with specific firewall rules.
7. This is what the general firewall zones should look like
8. Under the Firewall -> Traffic Rules section add a new Source NAT Rule. Call it “pub2lan“. Set the “Source zone” to “public_zone” and the “Destination zone” to “lan” and set the drop down option “To source IP” to br-lan interface, in this example its 10.101.101.10. Leave “To source port” blank. This SNAT rule will translate all traffic on the public wireless network of 172.16.134.0/24 into the IP of 10.101.101.10. This is the redirect rule from /etc/config/firewall
config redirect
option target 'SNAT'
option src 'public_zone'
option dest 'lan'
option proto 'all'
option name 'pub2lan'
option src_dip '10.101.101.10'
option enabled '1'
9. Setup a “New forward rule:” Set name to allow2gw or similar. Source zone to “public_zone” Destination zone to “lan” Click “Add and edit…” Protocols should be “Any”, Destination address is the gateway of the network. In this case 10.101.101.1. The following is the /etc/config/firewall rule for reference. This will allow traffic from the public_zone to reach the gateway of the network.
config rule
option target 'ACCEPT'
option proto 'all'
option name 'allow2gw'
option src 'public_zone'
option dest 'lan'
option dest_ip '10.101.101.1'
10. Setup a “New forward rule”. Set the name to drop2lan or similar. Set the Source zone to “public_zone” and Destination zone to “lan”. Click “Add and edit…” Set Protocol to “Any”, Destination address to custom and enter the subnet of the LAN. In this case its 10.101.101.0/24, set “Action” to “drop”. You can add more rules like this one to limit access to other networks or hosts as needed.
config rule
option name 'drop2lan'
option src 'public_zone'
option proto 'all'
option target 'DROP'
option dest 'lan'
option dest_ip '10.101.101.0/24'
11. Firewall Traffic Rule overview. There is an error on this view. The following rules have “option proto ‘all’” set and the luci web interface shows “Any TCP+UDP”. This is simply a bug in the luci interface and can be ignored. The order of these rules is very important. In this case you can see we added the “Allow to 10.101.101.1” before the “Drop to 10.101.101.0/24”. If reversed, the lan including the gateway would not be accessible from the public wireless AP. Therefore, you would not be able to reach the Internet.
That said, if you want to setup pptp on the openwrt here is a guide.
The router is Backfire 10.03.1 at address 192.168.11.1/24. This configuration will setup the PPtP VPN server and it should be pointed out that its not a very secure VPN. Basically, it requires that someone capture the authentication handshake of a pptp connection. Then extract the keys and crack the hashes or bruteforce. There is a service that was released last year that will crack these keys and produce the authentication hash, that can auth as the password. This was done to encourage people to stop using this lame technology. Here is a great write up that will answer all questions https://www.cloudcracker.com/blog/2012/07/29/cracking-ms-chap-v2/
With the above insecurity disclaimer and a note that this really shouldn’t be used for anything requiring real security. I proceed..
debug
logfile /tmp/pptp-server.log
192.168.11.1:
auth
name "pptp-server"
lcp-echo-failure 3
lcp-echo-interval 60
default-asyncmap
mtu 1482
mru 1482
nobsdcomp
nodeflate
proxyarp #required to be able to connect to the lan subnet without being directly connected.
#noproxyarp
#nomppc
mppe required,no40,no56,stateless
require-mschap-v2
refuse-chap
refuse-mschap
refuse-eap
refuse-pap
ms-dns 192.168.11.1
== /etc/ppp/chap-secrets ==
#USERNAME PROVIDER PASSWORD IPADDRESS
jason * testypass *
== /etc/firewall.user ==
# This file is interpreted as shell script.
# Put your custom iptables rules here, they will
# be executed with each firewall (re-)start.
# Allow all traffic in and out of the ppp interface. No reason to specify nets.
iptables -A input_rule -i ppp+ -j ACCEPT
iptables -A output_rule -o ppp+ -j ACCEPT
# This rule will allow traffic towards internet
iptables -A forwarding_rule -i ppp+ -j ACCEPT
UPDATE: The easiest way to do this is through the web interface (LuCI). System -> Administration -> SSH-Keys. Paste your public key (~/.ssh/id_rsa.pub) and click “Add key”
I’ve been using so many openwrt devices lately I wanted to setup my public ssh key on each device so I can auto login. Also, I can setup a really unfriendly password for the root account that is very secure and use my public key to authenticate. Convenient and secure? What a concept!!
Since this is dropbear and not openssh the typical ~/.ssh/authorized_keys file doesn’t work. Instead you need the authorized_keys file to be in /etc/dropbear/
This is how I do it quickly and efficiently.
Using the ssh-copy-id command to copy your public key to the remote devices authorized_keys. This is the same you would do to copy your public key to your server or such. Thanks to Sam for turning me onto this most valuable tool.
From your local user account (must have a public/private key, see ssh-keygen if you need to generate keys)
$ ssh-copy-id root@192.168.1.1
enter current password, the following will display if you entered password correctly
Now try logging into the machine, with "ssh 'root@192.168.1.1'", and check in:
~/.ssh/authorized_keys
to make sure we haven't added extra keys that you weren't expecting.
now ssh to the device and move the authorized_keys to dropbear directory
logout and ssh back to 192.168.1.1. This time it will ask for your ssh key passphrase instead of the root password. $ ssh root@192.168.1.1
Enter passphrase for key ‘/home/jason/.ssh/id_rsa’:
If you would like to login without ssh asking for your passphrase you can use ssh-agent to store your identity. Use ssh-add to add to ssh-agent.
$ ssh-add
Enter passphrase for /home/jason/.ssh/id_rsa:
Now ssh to 192.168.1.1 again, this time it doesn’t ask for a password!
$ ssh root@192.168.1.1
BusyBox v1.15.3 (2011-11-24 00:44:20 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
Backfire (10.03.1, r29592) ------------------------
* 1/3 shot Kahlua In a shot glass, layer Kahlua
* 1/3 shot Bailey's on the bottom, then Bailey's,
* 1/3 shot Vodka then Vodka.
---------------------------------------------------
root@MyOpenWrt:~#
Voilà!
You can also do this via the luci web interface. Its actually very easy. Copy your ~/.ssh/id_rsa.pub and paste it into “System” -> “Administration” -> “SSH-Keys” and then “Save & Apply”. Done
[] Vim reference :e filename (open filename)
:q! (quit, don’t save)
:w (write/save)
:wq (write and quit)
:x (write if changed, otherwise exit)
:changes (show list of edits in the buffer)
a (insert after)
A (insert after line)
h j k l (left, down, up, right)
$ (move to end of line)
^ or 0 (move to beginning of line)
G (move to end of file)
gg (move to top of file)
gUU (uppercase entire line)
guu (lowercase entire line)
gUw (uppercase a word, u lowers)
:n (move to “n” line, n=number)
x (delete to the right)
X (delete to the left)
D (delete to the end of line)
dd (delete current line)
yy (yank/copy current line)
V (begin highlight, up and down to select “y” to yank selection)
vn (yank “n” lines below cursor, n=number)
p (put/paste)
u (undo)
ctrl+r (redo)
/string (search for “string”)
n (search for next string match) :s/yellow/green/gc (replace yellow with green on current line, g is for global, each match is replaced in a line, instead of the first match in a line. c is for confirm/ask) :%s/yellow/green/g (replaces yellow with green on the entire page) :%s:/usr/local/bin:/opt/users/bin:g (use something other than / as delineation so you don’t have to escape “/”. Like this nasty example: :s/\/usr\/local\/bin/\/usr\/loca\/bin) :%s#http://jasonschaefer.com#https://jasonschaefer.com#g (Switch the delimiter to # for strings with : and / to avoid annoying escapes!) :2,$s/ */ /g (After the 2nd line, replace 1 (2 spaces with a *) or more spaces with 4 spaces, globally)
strftime $ echo the day and time is currently `date +"%a at %T"` https://foragoodstrftime.com/
Sat, Jun 23 22:01:40 “%a, %b %d %T”
Sat, Jun 23 2018 7:04 PM “%a, %b %d %Y %l:%M %p”
[] bash tricks
stop bash history: unset HISTFILE
[] find command find . -name "name" -exec [command goes here] {} \; find . -type d -exec chmod 750 {} \;
recursively changes type directories to user=rwx, group=r-x, other=— find . -type f -exec chmod 664 {} \;
recursively changes type file user=rw-, group=rw-, other=r– (so that files are not executable) find /home/BACKUP -mtime +14 -exec rm -fr {} \;
-mtime options:
n exactly n days
+n more than n days
-n less than n days
find files that are newer than specified date time:
find /path/ -newermt 2018-01-15
use -ls to output long listing of matches
find /path/ -newermt “may 21 2018 16:00” -ls
yesterday or today can be used instead
find files between a date reference
finds files between 16:00 and 16:47 on may 21
find /path/ -newermt “may 21 2018 16:00” ! -newermt “may 21 2018 16:47”
to convert all backslash \ to forward slash / find . -type f -iname *.xml -exec sed -i 's:\\:/:g' {} \;
find hard links (directories have multiple links so use type file and not with 1 link)
find /path -type f ! -links 1
find directories, with emails, with less than 330 files (emails)
find /home/user/Maildir/ -type d -name cur -exec tree -RaFC –filelimit 330 {} \;
find quantity (310-320) of files under any directory named cur
find /home/user/Maildir -type d -name cur -exec bash -c “echo -n ‘{} ‘; ( ls ‘{}’/ | wc -l )” \; | grep ‘ 3[12][0-0]$’
find -exec has two variants:
this variant runs the command (echo in this case) once per match -exec echo '{}' \;
echo ./match1
echo ./match2
echo ./1match
and this runs the command once against all matches -exec echo '{}' \+
echo ./match1 ./match2 ./1match
[] Image Conversions and Resizing in batch groups
This will resize all jpg’s in the current directory “.” to 1024×768 and put them in the directory small find . -iname "*.jpg" | xargs -l -i convert -resize 1024x768 {} small/{} or a better use of find and convert would be
find -iname "*.jpg" -exec convert -resize 20% {} {}_small.jpg \;
You can replace the “convert -resize” with convert -quality 85% to compress the images instead.
merge multiple images into one pdf convert blah-page1.png blah-page2.png blah.pdf
wildcards work convert *.png blah.pdf
convert is a part of imagemagick
[] Edit EXIF data on images
Using exiftool to shift wrong date caused by a camera with the wrong time. man Image::ExifTool::Shift.pl for a manual.
example: exiftool "-AllDates+=1:0:21 0:0:0" *.JPG
This adds (+=) 1 year, 0 months and 21 days, 0 hrs, 0 min, 0 sec to all files ending in .JPG
[] tar
tar with various exclude examples tar zcfv backup-website.tar.gz --exclude=stuff --exclude=path/to/stuff --exclude="more stuff with spaces in the name" --exclude=*.wild /home/website
[] chmod tricks
chmod can be used in a way where it preserves executable permissions, if they are already present. using upper X chmod -R u=rwX,g=rwX,o=rX /path/to/
This recursively (-R) sets user and group to rw- dirs and files that don’t already have executable permissions (the X is similar to x but preserves executable perms if they were preexisting). If the dir or file has any executable permissions then it sets user and group to rwx. This can be handy if you want to change lots of files and dirs at once but not make files executable. For instance, chmod -R u=rwx,g=rwx would blanket files and dirs making them all executable. Of course, using find with type and exec can more explicitly set permissions. But it will reset any executable files as well. Thus the benefit of chmod and X.
To see what files are executable, if any, do find /path/ -executable -type f
Proper permissions for wordpress: chown www-data:wwwmaster -R /home/www/ find /home/www/ -type f -exec chmod g=rws {} \; find /home/www/ -type d -exec chmod g=rwxs {} \;
[] How to recursively force a group permission + umask per user on gnu/linux.
First you can recursively set the desired owner and group. Recursive is optional, only needed if you have sub dirs. chown -R root.users /path/to/dir
Then force all files and directories created under /path/to/dir to be owned by the creator and the group will be set to “users” group. Notice the chmod g+rwxs is adding the (s)etGID bit for the group. find /path/to/dir -type d -exec chmod g+rwxs {} \;
You will notice that when a user now creates files or directories under /path/to/dir they come out as (on a typical system) -rw-r--r-- 1 jason users 0 Aug 29 16:49 this is a file
drwxr-sr-x 2 jason users 6 Aug 29 16:49 this is a directory
You will need to change your umask. You can find it under your home directory in ~/.profile
Uncomment or add umask 002 so that the group “users” will be able to read your files and execute your directories.
[] changing default new file or directory permissions, umask on debian wordaround for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646692
change /etc/login.defs UMASK 022 (equivalent to 644/rw-r–r– files and 755/rwxr-xr-x directories)
to UMASK 002 (equivalent to 664/rw-rw–r– files and 775/rwxrwxr-x directories)
If that doesn’t work. Enable the pam_umask module like this. echo "session optional pam_umask.so usergroups" >> /etc/pam.d/common-session
[] Cleanup /etc/passwd and /etc/group
sort /etc/passwd in place pwck -s
sort /etc/group in place grpck -s
[] Rename multiple files
remove space from all files ending in .mp3 rename 's/ //'g *.mp3
rename all files ending in .ZIP to .zip
rename 's:\.ZIP:\.zip:' *.ZIP
[] search and replace text within a group of files
find /etc/NetworkManager/system-connections/ -exec sed -i "s/mac-address=0:1e:4c:27:40:00/mac-address=EC:55:F9:0F:5D:00/g" {} \; use -name, -type to refine the match if you need.
jedit is a gui program that can do this.
[] migrating Network Manager system-connections to new computer
You can replace the interface-name and the mac-address as shown above or remove them entirely.
sed -i ‘/^interface-name/d’ /etc/NetworkManager/system-connections/*
sed -i ‘/^mac-address/d’ /etc/NetworkManager/system-connections/*
On the new machine “systemctl stop NetworkManager” and “rsync -a” them to the new machine. Then start network manager “systemctl start NetworkManager”
[] SSH stuffs
copy your ssh public key to remote hosts ~/user/.ssh/authorized_keys file ssh-copy-id user@host
Use ‘ssh-add’ to add your private key to the ssh-agent, so you don’t need to type your passphrase each time you ssh someplace.
create a listen socket on your local computer, that redirects port to a host on remote network (10.9.8.2) ssh -L localhost:3389:10.9.8.2:3389 user@host -L [bind_address:]port:host:hostport
(now you can rdesktop to localhost and it will connect to the remote 10.9.8.2) rdesktop -g90% localhost
create a remote socket that forwards port 2222 on localhost of server to port 22 on initiating host.
Useful for remote support sessions. ssh -R localhost:2222:localhost:22 user@hostname -R [bind_address:]port:host:hostport
(now you can ‘ssh -p2222 localhost’ from the server and reach the host)
create a socks4/5 proxy over ssh ssh -D8080 user@hostname
(now you can configure your browser to use socks5 proxy at localhost:8080 and you can reach the remote networks web servers, or just use it to securely proxy your web traffic through the remote hosts internet connection)
[] Sending mail with telnet: telnet hostname 25
helo me
mail from:myaddress@mydom.com
rcpt to:youraddress@yourdom.com
data
This is a test
.
(thats a newline [enter] – period – and another newline [enter])
echo Cleanup .bak files older than 7 days forfiles /p d:\backup /m *.bak /d -7 /c "cmd /c del /q @path"
echo Set variable date as yyyymmdd set date=%date:~-4,4%%date:~4,2%%date:~-7,2%
echo %date%
[] Filesystem stuff
make clone image of sda dd if=/dev/sda of=/dev/sdb bs=4096 conv=notrunc,noerror
notrunc or ‘do not truncate’ maintains data integrity by instructing dd not to truncate any data.
noerror instructs dd to continue operation, ignoring all input errors. Default behavior for dd is to halt at any error. Useful when imaging damaged drives.
bs=4096 sets the block size to 4k, an optimal size for hard disk read/write efficiency and therefore, cloning speed.
check status of dd transfer (use pgrep to find process id, kill to send user define signal 1, dd progress will be displayed on terminal where dd was run) or pass “status=progress” to dd command
kill -USR1 $(pgrep ^dd)
mount image losetup /dev/loop0 sda.img
mount /dev/loop0 /mnt
Initialize all SATA buses: for x in /sys/class/scsi_host/host*; do echo "- - -" > $x/scan; done
xfs filesystem and xfsprogs
Determine the amount of fragmentation on sda2 xfs_db -c frag -r /dev/sda2
Filesystem re-organizer, by default, with no arguments. It re-organizes files in mounted partitions for 2 hours. Use -t to change the time.) xfs_fsr
These tools reside in the xfsdump package
[] Recover Files
testdisk (recover lost partitions)
photorec (part of the testdisk suite)
foremost sda.img
-t (type doc,jpg,exe etc. all is default)
-a (no error detection, recovers partial files)
-d (indirect block, use for nix filesystems)
-o (output dir)
-T (timestamp output dir)
Interface config for bridging to virtualized client /etc/network/interfaces
wireless interfaces rarely ever support bridging.
# The primary network interface
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_stp off
bridge_waitport 0
bridge_fd 0
Resize/Add storage to kvm image: dd if=/dev/zero of=myvirtualhost.img bs=1M count=78k oflag=append conv=notrunc
notrunc MUST be used or else append will overwrite beginning of image.
Alternately, creates a sparse file which suffers from fragmentation and possible corruption if host system doesn’t provide proper space for the sparse image to fill into. So its not recommended. truncate -s +10G image.raw
Alternate method sparse: qemu-img create -f raw addon.img 10G
be sure to make a backup of original.img
now you can append addon.img to original.img cat addon.img >> original.img
Now, boot the .img vm and use cfdisk to partition the new space. Reboot, and build a filesystem OR boot the instance with a live distro that has gparted and merge/resize the new partition with the old.
Convert a qcow2 image to raw image and remove the sparsity (-S 0 is non-sparse). qemu-img convert -p -O raw -S 0 win7pro.qcow2 win7pro.img
Also, fallocate is a great way to allocate kvm images. “preallocation is done quickly by allocating blocks and marking them as uninitialized, requiring no IO to the data blocks. This is much faster than creating a file by filling it with zeroes” fallocate -l 128GiB virtualhost.img
write zeros to the image so that you can make a sparse copy of the image for backup. Without the zeros the sparse copy won’t have the ability to sparsify dd if=/dev/zero of=virtualhost.img conv=notrunc,fdatasync bs=1M count=128K
preferred method for expanding a disk image (make a backup!!) original.img is 64GB and you want to expand it to 128 fallocate -l 128GiB original.img use gparted to expand the partition and filesystem into the extra space.
Backup virtual images into a sparse file to save space cp --sparse=always winblows7.img SNAPSHOTS/winblows7.img_oct06-2017
Be sure to unsparsify the file if you need to restore it! cp --sparse=never SNAPSHOTS/winblows7.img_oct06-2017 winblows7.img
[] KVM with Windows
The best way to get virtio is on install. Download the block driver floppy image and attach it, I use virt-manager. Set your hard drive to type virtio and start your windows install. It will will prompt you to press f6 to install third party drivers. Then press S (you have a disk from a third party manufacturer, your floppy image)
If you already have a disk type IDE and want it to be virtio (better). Then do this:
1. Create a temporary image kvm-img create -f qcow2 temp-virtio.img 1G
2. Shutdown your virtual machine and attach temp-virtio.img as a hard drive, as type virtio.
3. Attach the virtio-win-x.x.x.vfd (i used the one from fedoraproject.org, see below) to you virtual machine
4. Boot up and install the drivers
5. Shutdown, remove the old hard drive image and re-add it as type virtio
6. Boot up and since you already installed the drivers it will boot. Otherwise, you get BSOD..
(You can remove the temp-virtio.img and floppy image).. All done.
For network drivers.. Shutdown, set the “device model” to virtio. Attach the NETKVM-xxxx.iso as a cdrom. Bootup and install drivers. yay!
When using raw disk images, the “live” backup options are almost non-existent. The pros of raw img performance may outweight the cons of backup. Here is a simple way to backup .img virt images with minimal downtime:
rsync -a --inplace --progress --stats [source.img] [destination.img]
md5sum [source.img]
virsh start [source.img]
md5sum [destination.img]
[] Debian package tricks
list all packages that come from a particular repository, this case “testing”
for p in $(dpkg -l | awk ‘/ii/{ print $2 }’); do for i in $(apt-cache policy “$p” | awk ‘/Installed/{ print $2}’); do apt-cache policy “$p” | grep -A1 ‘\*\*\*\ ‘$i” | if grep -q testing; then echo $p; fi; done; done
[] Windows Policy
run gpedit.msc to edit policy
to backup or move to new host, copy the following
%systemroot%\system32\GroupPolicy\Machine and User dirs
to apply changed policy’s gpupdate /force
[] RDP tricks
plain old vnc is no more, not to say its not useful but xrdp is a super combo rambo pack. when it comes to ease of use, autostart scripts in debian, built in encryption, performance and cross platform the xrdp project rules the roost. Follow these simple steps.
on server: apt-get install xrdp
done;
on client: rdesktop -g95% [server name or ip]
-g is for geometry, look it up in man rdesktop
done; wow!
obviously, you will need rdesktop or some other remote desktop protocol installed on the client.
If you have issues with the arrow up and down keys minimizing and maximizing your X terminal do the following:
In gnome, use gnome-control-center -> Go to keyboard ‘Shortcuts’ tab, ‘Windows’ on the left pane -> select super+up and super+down shortcuts -> press backspace to disable these shortcuts on these actions.
xfreerdp is a fork of rdesktop that has newer features like certificate verification that comes with new versions of MS Windows.
SeamlessRDP http://www.cendio.com/seamlessrdp/ rdesktop -A -s "c:\seamlessrdp\seamlessrdpshell.exe c:\program files\internet explorer\iexplore.exe" -u username -p password hostname
uhhh, for the record I have NEVER gotten this to work properly. Please contact me if you have!
[] Self Signed certificate on debian, the easiest way possible make-ssl-cert /usr/share/ssl-cert/ssleay.cnf /etc/ssl/private/hostcert.crt
This script will ask for a domain and write the certificate. to /etc/ssl/private/hostcert.crt
flashing with atftp (follow the instuctions for particular device at http://wiki.openwrt.org/toh/start) curl -T openwrt-xxxx-xxxxx-squashfs-factory-xxxx.img tftp://192.168.1.1
or the more complicated annoying way atftp --trace --tftp-timeout=1 --put --local-file openwrt-xxxxx-xxxxx.img 192.168.1.1
Setup SSL/TLS (https) for Luci web interface and disable insecure plaintext (http) opkg install luci-ssl
be sure the following is commented out in /etc/config/uhttpd # HTTP listen addresses, multiple allowed
# list listen_http 0.0.0.0:80
# list listen_http [::]:80
Also change the cert px5g options to be more unique and add more days to the self signed certificate. /etc/init.d/uhttpd restart
Disable/Enable Wireless on a schedule, automatically
The first line will use bridge control to remove the wireless interface (wlan0-1) from the lan bridge (br-lan) at 22:30. The next cron will add the interface back at 6:00. Redirect (>) all output to dev null. Substitute wlan0-1 for whichever interface you need to. Add this to crontab: 30 22 * * * brctl delif br-lan wlan0-1 >/dev/null 2>&1
0 6 * * * brctl addif br-lan wlan0-1 >/dev/null 2>&1
use “brctl show” to see which interfaces are in the bridge:
root@OpenWRT:~# brctl show
bridge name bridge id STP enabled interfaces
br-lan 7fff.c6031578e51d no eth0.1
wlan0
wlan0-1
[] Cron and wget with Afraid free DNS
Its best to use curl. Install curl with opkg update and then opkg install curl or apt or yum, etc. */10 * * * * /usr/bin/curl -k https://freedns.afraid.org/dynamic/update.php?[random string]
wget is overly complicated… but if its all you got, then its great. */10 * * * * /usr/bin/wget --no-check-certificate -O - https://freedns.afraid.org/dynamic/update.php?[random string] > /dev/null 2>&1
add to /etc/rc.local so that it updates immediately on bootup. This doesn’t always work if the wan interface isn’t operational at time of execution.
# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.
/usr/bin/curl -k https://freedns.afraid.org/dynamic/update.php?[random string]
exit 0
[] MYSQL
mysql> create database newdb;
mysql> CREATE USER 'newuser'@'localhost' IDENTIFIED BY 'password';
mysql> GRANT ALL PRIVILEGES ON newdb . * TO 'newuser'@'localhost';
(GRANT ALL PRIVILEGES ON [database name].[table name] TO ‘[username]’@’localhost’;)
mysql> SET PASSWORD FOR 'newuser'@'localhost' = PASSWORD('newpassword');
mysql> DROP USER 'newuser'@'localhost';
update table g2_PluginMap and set column g_active to 0 where column g_pluginID is captcha. This disables the captcha plugin in gallery2 UPDATE g2_PluginMap SET g_active = '0' WHERE g_pluginId = captcha; DELETE FROM g2_FactoryMap WHERE g_implModuleId='captcha';
(unrelated to mysql, you will need to clear the cache to fully disabled this plugin -> http://your-domain.tld/gallery/lib/support/index.php
[] RSYNC
rsync highlights:
typical use — rsync -av --delete --stats --exclude media/* /home/ /mnt/usb/rsync-home-mirror
copy [a]rchive, [v]verbosely, –delete any files on the destination that don’t exist in source (mirror), show transfer [stat]istics, [exclude] any files inside directory media, copy contents of /home/ into /mnt/rsync-home-mirror
advanced use — useful for copying entire OS rsync -aAHXi --super --numeric-ids /source/ /destination
-a archive, -A copy ACL, -H copy hard links, -X copy extended attributes, -i show changes, –numeric-ids preserves uid and gid numerically instead of by name.
Use -n to do a dry run! Especially valuable when using –delete switch.
You can think of a trailing / on a source as meaning “copy the contents of this directory” as opposed to “copy the directory by name”
[] fstrim
fstrim one-liner for cron. every sunday at 12:30 timestamp the log and include two partitions, / and /home. 30 12 * * 0 /bin/date +\%c > /tmp/fstrim.log && /sbin/fstrim -v / >> /tmp/fstrim.log 2>&1 && /sbin/fstrim -v /home >> /tmp/fstrim.log 2>&1
[] wget
for range in {1..7};do wget http://URL/Episode$range.mp3 ; done for range in {{1..3},{5..7}};do wget http://URL/Episode$range.mp3 ; done
Mirror entire site with wget wget --mirror -p --convert-links http://URL
or wget --recursive --no-clobber --page-requisites --html-extension --convert-links --no-parent --domains website.org http://website.org [] ffmpeg
convert video to webm ffmpeg -i be-hose.mp4 -acodec libvorbis -aq 5 -ac 2 -qmax 25 -threads 2 be-hose.webm
[] booting os manually from grub2
set root=(hd0,gpt2)
linux /boot/vmlinuz-2.6.18-6-686 root=/dev/sda1
initrd /boot/initrd.img-2.6.18-6-686
boot
[] booting into password recovery using grub
new methond: append systemd.debug_shell to linux line of grub. system boots normal and ctrl+alt 9 will have root shell that bypasses password prompt.
old method: append init=/bin/bash to linux line of grub. system boots in read only mode mount -o remount,rw / and run passwd to change password.
[] Text Manipulation, simple and common techniques
file.txt contains:
a b c d e
f g h i j
awk '{print $2 "\t" $5}' file.txt
b e
g j
awk '{print $2","$5}' file.txt
b,e
g,j
cut -d " " -f 2 file.txt
b
g
cut -d " " -f 2,4 file.txt
b d
g i
cut -d " " -f 3-5 file.txt
c d e
h i j
MATH with awk!
file.txt contains:
1 2 3 4
5 6 7 8
awk '{print $2 + $4}' file.txt
6
14
awk '{print $2 * $3}' file.txt
6
42
[] EXIM
consult the oracle: zless /usr/share/doc/exim4-base/README.Debian.gz
dpkg-reconfigure exim4-config
update-exim4.conf; service exim4 stop; service exim4 start
Enable tls:
enable the following in /etc/default/exim4 SMTPLISTENEROPTIONS='-oX 25:465:587 -oP /run/exim4/exim.pid'
enable plain_server: PLAIN and LOGIN in /etc/exim4/exim4.conf.template
swaks -a -tls -q HELO -s smtp.schaeferconsulting.com -au test -ap '<>'
for x in $(mailq | grep frozen | sed -e ‘s/^……….//’ -e ‘s/ .*//’); do exim -Mrm $x; done
[] GPG
jason gets the public key for geoff from keyserver gpg --keyserver keys.openpgp.org --recv-keys 6058D99C
or gpg --keyserver keys.openpgp.org --search-keys email@address
signs the key with his B0EE80C1 key gpg --default-key B0EE80C1 --sign-key 6058D99C
export the signed key to send to geoff gpg --output 6058D99C.asc --export --armor 6058D99C
send geoff_6058D99C.asc to geoff
———-
geoff receives key and imports gpg --import geoff_6058D99C.asc
sends the updated key to keyserver gpg --keyserver keys.openpgp.org --send-keys 6058D99C
These are the manual instructions for installing and configuring OpenVPN client.
After having many problems over the years with openvpn gui breaking, I have devised a reliable work around. Create the following batch script, name it something like ovpnConnect.bat, and right click to “Run as Administrator”. This does require the openvpn gui from openvpn.net to be installed. It calls the openvpn.exe. You can also add multiple vpn client connections!
@echo off
net session >nul 2>&1
if %errorLevel% == 0 (
echo Success: Administrative permissions confirmed.
) else (
echo Failure: Please right click and "Run as administrator"
pause
exit 0
)
cd "c:\Program Files\OpenVPN\config\" && "c:\Program Files\OpenVPN\bin\openvpn.exe" [userconfig].ovpn
Go to Compatibility tab and select “run this program as administrator”
(It requires admin priviledges because it needs to write routes for the new VPN tunnel. Without, it will connect but won’t know how to reach the other network.)
Get your OpenVPN configuration files from the system administrator. Copy and paste them into C:\Program Files\OpenVPN\config
ca.crt (certificate authority)
jason.crt (client certificate)
jason.key (client secret key)
jason.ovpn (client configuration). Here are the contents of jason.ovpn:
client
dev tun0
cert jason.crt
key jason.key
ca ca.crt
remote vpn.server 1194
Now you can launch OpenVPN GUI by double clicking the icon on the desktop (the one we just set to run as admin). This will launch the OpenVPN GUI into the system tray.
Click on system tray, right click on OpenVPN GUI, left click “Connect”.
If all goes well, you will successfully connect. The OpenVPN GUI systray icon turns green. Now you are on the Virtual Private Network!