@Michael: while I left out a word, that is precisely what I was getting at with this comment:
"because the snap's HOME is set to ~/snap/name/revision and not what getpwent() returns (eg, /home/user), ssh shipped in the snap [sic. may] or not may need to be told where the .ssh directory is. This is bug #1636229 (see comment 11 in particular)"
Since the use of getpwent() is now confirmed, I believe what I outlined in https://bugs.launchpad.net/snappy/+bug/1606574/comments/7 as a possible design is how this interface should be written, if it is going to be implemented.
Note that people shouldn't feel blocked by this: people can ship their own ssh binaries and use 'ssh -F $HOME/.ssh/config -i $HOME/.ssh/id... ...' with any other options to have ssh use the files in /home/<user>/snap/$SNAP/$SNAP_REVISION/.ssh (ie, the value of $HOME with the 'ssh -i' command) such as -S, -o, etc.
@Michael: while I left out a word, that is precisely what I was getting at with this comment:
"because the snap's HOME is set to ~/snap/ name/revision and not what getpwent() returns (eg, /home/user), ssh shipped in the snap [sic. may] or not may need to be told where the .ssh directory is. This is bug #1636229 (see comment 11 in particular)"
Since the use of getpwent() is now confirmed, I believe what I outlined in https:/ /bugs.launchpad .net/snappy/ +bug/1606574/ comments/ 7 as a possible design is how this interface should be written, if it is going to be implemented.
Note that people shouldn't feel blocked by this: people can ship their own ssh binaries and use 'ssh -F $HOME/.ssh/config -i $HOME/.ssh/id... ...' with any other options to have ssh use the files in /home/< user>/snap/ $SNAP/$ SNAP_REVISION/ .ssh (ie, the value of $HOME with the 'ssh -i' command) such as -S, -o, etc.