You are not logged in.
Setting Up fscrypt filesystem /home for user
have read in fscrypt arch.wiki that pam_fscrypt.so
needs to be in /etc/pam.d/system-login [owned by pambase]
and /etc/pam.d/passwd [owned by shadow]
Could config pacman to ignore those packages pambase and shadow.
But know pambase has not changed in over a year, But some other
package makes changes to /etc/pam.d/system-login.
iF pam_fscrypt.so is not the above /etc/pam.d/files will not login to deCrypt files??
Not enough fscrypt user for a pacnew file.
TIA
Last edited by carlday (2020-07-07 05:28:17)
Offline
Both of the files you mentioned are in the backup file array of the packages that own them. Pacman will not attempt to overwrite your modifications.
Last edited by Trilby (2020-07-03 20:41:20)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I don't think making /etc/pam.d/system-login read-only is the right decision. Are you worried that you would miss the "pacnew" notification if those files were updated and you would get locked out of your home folder?
I'm not following what you mean by "Not enough fscrypt user for a pacnew file" - can you clarify?
Whichever way you approach the problem, you still will have to manually deal with any changes that an upgrade to pambase or shadow will introduce before you reboot?
Offline
Did search on pamBase, creator said arch users helped on that set of files.
Have Post UpGrade scripts [sed,rm] that run, part of scripts on the system-login file.
Always login to tty, no DM. Can add extra MSG to root login about post-Syu.
Can add a copy of the two pam-files with ending .good for backup for quick fix
Offline
Can add a copy of the two pam-files with ending .good for backup for quick fix
What is this a "fix" for? They are already in the backup array: pacman will not overwrite your content.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I have not encountered a single package that doesn't have files in /etc in the backup array.
Last edited by Awebb (2020-07-07 13:41:30)
Offline
Well, lots of packages have files in /etc that are not in their backup array. These are just the ones currently installed on my system that meet that criteria:
ca-certificates-utils
dnssec-anchors
e2fsprogs
fakeroot
filesystem
fontconfig
gawk
glibc
gpm
iproute2
iptables
libtirpc
libvdpau
neomutt
openssh
openssl
p11-kit
perl
systemd
texlive-core
tslib
ttf-dejavu
But the files mentioned in this thread are most certainly in backup arrays.
Last edited by Trilby (2020-07-07 12:45:19)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Indeed, Trilby. I just re-read my sentence and completely withdraw my comment.
Offline