I currently use bash/zsh aliases to simplify setting up tunnels to our database servers.
In an article in the Linux Magazin I read about boring.
The tool looked nice as it allows a well readable config file and opening the tunnels in the background.
As boring (or rather its ssh_config library) does not support Match in the ssh config, it is no real solution for me.
Luckily I read ssh itself can do the job quite well without 3rd party tool!
evcc does not provide an metric endpoint for prometheus (see evcc discussion #7306).
With pollect, its easy to publish the evcc data for prometheus.
With my former Yubikeys I was used to use yubikey-oath-dmenu for (T)OTP.
As I found no similar solution for Token2, I wrote a wrapper script around t2-cli.
I recently started to use Token2 "T2F2-PIN+ Release3 TypeC" Keys to store SSH Keys use them for (T)OTP and U2F/FIDO2.
But GnuPG did not work out of the box on my Arch Linux notebook.
To enhance the restore speed for PostgreSQL databases, the pg_restore command running the most time-consumping steps concurrently by providing the number of jobs with -j/--jobs.
Unfortunately the parallel restore can fail when restoring foreign keys due to not yet restored tables:
pg_restore: error: could not execute query: ERROR: there is no unique constraint matching given keys for referenced table "page"
Command was: ALTER TABLE ONLY pagecontent
ADD CONSTRAINT "$1" FOREIGN KEY (page_id) REFERENCES page(id);
Configuring and using a local Yubikey for SSH with FIDO2 is very straight forward using the Yubico manual Securing SSH with FIDO2
But in some cases I would like to use my Yubikey based SSH key on my office's workstation when I am at home using my notebook.
The expiring Let’s Encrypt DST Root CA X3 can cause problems on old servers:
root@server:/etc# wget https://www.example.com/monitoring --2021-09-30 21:34:39-- https://www.example.com/monitoring Resolving www.example.com (www.example.com)... 93.184.216.34 Connecting to www.example.com (www.example.com)|93.184.216.34|:443... connected. ERROR: The certificate of `www.example.com' is not trusted.
Fortunately there is an easy workaround to ensure the expired chain is not checked.
The residential Swisscom Internet Box 2 does not allow to autoconfigure an Unify Dream Machine with IPv6.
After several hours of research I found a workaround to get IPv6 support.
In one of my projects I let Spring Boot automatically bind domain objects from the database.
This fails in the reduced unit test setup, because DomainClassConverter is not available. But it can be mocked!
When I fist started to use yedit to modify YAML files I got the following warning:
[WARNING]: The value {...} (type dict) in a string field was converted to "{...}" (type string). If this does not look like what you expect, quote the entire value to ensure it does not change.
Page 1 of 6
© 2015 - 2022 Moritz Kobel
Theme by Anders Noren — Up ↑