Complete guide for configuring Synaptics fingerprint readers (including Metallica MIS Touch) on Linux distributions using python-validity and fprintd.
This guide specifically covers Synaptics fingerprint sensors that require proprietary drivers:
The Synaptics fingerprint sensor (06cb:009a) present on my T480 is not supported by libfprint and fprintd as it requires a non-free binary blob. uunicorn created open-fprintd, a replacement for fprintd, that allows for loading of binary blobs. In conjunction with their python-validity driver we are able to make use of the inbuilt fingerprint reader. The following instructions were tested against Fedora Linux 35.
sudo dnf copr enable tigro/python-validity
sudo dnf install open-fprintd fprintd-clients fprintd-clients-pam python3-validity
$ parted /dev/sdX mklabel gpt/dev/sdXY)
$ parted /dev/sdX mkpart esp fat32 1MiB 512MiB$ parted /dev/sdX set 1 esp on$ parted /dev/sdX set 1 boot on$ mkfs.fat -F 32 -n UEFI /dev/sdXY
| #!/bin/bash | |
| # This script will run a restic backup and remove snapshots according to a policy. | |
| # In order for this script to work two environment vaiables must be set: | |
| # RESTIC_PASSWORD which is the restic repository password (or read https://restic.readthedocs.io/en/latest/faq.html#how-can-i-specify-encryption-passwords-automatically) | |
| # MY_RESTIC_LOGS_PATH which is the path where to save logs. For example: /home/paolo/restic/logs | |
| # | |
| # WARNING: This script prunes ond backups! Be careful not to delete backups that you need. | |
| # Customize the removing policy according to https://restic.readthedocs.io/en/latest/060_forget.html#removing-snapshots-according-to-a-policy | |
| # |
This gist was essentially created out of my own rant about Netflix being hostile to IPv6 tunnel services since June 2016. You are welcome to read my opinion on the matter, this is the more technical side to the issue and how to combat it within your own network.
Since I wrote this, various GitHub users have contributed their thoughts and ideas which has been incorporated into this gist. Thank you to everyone who have contributed their own methods and implementations.
Netflix now treats IPv6 tunnel brokers (such as Hurricane Electric) as proxy servers. A while ago it became apparent to users and Netflix that somewhat by accident, IPv6 tunnel users were being served content outside of their geolocation because of the way Netflix was identifyi
dhcp-script=/etc/detect_new_device.sh
Reference:
Just thought I'd put together some detail on deploying Tailscale using Docker and Portainer. These bits-and-pieces are available elsewhere, but not together, so hopefully this will save someone a bit of time if you'd like to add Tailscale to an existing Docker install:
Here's my annotated recommended docker-compose, to use with Portainer-Stacks. Note that I'm not using a pre-made Auth Key. I started that way, but realized it was very easy to simply check the Portainer log for the tailscaled container once the stack is running. In that log you'll see the standard Auth link that you can use to authorize the container. This way you don't need to create a key in advance, or create a reusable key that introduces a security risk:
version: '3.9'
services:
tailscale:
image: tailscale/tailscale
container_name: tailscaled