Probably one of the easiest things you'll ever do with gpg
Install Keybase: https://keybase.io/download and Ensure the keybase cli is in your PATH
First get the public key
keybase pgp export | gpg --import
Next get the private key
Probably one of the easiest things you'll ever do with gpg
Install Keybase: https://keybase.io/download and Ensure the keybase cli is in your PATH
First get the public key
keybase pgp export | gpg --import
Next get the private key
You need to know that Linux are have a default software: gpg
for sign the GPG key. but we are going to use Keybase instead.
tags: Auburn, Auburn University, WPA2, WPA2 Enterprise
Auburn University is gracious enough to provide instructions to Ubuntu users on how to connect their hosts to the Auburn University WiFi Network.
Many Universities use WPA2 Enterprise authentication on their networks. This allow you to track WHO is connected where and have granular control over who's able to access the WiFi network.
For tinkerers and experimenters with Raspberry Pi, Particle Photon, and other embedded systems, this poses a problem because many simplier IoT devices do not support WPA2 Enterprise natively or not without some hassle.
Raspbian Jesse and earlier will display a WPA2 Enterprise network from its dropdown list, but it will be greyed out. The workaround is to manually connect to it:
import os | |
import re | |
def zsh_to_fish(cmd): | |
return (cmd.replace('&&', '; and ') | |
.replace('||', '; or ')) | |
def is_valid_fish(cmd): |
#!/bin/bash | |
WORKING_DIR=/usr/syno/etc/certificate | |
ARCHIVE_DIR=${WORKING_DIR}/_archive | |
INFO=`cat ${ARCHIVE_DIR}/INFO` | |
KEYS=`echo $INFO | jq -r 'keys_unsorted|.[]'` | |
for key in ${KEYS}; do | |
SERVICES=`echo $INFO | jq -r --arg key ${key} '.[$key].services | .[] | [.subscriber, .service] | join("/")'` |
* { background-color: rgba(255,0,0,.2); } | |
* * { background-color: rgba(0,255,0,.2); } | |
* * * { background-color: rgba(0,0,255,.2); } | |
* * * * { background-color: rgba(255,0,255,.2); } | |
* * * * * { background-color: rgba(0,255,255,.2); } | |
* * * * * * { background-color: rgba(255,255,0,.2); } | |
* * * * * * * { background-color: rgba(255,0,0,.2); } | |
* * * * * * * * { background-color: rgba(0,255,0,.2); } | |
* * * * * * * * * { background-color: rgba(0,0,255,.2); } |
const countryList = [ | |
{ | |
name: 'Afghanistan', | |
emoji: '🇦🇫', | |
}, | |
{ | |
name: 'Åland Islands', | |
emoji: '🇦🇽', | |
}, | |
{ |
#!/bin/bash | |
# /volume1/UDMBackup is the path to the NFS share on the Synology | |
# /nfs/UDMBackup is the mount point on the local Linux server where the script runs | |
# /opt/scripts/UDM_pass is a text file containing the root account password on the UDM | |
# I run this script on an Ubuntu VM for ease of maintenance and save the backups on a Synology using NFS | |
LOGFILE="/opt/scripts/udmpro-backup.log" | |
BKUPSCRIPT="sshpass -f /opt/scripts/UDM_pass scp -o StrictHostKeyChecking=no -r root@<<UDM PRO IP ADDRESS>>:/mnt/data/unifi-os/unifi/data/backup/autobackup/* /nfs/UDMBackup" | |
mount <<SYNOLOGY IP ADDRESS>>:/volume1/UDMBackup /nfs/UDMBackup |
const net = require("net"); | |
const server = net.createServer(); | |
server.on("connection", (clientToProxySocket) => { | |
console.log("Client connected to proxy"); | |
clientToProxySocket.once("data", (data) => { | |
let isTLSConnection = data.toString().indexOf("CONNECT") !== -1; | |
let serverPort = 80; | |
let serverAddress; |