I'm using bash. The shell does the correct thing. Sorry didn't give the use case clearly. I'm talking about the use of tilde inside client config. The example was to illustrate desired behavior. Ssh itself does not eval tilde with any consideration for environment. That is the problem. Original Message From: Gert Doering Sent: Friday, May 19, 2017 02:19 To: matthew patton Cc: openssh-unix-dev@xxxxxxxxxxx Subject: Re: feature request: use HOME before getpwnam() in misc.c Hi, On Thu, May 18, 2017 at 09:51:04PM +0000, matthew patton wrote: > What is the use case? > > HOME=longpath_to_config1 > ssh -i ~/.ssh/key1 > > HOME=longpath_to_config2 > ssh -i ~/.ssh/key2 If you run things like that, the "~" is not expanded by ssh but by your shell. Try "echo ~/"... Barking up the wrong tree... gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert@xxxxxxxxxxxxxx fax: +49-89-35655025 gert@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
