so first when I wanted to configure ssh to use the correct keys by
default I found some guide that used IdentitiesOnly yes so I used it
too without even knowing what it does
then later when I wanted to nix my ssh config I noticed that it's set to
true and didn't know what it does so I read the manpage
I wrote the description of the `indentitiesOnly` option of my wrapper
module based on that but I didn't really understand what it actually
does
well, as you can see in the commit history, a day or two ago (forgot) I
started using an ssh key to sign my commits and to make things even more
convenient I moved all of my private ssh keys to my keepassxc database
as attachments
I tested it on my main laptop and everything worked fine but on that
laptop all the keys were still in ~/.ssh as I didn't just want to
immediately delete them and risk losing any
well that's what hid this bug - on the main laptop when pushing, it just
used the keys in ~/.ssh, which I don't have on this laptop (the one I
take to classes) because, well, I did this not to have to copy both the
keepassxc database and ~/.ssh between machines - I only copied the
keepassxc database as it had all the keys in it
well turns out with the config before this commit, it would only try to
use keys in ~/.ssh which aren't - and won't - be here so it failed
this option makes it actually use keys supplied by ssh-agent, which
keepassxc acts as and is the only way to get them in the current setup
I moved from `includes` to `extraConfig` and didn't remove the
`contents` that explains EVERYTHING
it doesn't explain why I'm this retarded though
followed this btw https://code.mendhak.com/keepassxc-sign-git-commit-with-ssh/
big shoutout to mendhak :-)
in the future I'll need to make some custom module where I define what
hardware the system has, I'd like not to rely on things like this
for now this is enough I hope
