An article how the authselect tool works, how you create and maintain custom profiles and how to apply them.
I stumbled upon this topic in context of configuring pam to enable u2f smartcard support.
Sources:
Metadata Update from @rlengland: - Issue assigned to w4tsn - Issue tagged with: article, needs-image, needs-series
I'm going to approve this but the normal process is to pose your article topic and outline to the editors via the Fedora Magazine discussion board rather than opening a new Pagure ticket. Two of the editors then approve it and open and assign the ticket to you.
But I don't believe there is likely to be discussion on this, so it's yours.
Oh, I'm sorry. I didn't intent to be rude / violate the procedure. I'll keep it in mind for the future.
This article was just mentioned on card #177. Beware, however, that there seems to be a problem with the PAM stack configuration I suggested. I just tested adding those two lines to the system-auth file and, while it seems to work for authentication, it seems to break the crond service. With those lines in place, I'm seeing the following when I run crontab -l.
crontab -l
$ crontab -l You (glb) are not allowed to access to (crontab) because of pam configuration.
And in the system log I'm seeing the following.
crontab[2909066]: (glb) PAM ERROR (The return value should be ignored by PAM dispatch)
I do not know why those lines are causing the crond service to fail.
@w4tsn Is this article still on your todo list?
Metadata Update from @w4tsn: - Assignee reset
@rlengland no, I'm not currently pursuing this. I removed myself from the ticket.
Metadata Update from @mariowritescode: - Issue assigned to mariowritescode
@rlengland
Working on this
@mariowritescode Are you still working on this article?
Log in to comment on this ticket.