I'm glad Windows 10 has OpenSSH now:
> Microsoft Windows [Version 10.0.17763.437]
> (c) 2018 Microsoft Corporation. All rights reserved.
> > ssh -V
> OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
I've found the built-in Windows 10 ssh client has trouble with tunneling, so I still use the ssh client included with git.
If you can figure out how to reproduce the issue, I'm sure the team would accept a bug report at https://github.com/PowerShell/Win32-OpenSSH
netsh interface portproxy add v4tov4 listenport=8001 connectport=80 connectaddress=1.1.1.1
Re:“Python's batteries are leaking”
by throwaway2048 on Sunday May 19, 2019 @12:29PM
(#19954082)
this isn't useful for tunneling through a remote machine (which is what ssh does)
I've been checking but I can't add the module. Either it's slow to get to Enterprise version or it's blocked. Not sure.
Found a work-around though - Google cloud shell being *nix works fine for SSHing about the place. Gets me around the port fw too
Not OP but same. I'm currently debating with myself whether I should attempt to install PUTTY. Given that port 22 is blocked and it's not needed for my core role it'll be dicey if I get challenged.
Pulling executable code off some repo...no way that is ever officially passing muster. People might do it anyway, but on a personal risk basis.
>Can you explain this more?
Place that are heavy on confidential financial info basically. Practically everything I touch is confidential client data. So employer is naturally jumpy about what's on my laptop software wise.
Ironically the above comes full circle...need putty to get onto a VM in cloud where there are no restrictions and crucially no client data. Nobody cares what I do there - hell they'll even pay for it thanks for MSDN enterprise