Blog: 2023-09-01
September is here so how bout an august LINK ROLL UP ?!?
https://serverfault.com/questions/669321/alternatives-to-kerberos-for-passwordless-server-access
https://github.com/krb5/krb5/blob/master/doc/appdev/y2038.rst
https://www.kerberos.org/software/tutorial.html
https://mailman.mit.edu/pipermail/kerberos/2018-May/021972.html
https://mailman.mit.edu/mailman/listinfo/kerberos
https://mailman.mit.edu/pipermail/krbdev/2014-December/012239.html
https://github.com/signalapp/Signal-Server
https://signal.org/docs/specifications/doubleratchet/
https://github.com/signalapp/libsignal
https://serverfault.com/questions/973654/using-ssh-keys-with-multiple-computers (maybe the solution for the short term is to make a single key which I can then copy between hosts, but give it a name which makes it clear it's not designed for any particular machine)
https://github.com/hashicorp/vault
https://smallstep.com/blog/use-ssh-certificates/
https://github.com/keybase/bot-sshca#getting-started
https://unix.stackexchange.com/questions/208495/ssh-key-authentication-with-multiple-computers
Oh ok yeah I can make all my machines public keys public, and just add them all as a bundle to authorized_keys. For now
With that in mind, here's my windows wsl public key
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILL5wJYLgKlQ2+e9YL57nv+PqjUEpzgCVSsn40nrQONq razzi@DESKTOP-IFJ7AJU
ez!
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDhUAvZuufX/fBFY3UKJb5cmLggDbMfFyd3mpyOB5LmR razzi@razzi-lightspeed
is my debian side