| 25 Nov 2022 |
psvo | please disregard, I've misunderstood it, it should not affect nixos probably | 17:52:26 |
K900 | OK I am very confused now | 17:53:18 |
K900 | login -f does invoke PAM | 17:53:31 |
K900 | But WSL doesn't invoke login -f | 17:53:51 |
K900 | Or rather, it invokes it ONCE | 17:53:55 |
K900 | Oh god I have a SUSPICION | 17:55:01 |
K900 | If this turns out to be it | 17:55:19 |
K900 | I will slap someone | 17:55:24 |
Arson Copperflame | From what I learned when I made the horrible runuser hack, systemd --user only works, when the shell is inside a PAM session and the PAM config that is used includes pam_systemd.so | 17:55:39 |
K900 | OK it's not it | 17:55:53 |
K900 | Thank god | 17:55:55 |
Arson Copperflame | So MS did the exact same thing that I did, but they used login instead of runuser | 17:55:56 |
K900 | I think what they're doing is worse actually | 17:56:09 |
K900 | They're spawning exactly one PAM session with login | 17:56:18 |
K900 | That just hangs around in the background | 17:56:24 |
psvo | just checked: when you put your locale to /etc/default/locale, the shell spawn by /init will have, not that solves anything, but obviously there's a huge amount of hardcoded paths | 17:56:35 |
psvo | yes, I believe they do | 17:56:50 |
K900 | But that does not help us here because we need PAM on every process | 17:56:52 |
K900 | Because that's how we get LOCALE_ARCHIVE | 17:57:00 |
psvo | could we shim /init? :) | 17:57:28 |
K900 | We already are | 17:57:38 |
K900 | And it's not going to help | 17:57:41 |
K900 | Because they're spawning the shell processes completely outside /init | 17:57:49 |
psvo | we shim /sbin/init, right? | 17:57:53 |
K900 | What we need to do is shim the SHELL | 17:57:55 |
K900 | Oh no we can't shim the WSL /init | 17:58:05 |
K900 | It's bind-mounted from inside the utility distro | 17:58:16 |
Arson Copperflame | Hey, at least we have experience shimming the shell /s | 17:58:46 |
K900 | WE DON'T | 17:58:51 |
K900 | That's the problem | 17:58:54 |