Skip to content

u2f desktop login: remove nouserok and add troubleshooting#568

Open
blu-nitro wants to merge 10 commits into
mainfrom
push-lovyyquwztnz
Open

u2f desktop login: remove nouserok and add troubleshooting#568
blu-nitro wants to merge 10 commits into
mainfrom
push-lovyyquwztnz

Conversation

@blu-nitro
Copy link
Copy Markdown
Member

@blu-nitro blu-nitro commented Apr 21, 2026

nouserok appears to be ignored on Ubuntu. Login with password still possible without it if sufficient control flag is used.

fixes #278

Added troubleshooting guide for issues caused by gdm when certain pkcs packages are installed.
General updates and cleanup.

@blu-nitro blu-nitro requested a review from daringer April 21, 2026 16:10
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 21, 2026

The successful documentation build for 8244db5 was deployed for preview:

generated by workflow run 24895582147 (attempt 1)

@jans23
Copy link
Copy Markdown
Member

jans23 commented Apr 22, 2026

  • It talks about "Nitrokey FIDO2" while instead the text should be generic for all applicable Nitrokey models.
  • Ubuntu 20.4 is outdated
  • "GUI Method" and "CLI Method" sounds as this would be alternative. Instead they
  • Is "Set up the rules" still required these days with a recent distribution? I doubt so.

@jans23
Copy link
Copy Markdown
Member

jans23 commented Apr 22, 2026

The last line is wrongly indented.

`nouserok` is not needed to allow login with password
gui method for creating a user account serves no real purpose, as the 
rest of the documentation requires the user to be comfortable with cli anyway
on modern operating systems this should no longer be necessary
also udev rule setup is described in all troubleshooting pages of the relevant nitrokey models
@blu-nitro blu-nitro requested a review from jans23 April 23, 2026 14:38
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
Comment thread source/components/nitrokeys/features/u2f/desktop-login.rst Outdated
@blu-nitro blu-nitro requested a review from jans23 April 24, 2026 14:28
reflect the fact that pamu2fcfg by default generates the config for the current user
instead describe how to configure for multiuser properly
Copy link
Copy Markdown
Member

@jans23 jans23 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Explain in the introduction: Is this adding a NK as a 2nd factor in addition to a password or does it replace the password? Or will the user have the choice between password and NK usage?


.. rstcheck: ignore-next-code-block
.. code-block:: bash
This step is optional, however it is advised to have a backup Nitrokey in the case of loss, theft or destruction of your primary Nitrokey.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Elaborate that this requires a second Nitrokey device. This fact is not clear. Maybe just a single sentence would be sufficient such as "repeat the step to configure another Nitrokey as backup device"

Also the heading "Backup" is not very precise or misleading.


$ cd /etc/pam.d
$ sudo $editor common-auth
$ sudo $EDITOR /etc/pam.d/common-auth
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  $ sudo editor /etc/pam.d/common-auth


.. contents:: :local:

.. warning::
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move the warning after the introduction

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Insecure PAM configuration for u2f devices

2 participants