[00:06] <vorlon> mwhudson: I certainly agree that this is a bug in pam_env for not being more robust; not committing to the work to fix it though
[00:25] <mwhudson> vorlon: ack
[00:25] <mwhudson> vorlon: are you pam upstream too?
[00:38] <vorlon> mwhudson: certainly not actively
[00:39] <mwhudson> vorlon: ok. i'll file a bug there eventually
=== not_phunyguy is now known as phunyguy
=== genii is now known as genii-core
=== handsome_feng_ is now known as handsome_feng
=== doko_ is now known as doko
[11:31] <xnox> mwhudson:  what's the context for "it settling down" ?
=== dbungert1 is now known as dbungert
=== genii-core is now known as genii
[20:21] <mwhudson> xnox: i don't know, one of the releases definitely seemed like a bit of a climb down
[20:21] <mwhudson> xnox: i haven't checked the mailing list in a while though
[22:55] <mwhudson> vorlon: reported the pam bug fwiw https://github.com/linux-pam/linux-pam/issues/395
[22:55] <ubottu> Issue 395 in linux-pam/linux-pam "pam_env: leading = in envfile causes pam_open_session to fail" [Open]
[22:58] <vorlon> mwhudson: cheers
[22:59] <mwhudson> vorlon: i do hope the code in pam that parses user_envfile with handcrafted C runs as the user ...