Cave Amber :mashtenjar: on Nostr: fucking hell though i was trying to generate my own /usr/share/pam-configs/ ...
fucking hell though i was trying to generate my own /usr/share/pam-configs/ pam-config for pam-auth-update & i got far enough but i couldn't get it to actually do what i wanted.
```
auth required pam_faillock.so preauth
auth [success=1 default=ignore] pam_unix.so nullok
auth [default=die] pam_faillock.so authfail
auth sufficient pam_faillock.so authsucc
```
right so following the very fucking lackluster docs
https://wiki.ubuntu.com/PAMConfigFrameworkSpec... and also viewing other files in that directory... I thought...
```
Name: Faillock
Default: no
Priority: 256
Auth-Type: Primary
Auth:
required pam_faillock.so preauth
[default=die] pam_faillock.so authfail
sufficient pam_faillock.so authsucc
Account-Type: Primary
Account:
required pam_faillock.so
```
of course... that was great but the resulting output was mangled with pam-configs/unix
so i ended up getting a resulting output of...
```
auth [success=1 default=ignore] pam_unix.so nullok
auth required pam_faillock.so preauth
auth [default=die] pam_faillock.so authfail
auth sufficient pam_faillock.so authsucc
```
which i went oh fuck okay this is gonna be a bit more difficult. still haven't bothered to fix it i just edited my config by hand after using pam-auth-update to disable my template.
Published at
2024-06-22 16:59:05Event JSON
{
"id": "38a6f6493ace94aa4c447a7ac4a9e9d2aea90e77188345236ada5c501e49fc8f",
"pubkey": "191c663309451f1310e71171bbd87d8d0cd7f28d7a3a1a16e34f65beb9bfeb59",
"created_at": 1719075545,
"kind": 1,
"tags": [
[
"e",
"5839dc64b4b7541e8dac007c6ef52d6149b6816ef2052c70b60d178fbf6c9dc8",
"",
"reply"
],
[
"p",
"191c663309451f1310e71171bbd87d8d0cd7f28d7a3a1a16e34f65beb9bfeb59"
],
[
"e",
"fe9d2e3cb26e2a1317b2bb42b4a107db458230af2f4b6b380381971cd2e27c89",
"",
"root"
],
[
"proxy",
"https://woem.men/notes/9utxi9udgow207r5",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://woem.men/notes/9utxi9udgow207r5",
"pink.momostr"
],
[
"expiration",
"1721669453"
]
],
"content": "fucking hell though i was trying to generate my own /usr/share/pam-configs/ pam-config for pam-auth-update \u0026 i got far enough but i couldn't get it to actually do what i wanted.\n\n```\nauth required pam_faillock.so preauth\nauth [success=1 default=ignore] pam_unix.so nullok\nauth [default=die] pam_faillock.so authfail\nauth sufficient pam_faillock.so authsucc\n```\n\nright so following the very fucking lackluster docs https://wiki.ubuntu.com/PAMConfigFrameworkSpec... and also viewing other files in that directory... I thought...\n\n```\nName: Faillock\nDefault: no\nPriority: 256\nAuth-Type: Primary\nAuth:\n required pam_faillock.so preauth\n [default=die] pam_faillock.so authfail\n sufficient pam_faillock.so authsucc\nAccount-Type: Primary\nAccount:\n required pam_faillock.so\n```\nof course... that was great but the resulting output was mangled with pam-configs/unix\n\nso i ended up getting a resulting output of... \n\n```\nauth [success=1 default=ignore] pam_unix.so nullok\nauth required pam_faillock.so preauth\nauth [default=die] pam_faillock.so authfail\nauth sufficient pam_faillock.so authsucc\n```\n\nwhich i went oh fuck okay this is gonna be a bit more difficult. still haven't bothered to fix it i just edited my config by hand after using pam-auth-update to disable my template.",
"sig": "d3de5b89c3041ce3b227007aef8b7d0de84b67c508fb9b5f3ef92f4131f27938d31648a5e7ee91f2ca2db9c3a0225a7ce363055535a4bf19b2aecc5a59193118"
}