-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
If the Conduit is in its initial state, it can be hard to log in.
- the conduit has a default password and no ssh authorized_keys
- the user has a lot of keys loaded via
ssh add - ssh and sshd exchange the loaded keys before going to pasword auth
- but sshd is configured to only try three times
The result is that sshd fails due to testing loaded keys before it drops to password auth.
The workaround is ssh-add -D, which deletes all loaded keys. But this will be confusing and awkward for our users.
Metadata
Metadata
Assignees
Labels
No labels