[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug/Problem ${HOME} variable not honored on WIndows
[Thread Prev] | [Thread Next]
- Subject: Re: Bug/Problem ${HOME} variable not honored on WIndows
- From: Andreas Schneider <asn@xxxxxxxxxxxxxx>
- Reply-to: libssh@xxxxxxxxxx
- Date: Tue, 15 Jan 2019 07:52:29 +0100
- To: libssh@xxxxxxxxxx
- Cc: Duane Ellis <duane@xxxxxxxxxxxxxx>
On Thursday, January 10, 2019 7:54:35 PM CET Duane Ellis wrote:
> Problem statement:
>
> Users get DIFFERENT HOME directory locations depending if they are
> attached to windows network (ie: corporate network)
>
> Or if the user is not attached to the Server.
>
>
> Where this occurs:
>
> This problem boils up into GIT on Windows when switching between a
> network configuration and a non-network configuration
>
>
> Where does the problem occur:
>
>
> This problem occurs in the function ${libssh}/src/misc.c - function
> ssh_get_user_home_dir()
>
>
> The windows implementation should honor the $HOME variable, it currently
> does not.
>
>
> The windows implementation calls SHGetSpecialFolderPath( ..., CSIDL_PROFILE,
> TRUE )
>
>
> Effectively - this is described as: C:\users\<USERNAME> - aka: The windows
> Home Directory
Which seems to be correct as profiles are normally synced when logging in an
out.
>
> HOWEVER - when attached to a microsoft network this often becomes a location
> on the corporate network, I believe this has to do with "roaming profiles"
> - of which I cannot control the corporate powers that be - they make the
> rules not me, I live with the rules.
>
>
> The result of which is that "~/.ssh" - dynamically changes from
> c:\users\<USERNAME>\.ssh to \\someserver\someplace\yourprofile
But this only happens in MinGW?
Andreas
--
Andreas Schneider asn@xxxxxxxxxxxxxx
GPG-ID: 8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D
| RE: Bug/Problem ${HOME} variable not honored on WIndows | Duane Ellis <duane@xxxxxxxxxxxxxx> |
| Bug/Problem ${HOME} variable not honored on WIndows | Duane Ellis <duane@xxxxxxxxxxxxxx> |