Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ssh-copy-id results in immediate lockout #21

Open
rcoder opened this issue Aug 21, 2020 · 0 comments
Open

ssh-copy-id results in immediate lockout #21

rcoder opened this issue Aug 21, 2020 · 0 comments

Comments

@rcoder
Copy link

rcoder commented Aug 21, 2020

I can pull detailed logs if it would help, but the basic use case seems consistent with each of the ~half-dozen CL hosts I've deployed in the cloud:

  1. SSH to a remote host using password auth for the normal installer-created user, then log out: ✅
  2. Run ssh-copy-id to install the local client (ed25519) SSH public key into authorized_keys on the same host
  3. ...watch the copy hang at INFO: 1 key(s) remain to be installed..., after which tallow has banned the client IP: 😢

I'm guessing there's a logfile parsing issue where the handshake used to query existing keys appears as a failed auth and results in the ban, but this exact workflow is part of how I bootstrap a new server or workstation so it's honestly a PITA that tallow locks me out 100% of the time when I do it, after which I have to log in via the actual server console and whitelist client IPs and flush firewall rules to unlock my access.

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

No branches or pull requests

1 participant