Note: this was written before support for multiple handlers per logger was added to CircuitPython logging.
In CPython, there is a hierarchy of loggers.
Each logger except the root logger has a parent. When a log record is handled for particular logger,
the hierarchy is traversed until either the propagate flag of given logger is found to be False,
or root logger is encountered.
This is meant for Debian/Ubuntu.
wget -O /tmp/snmp_exporter.tgz \
https://github.com/prometheus/snmp_exporter/releases/download/v0.20.0/snmp_exporter-0.20.0.linux-armv7.tar.gz
sudo mkdir -p /srv/snmp_exporter
sudo chown pi:pi /srv/snmp_exporter
This setup is basically using the configuration from https://crashlaker.github.io/2021/10/09/truenas_snmp_exporter.html
It assumes Prometheus as data backend. Also, nas.local is the NAS machine hostname used throughout this Gist.
This note is a bit of a experiment with Gists.
The end result looks like this: 
This is meant for Ubuntu 20.04.4 LTS and Solokey Somu
The purpose of the key is backup key (in case all my Yubikeys and smart phone get lost), hence the resident SSH key and 2FA setup for the Github account.
python3 -m venv env
. ./env/bin/activate
A 2005 booklet with mission statement from Scott McNealy.
using https://yetiops.net/posts/openbsd-snmp-exporter/
The goal is to present basic metrics such as bytes passed through the external interface of the router. The main idea is to run SNMP on the OpenBSD router that can get the metrics from PF. Then SNMP exporter from Prometheus will convert the data to Prometheus format that can be scraped by Grafana.
The constraint is that this should be done in reasonably secure way: the IoT devices are in separate VLAN, however the router should have miminal exposure. Using snmpd with privilege separation and in flight data protection is sufficient. Further, the data collection and graphing will be done on single machine.
The result looks like this: 
The goal is to use FreeBSD as a KTLS client.
ref: https://docs.freebsd.org/en/books/handbook/cutting-edge/
Notes:
GENERIC kernel configuration has the KERN_TLS option set by defaultrpc.tls* daemons are built by default
This gist contains my notes about how the FIPS selftest signature check works in OpenSSL 1.x. Assumes basic awareness of the OpenSSL FOM (FIPS Object Module). My focus for this case is Solaris on SPARC.
The goal is to examine some of the inner workings of FIPS signature verification.
The FOM is built as fipscanister.o using designated code and linked into common OpenSSL build.
When the libcrypto.so library is loaded, the FOM will perform self test. If the self test fails,
the running program is abort()ed.
These are my personal notes on how to run/use OpenBSD on Ubiquiti Edgerouter, specifically for Edgerouter 4. I installed OpenBSD bunch of releases back and keep upgrading. Perhaps some of the issues highlighted below would not happen on fresher install.
Use the Cisco RJ45 Male to DB9 Female console cable + the Aten USB to serial converter.
# pre-flight check
VBoxManage list ostypes | grep FreeBSD
# new VM
VM=FreeBSD
zfs create tank/vm/vkotal/$VM
VBoxManage createvm --basefolder /tank/vm/vkotal --name $VM --ostype FreeBSD_64 --register
# CPU