AliSot2000

After switching my ssh keys to be stored in Bitwarden I came across the problem that my development applications by Jetbrains did not pick up the ssh-agen and the SSH_AUTH_SOCK environment variable. That is:

• launch from a shell would work
• launch from toolbox would not work
• launch from the .desktop file would not work

I could not find a solution and asked on their forum, how this is achieved: There I was also informed that this is a workaround and that it's a problem of the way linux handles desktops [...].

AliSot2000

Disclaimer: I tested this gist works however, I did not do a deep dive into all the moving parts to verify that every sentence is 100% So use the guide and my explanation as a guesstimation of what's happending. The exact details might be off.

Base assumptions:

• You have >10 ssh keys.
• You configured hosts, users and keys in .ssh/config
• You are using a password manger like Bitwarden that comes with a ssh authentication socket.
• You want to migrate your ssh keys into Bitwarden.
• You want to keep using .ssh/config to also specify the key.

AliSot2000

The two hallmarks of the problem:

• the isc-dhcp-server is configured correctly. The /etc/dhcp/dhcpd.conf can be correctly parsed an running dhcpd -f -4 -cf /etc/dhcp/dhcpd.conf doesn't raise any errors.
• once the system is booted and you run systemctl status isc-dhcp-server.service you get this error:

Mar 15 20:12:04 raspi systemd[1]: Started isc-dhcp-server.service - ISC DHCP IPv4 server.
Mar 15 20:12:04 raspi sh[1005]: Internet Systems Consortium DHCP Server 4.4.3-P1
Mar 15 20:12:04 raspi sh[1005]: Copyright 2004-2022 Internet Systems Consortium.
Mar 15 20:12:04 raspi sh[1005]: All rights reserved.
Mar 15 20:12:04 raspi sh[1005]: For info, please visit https://www.isc.org/software/dhcp/