xtranophilist

One of the common errors after running updates on your Arch Linux system:

error: key "..." could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

Fix:

bjoern-r

arch: amd64
cores: 2
hostname: kodipriv
memory: 2048
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=56:94:2A:9A:8E:1B,ip=dhcp,ip6=auto,type=veth
ostype: ubuntu
parent: before_first_boot
rootfs: encrypted_zfs:subvol-103-disk-0,size=8G
swap: 512
lxc.cgroup2.devices.allow: c 226:* rwm

weinbrenner

# After upgrading Ubuntu to 21.10 CS.GO in Steam for Linux stopped working
# (@see https://github.com/ValveSoftware/csgo-osx-linux/issues/2815
#  and https://github.com/ValveSoftware/csgo-osx-linux/issues/2811
# )

# Here is how I fixed it:

# 0) Exit Steam, make sure it is not running anymore
$ ps aux | grep steam

morfikov

#!/bin/sh
# this goes into /etc/initramfs-tools/scripts/init-premount/a_enable_wireless
PREREQ=""
prereqs()
{
    echo "$PREREQ"
}

case $1 in
prereqs)

izzyleung

Generate a new pair of keys via wg

wg genkey | tee privatekey | wg pubkey > publickey

Upload the newly generate key to Mullvad

curl https://api.mullvad.net/wg/ -d account=YOUR_ACCOUNT_NUMBER --data-urlencode pubkey="$(cat publickey)"

aliicex

Stangri's VPN Policy Routing package is a mainstay of my OpenWRT builds. It works great for IPv4, but I couldn't, for the life of me, get it working with IPv6. Instead, I had to faux-implement PBR as follows.

My VPN provider only gave me a single IP address with a /128 prefix, so I was forced to use NAT6. This left me with a stanza in my firewall config that looks like this; note the masq6 option

config zone
	option name 'wan_vpn'
	option input 'REJECT'
	option output 'ACCEPT'
	option forward 'REJECT'

Snuggle

OpenPGP SSH access with Yubikey and GnuPG

Yubikey, Smart Cards, OpenSC and GnuPG are pain in the ass to get working. Those snippets here sould help alleviate pain.

Yubikey Config under Ubuntu

To reset and disable not used modes on Yubikey you need the ykman program

You can install it using those commands

G-UK

Introduction

The objective of these instructions is to create a complete Arm64 OS (Userland and Kernel) using Debian Debootstrap and RPI-Update for use on the Raspberry Pi 3 and 4.

Prerequisites:

• An existing Debian/Raspbian system (any architecture will do)
• An empty SD card formatted as per a standard Raspbian installation mounted to /mnt/sd on the build system
  • 1st Partition 0-256MB = FAT32 (Mount to /mnt/sd/boot)
  • 2nd Partition 256MB+ = EXT4 (Mount to /mnt/sd)

Set-up basic Debian system

AfroThundr3007730

#!/bin/bash
# These steps will allow the setup of an on-demand SSH proxy
# Three unit files will be created to serve this purpose:
#   ssh-socks-helper.socket - The listening socket providing activation
#   ssh-socks-helper.service - A systemd proxy to pass the socket fd
#   ssh-socks.service - The actual SSH service providing the tunnel

cat <<'EOF' > ~/.config/systemd/user/ssh-socks-helper.socket
[Unit]
Description=Proxy Helper Socket for Bastion SOCKS5 Proxy

artizirk

NB: This document describles a 'Old-School' way of using Yubikey with SSH

Modern OpenSSH has native support for FIDO Authentication. Its much simpler and should also be more stable with less moving parts. OpenSSH also now has support for signing arbitary files witch can be used as replacement of gnupg. Git also supports signing commits/tags with ssh keys.

Pros of FIDO

• Simpler stack / less moving parts
• Works directly with ssh, ssh-add and ssh-keygen on most computers
• Simpler
• Private key can never leave the FIDO device

Cons of FIDO