[BUG] Inconsistent use of args in ssh_auth.managed #64442
Labels
Bug
broken, incorrect, or confusing behavior
severity-medium
3rd level, incorrect or bad functionality, confusing and lacks a work around
State-Module
Milestone
Description
ssh_auth.managed does not fully respect arguments such as config, fingerprint_hash_type, options, etc
In particular, it will happily use all of the args available when making sure that keys are present, always putting new keys into their correct places. However, when determining what keys to remove or modify, it won't, always using the default
~/.ssh/authorized_keys
file, and other such default options forssh.auth_keys
andssh_auth.absent
callsSetup
Standard setup in v3005 or v3006. Doesn't matter if it's a VM, on-prem or anything else. It is linux-only, however
Please be as specific as possible and give set-up details.
Steps to Reproduce the behavior
I originally spotted this bug while using a different config file, so!
~/.ssh/authorized_keys
ssh_auth.managed
and specify a different path forconfig
. Use one or more different keys to those you added to the default file~/.ssh/authorized_keys
have been removedExpected behavior
All functions called by
ssh_auth.managed
should respect arguments provided where applicableScreenshots
If applicable, add screenshots to help explain your problem.
Versions Report
N/A, exists in v3005 and v3006's code. Haven't checked other releases
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: