Comment 3 for bug 354288

Revision history for this message
Todd Deshane (deshantm) wrote :

At first I tried to go the os.chown way, but there were a few complications that made the code less elegant.

First, the chown command takes, as the 2nd and 3rd arguments, the uid and gid of the user. The user that needs to own the .ssh directory and its contents is a user that is created within the chroot. While it is possible to get the information with the pwd module, it is a lot easier to simply do the chroot and then use chown command within the chroot.

Other suggestions or code are welcome for review. I am not a developer on this project, so it will be up to them on what they accept/commit as a fix.