You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2022. It is now read-only.
One issue some clients have raised has been around management of SSH keys. Often times, clients do not know what SSH keys they have installed. This can be a big attack vector.
Do do this in a solid way, we need to take the following steps:
First we identify the path for the authorized_keys location(s):
One issue some clients have raised has been around management of SSH keys. Often times, clients do not know what SSH keys they have installed. This can be a big attack vector.
Do do this in a solid way, we need to take the following steps:
First we identify the path for the authorized_keys location(s):
Next, we need to look up all shells:
We then need to look for all users with one of these valid shells, and extract their home directory:
Finally, we can traverse the list, which would be:
With the above data, we need to submit it upstream and report both the key(s) in the authorized_keys files, along with the corresponding user.
Known issues:
The text was updated successfully, but these errors were encountered: