cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lars Tobias Skjong-Børsting (JIRA) <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-10067) Fix a case where a user 'ro' or 'roo' exists on the system
Date Fri, 08 Sep 2017 10:25:00 GMT
Lars Tobias Skjong-Børsting created CLOUDSTACK-10067:
--------------------------------------------------------

             Summary: Fix a case where a user 'ro' or 'roo' exists on the system
                 Key: CLOUDSTACK-10067
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10067
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: Lars Tobias Skjong-Børsting


Fix a case where a user 'ro' or 'roo' exists on the system or other variants, like 'cen' and
'centos'.
If one sets user=roo, this will return two directories (/root /home/roo) and then it will
fail.

Also, if user 'ro' or 'roo' does not exist, this will happily put the sshkey to the authorized_keys
of the root account, which is not the intended place.

As another slightly less improbable example, if we have two users in our company named lars,
then we could end up with lars's sshkey in larsb's authorized_keys.

The binary getent should be available on most Linux platforms, including ones using uClibc.

Pull Request on Github, see external URL.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message