Skip to content

Handle PAM_RUSER and PAM_USER being identical#21

Open
AlD wants to merge 1 commit into
jbeverly:masterfrom
AlD:user-ruser
Open

Handle PAM_RUSER and PAM_USER being identical#21
AlD wants to merge 1 commit into
jbeverly:masterfrom
AlD:user-ruser

Conversation

@AlD

@AlD AlD commented Dec 30, 2019

Copy link
Copy Markdown

Warns if PAM_RUSER and PAM_USER are identical. Bails out if additionally
allow_user_owned_authorized_keys_file is enabled.
If authorized_keys_file is allowed to be owned by user, and user is identical
with ruser, this means that the calling user (i.e. ruser) can add arbitrary keys
to it, thus rendering the whole PAM step useless.

Fixes #17, but will cause the module to stop working in the described situation.
This is fine, as in this scenario, this module poses a massive security gap.

Warns if PAM_RUSER and PAM_USER are identical. Bails out if additionally
allow_user_owned_authorized_keys_file is enabled.
If authorized_keys_file is allowed to be owned by user, and user is identical
with ruser, this means that the calling user (i.e. ruser) can add arbitrary keys
to it, thus rendering the whole PAM step useless.

Fixes jbeverly#17, but will cause the module to stop working in the described situation.
This is fine, as in this scenario, this module poses a massive security gap.
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.

allow_user_owned_authorized_keys_file permits privilege escalation

1 participant