Closed JeremySkinner closed 6 years ago
Yes, I did commit the follow up but looks like I forgot to push it. Will do so when I'm back at my pc.
@dahlbyk @rkeithhill I've pushed up the missing change.
This doesn't change the environment variable scope for the calls to Get-TempEnv
in the main module file, I don't think this is a big deal, but do we want to introduce a global variable to control this? My inclination would be no
setenv
doesn't understand your third parameter:
This doesn't change the environment variable scope for the calls to
Get-TempEnv
in the main module file, I don't think this is a big deal, but do we want to introduce a global variable to control this? My inclination would be no
Get-TempEnv
is already explicitly user-scoped rather than process-scoped, and it doesn't make sense for it to be machine-scoped, so I think this is fine. In fact, it doesn't seem useful or correct to allow Start-SshAgent -Scope Machine
either, as this could leak the current user's credentials to another user. Am I missing a legitimate scenario for that?
@dahlbyk Good point, I'll remove the option for machine scope and leave just process/user.
Not sure why my change to setenv isn't showing up in the PR, it shows in my local repo. I'll force push it up.
@dahlbyk force push seems to have done it, the changes are showing now and I've removed machine scope from the options list.
Allows changing the environment variable scope from Process to User/Machine. Also updated
Stop-SshAgent
andGet-SshAgent
to work with win32 openssh.