You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2021. It is now read-only.
The problem is that the user can specify localhost, nodename, nodename.domain and these code treats them as different. It should not.
Because of this, directory tracking (the snippet above) does not work when the user specifies the hostname.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There is code in the module like this:
Location Changed handler that keeps the compatibility session PWD in sync with the parent PWD
This only applies on localhost.
$locationChangedHandler = {
[PSSession] $session = Initialize-WinSession -ComputerName $SessionComputerName -ConfigurationName $SessionConfigurationName -PassThru
if ($session.ComputerName -eq "localhost")
{
$newPath = $_.newPath
Invoke-Command -Session $session { Set-Location $using:newPath}
}
}
The problem is that the user can specify localhost, nodename, nodename.domain and these code treats them as different. It should not.
Because of this, directory tracking (the snippet above) does not work when the user specifies the hostname.
The text was updated successfully, but these errors were encountered: