| 14 Sep 2023 |
K900 ⚡️ | KDE Gear patch release: https://github.com/NixOS/nixpkgs/pull/255096 | 10:49:02 |
K900 ⚡️ | Will probably merge once nixpkgs-review finishes | 10:49:08 |
| 20 Sep 2023 |
| Nadim Kobeissi left the room. | 06:41:28 |
| 21 Sep 2023 |
| movefasta joined the room. | 11:10:38 |
| dedmunwalk joined the room. | 23:10:01 |
| 22 Sep 2023 |
| K900 ⚡️ changed their profile picture. | 09:53:40 |
| 23 Sep 2023 |
qbit | anyone else use ssh-agent with something like AddKeysToAgent confirm 90m? It used to be that I was prompted for key re-usage (confirm) but lately it has stopped working .. i am not sure if it's something that changed kde side.. or was caused by me switching to HEAD of openssh-portable.. or how to determine if that's the cause :P | 13:55:41 |
K900 ⚡️ | I don't think KDE particularly cares about your SSH agent? | 13:56:08 |
qbit | SSH_ASKPASS=/nix/store/6jarymv133mirsw63mgi0wsjwkzr51pp-ksshaskpass-5.27.8/bin/ksshaskpass | 14:00:20 |
qbit | so when the key was requested for usage, ksshaskpass would prompt me | 14:00:54 |
qbit | for sure it "cared" in the sense that this used to work and now doesn't :P | 14:04:12 |
K900 ⚡️ | ksshaskpass is never in charge | 14:04:43 |
K900 ⚡️ | It's ran by the agent | 14:04:49 |
K900 ⚡️ | So it's really up to the agent | 14:04:55 |
qbit | right, not saying otherwise - but since I can't figure out why i am not being prompted .. i am trying to find a place to start | 14:08:49 |
K900 ⚡️ | I'd definitely start with the agent | 14:09:41 |
qbit | it definitely seems to be something with what ever is setting SSH_ASKPASS | 15:17:11 |
qbit | when I manually fire ssh-agent with SSH_ASKPASS set it works as expected (using my HEAD ssh-agent) | 15:17:33 |
qbit | not sure how to see the env of the ssh-agent when started via systemd stuff | 15:24:01 |
K900 ⚡️ | systemctl show --user ssh-agent should show it | 15:24:45 |
qbit | SSH_ASKPASS=/nix/store/gh9fsf573j2jslq85m65qyn9nlzv0ypv-ssh-askpass-wrapper | 15:26:53 |
qbit | hmm | 15:27:38 |
qbit | everything i set SSH_ASKPASS to works when I invoke ssh-agent in a terminal - but when it's started via TheProcess™(systemd?) it doesn't prompt with SSH_ASKPASS | 17:48:58 |
K900 ⚡️ | Are you sure it doesn't? | 17:50:07 |
K900 ⚡️ | Maybe it's actually trying and failing to find $DISPLAY or whatever? | 17:50:20 |
qbit | if that were the case i'd expect having SSH_ASKPASS_REQUIRE=force would make it work - but it doesn't | 20:38:24 |
qbit | switched back to nixpkgs openssh and the same thing is happening - so I don't think it's anything I introduced | 23:14:40 |
| 24 Sep 2023 |
K900 ⚡️ | I'm still pretty sure it's something to do with the environment the agent is running in | 06:01:31 |
ulrik ⚡️ | In reply to @qbit:tapenet.org SSH_ASKPASS=/nix/store/gh9fsf573j2jslq85m65qyn9nlzv0ypv-ssh-askpass-wrapper Could the wrapper be setting something funny? | 08:29:52 |
qbit | when I use the wrapper and the non-systemd-started ssh-agent it works as expected | 11:58:37 |