Location of authorized_keys is not parsed correctly
Bug #1270896 reported by
Chris Stratford
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Unassigned |
Bug Description
For ${reasons} we have our own openssh-server package. One of the changes is the value of AuthorizedKeysFile in /etc/ssh/
AuthorizedKeysFile /etc/ssh/
It looks like Juju is parsing the sshd_config file, as on a newly MaaS/Juju installed server I ended up with the ubuntu user's key in:
/etc/ssh/
(note the space in the middle)
So, it looks like Juju sees this as one long filename and not two distinct ones.
The file permissions may also be incorrect in this arrangement, as after moving the key to its correct location, I needed to chmod 0444 it (from 0400).
tags: | added: security ssh |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju-core: | |
importance: | High → Medium |
To post a comment you must log in.
This area has been drastically changed and this bug may have been addressed as part of this work on both Juju 1.25 and Juju 2.