Commit graph

13 commits

Author SHA1 Message Date
0ce061fa31
switch to getExe and getExe' throughout the config 2024-07-05 00:41:59 +02:00
427333c2aa
workaround for the cve
https://github.com/NixOS/nixpkgs/pull/323753#issuecomment-2199762128
2024-07-01 13:21:26 +02:00
0ec34d7f5f
get rid of with lib; treewide 2024-05-05 12:38:40 +02:00
dd078d9c07
thanks raf (also fuck you raf) 2024-04-05 22:59:32 +02:00
a9584581e6
oops lol !!!! #2 2024-03-06 12:21:02 +01:00
7d9edd29c7
oops lol !!!! 2024-03-06 12:13:21 +01:00
f52134322c
rework the ssh module to use the publicKey directly 2024-03-06 12:11:58 +01:00
eac5089356
use pubkeys in ssh modules and make hostAliases {} by default 2024-03-06 12:03:08 +01:00
7bde656c9f
ssh-agent (this shit is crazy read the whole commit message)
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
2024-03-05 17:43:10 +01:00
cd8f5e7778 sign test #6 2024-03-03 02:25:43 +01:00
d172cfcb68
add port to ssh module 2024-02-05 22:24:04 +01:00
7a098a90cd
fix: pipewire module and other minor fixes 2023-10-13 23:18:35 +02:00
6306a80189
feat: massive 2023-10-13 21:04:24 +02:00