/etc/duress.d scripts should run after ~/.duress scripts #21
Comments
nuvious
added a commit
that referenced
this issue
Apr 4, 2022
* Swapped the user and global run order per issue #21 intent. * Forgot to pull main becore starting. Updated version, changelog, spelling pass on all files, and linted with clang-tidy. * Removed dockerfile inadvertently comitted to repo. * Fixed a minor grammar issue and nit-picked line lengths.
|
Closed in most recent PR. Merged on my end based on personal testing. Couldn't find a reviewer unforunately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/etc/duress.d scripts should be run after ~/.duress script to allow for a script to be implemented that removes pam-duress itself as a cleanup action. In the current implementation one would have to write a delayed-action script to remove pam-duress system-wide which if misconfigured may allow an attacker to see the modules presence after the attacker has dropped to a user shell.
The text was updated successfully, but these errors were encountered: