Re: OpenSSH and $HOME
From: Phil Endecott (phil_nn05_at_chezphil.org)
Date: 06/14/05
- Previous message: Darren Tucker: "Re: Setting up tunnel across multiple systems?"
- In reply to: Darren Tucker: "Re: OpenSSH and $HOME"
- Next in thread: Darren Tucker: "Re: OpenSSH and $HOME"
- Reply: Darren Tucker: "Re: OpenSSH and $HOME"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 14 Jun 2005 13:07:35 GMT
Thanks for the quick response.
Darren Tucker wrote:
> Phil Endecott wrote:
>>I was hoping to persuade ssh to look somewhere non-standard for these
>>files by temporarily setting $HOME, but this doesn't seem to be
>>possible. So, is there any other way to influence it, apart from
>>changing /etc/passwd (or hacking the source)?
>
> Depends on the file. See, eg, "-F" in ssh(1) and "IdentityFile" in
> ssh_config(5).
OK, so it looks as if I can change the location of the known hosts file
by generating a temporary config file with "UserKnownHostsFile XXX" and
passing that temporary file using -F. It's a bit clunky but I think it
will work.
> What exactly are you trying to achieve?
Think "kiosk application". ssh always runs as the same unpriviledged
user who has no home directory; currently it complains about being
unable to read or write to known_hosts and other things in $HOME/.ssh.
If possible, I'd like to keep the known_hosts data, but nothing else,
from one session to the next based on the person using it (where person
!= unix user).
>>Would people agree that this is a documentation bug?
> Yes, but it's already been fixed:
Excellent!
Thanks,
--Phil.
- Previous message: Darren Tucker: "Re: Setting up tunnel across multiple systems?"
- In reply to: Darren Tucker: "Re: OpenSSH and $HOME"
- Next in thread: Darren Tucker: "Re: OpenSSH and $HOME"
- Reply: Darren Tucker: "Re: OpenSSH and $HOME"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]