| Summary: | ssh-copy-id errors and does not work | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thomas Bigot <thomas.bigot> |
| Component: | RPM Packages | Assignee: | Guillaume Rousse <guillomovitch> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | openssh-8.4p1-1.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Thomas Bigot
2020-11-12 20:38:45 CET
Thank you for reporting this. [The 'ssh-copy-id' command is in pkg openssh-clients]. > Now try logging into the machine, with: "ssh 'me@server'" > and check to make sure that only the key(s) you wanted were added You do not say whether you can log into the server. What happens when you do, or try to? > Looking at the server, no /home/me/authorized_keys has been created The man page says: "By default it adds the keys by appending them to the remote user's ~/.ssh/authorized_keys (creating the file, and directory, if necessary)" Is that file (path) you looked for? [To be assigned to guillomovitch]. CC:
(none) =>
lewyssmith I can’t then log into the server without a password afterwards. Sorry, it was a typo, I indeed expected to find the new key in ~/.ssh/authorized_keys. Thank you for these clarifications. I was not aware (stranger to this field) that what you are trying to achieve is remote login without the need to give a password. At least you can for the moment (it seems) login with one. Assigning to Guillaume for 'openssh'. CC:
lewyssmith =>
(none) Should be fixed with incoming openssh-8.4p1-2.mga8, thanks for reporting the issue. Resolution:
(none) =>
FIXED |