SSH Access to Windows 10 Pro Workstations

DustinB3403

There's documentation like this which would seem to indicate that setting up Windows 10 1809 as an SSH server is perfectly acceptable, and then there is the EULA which says:

 c.      Restrictions. The device manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement. For example, this license does not give you any right to, and you may not:

(v)     use the software as server software, for commercial hosting, make the software available for simultaneous use by multiple users over a network, install the software on a server and allow users to access it remotely, or install the software on a device for use only by remote users;

d. Multi Use scenario 

(vi)    Remote assistance. You may use remote assistance technologies to share an active session without obtaining any additional licenses for the software. Remote assistance allows one user to connect directly to another user’s computer, usually to correct problems.

Which an is a bit of a conflicting statement, unless we only look at d. vi where it states "usually to correct problems".

So using powershell and running Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0 I should be in perfectly fine shape, yes?

IRJ

That does seem pretty cool

https://docs.microsoft.com/en-us/powershell/scripting/learn/remoting/ssh-remoting-in-powershell-core?view=powershell-6

IRJ

Is microsoft going to inspect your SSH traffic now?

DustinB3403

@IRJ said in SSH Access to Windows 10 Pro Workstations:

Is microsoft going to inspect your SSH traffic now?

They don't have too, but they could have the option if the license restricts it.

scottalanmiller

@DustinB3403 said in SSH Access to Windows 10 Pro Workstations:

There's documentation like this which would seem to indicate that setting up Windows 10 1809 as an SSH server is perfectly acceptable, and then there is the EULA which says:
 c.      Restrictions. The device manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement. For example, this license does not give you any right to, and you may not:

(v)     use the software as server software, for commercial hosting, make the software available for simultaneous use by multiple users over a network, install the software on a server and allow users to access it remotely, or install the software on a device for use only by remote users;

d. Multi Use scenario 

(vi)    Remote assistance. You may use remote assistance technologies to share an active session without obtaining any additional licenses for the software. Remote assistance allows one user to connect directly to another user’s computer, usually to correct problems.
Which an is a bit of a conflicting statement, unless we only look at d. vi where it states "usually to correct problems".

So using powershell and running Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0 I should be in perfectly fine shape, yes?

On Server, no issue. SSH the same as with Linux. SSH on Windows 10 is "single user" just like anything else on Windows 10.

DustinB3403

@scottalanmiller said in SSH Access to Windows 10 Pro Workstations:

On Server, no issue. SSH the same as with Linux. SSH on Windows 10 is "single user" just like anything else on Windows 10.

So then why would they have the statement about "usually to correct problems" as to me this would be a two person use. One who is using the desktop and the other administrator who is working on fixing an issue via ssh (presumably while the other user is using said system).

JaredBusch

@DustinB3403 said in SSH Access to Windows 10 Pro Workstations:

@scottalanmiller said in SSH Access to Windows 10 Pro Workstations:

On Server, no issue. SSH the same as with Linux. SSH on Windows 10 is "single user" just like anything else on Windows 10.

So then why would they have the statement about "usually to correct problems" as to me this would be a two person use. One who is using the desktop and the other administrator who is working on fixing an issue via ssh (presumably while the other user is using said system).

I'm not bothering to reread anything, but MS has long allowed admin connections.

marcinozga

@DustinB3403 said in SSH Access to Windows 10 Pro Workstations:

@scottalanmiller said in SSH Access to Windows 10 Pro Workstations:

On Server, no issue. SSH the same as with Linux. SSH on Windows 10 is "single user" just like anything else on Windows 10.

So then why would they have the statement about "usually to correct problems" as to me this would be a two person use. One who is using the desktop and the other administrator who is working on fixing an issue via ssh (presumably while the other user is using said system).

The same statement says to share an active session. 2 users sharing the same session, not 2 users with 2 different sessions.

scottalanmiller

@DustinB3403 said in SSH Access to Windows 10 Pro Workstations:

@scottalanmiller said in SSH Access to Windows 10 Pro Workstations:

On Server, no issue. SSH the same as with Linux. SSH on Windows 10 is "single user" just like anything else on Windows 10.

So then why would they have the statement about "usually to correct problems" as to me this would be a two person use. One who is using the desktop and the other administrator who is working on fixing an issue via ssh (presumably while the other user is using said system).

Yes, a support user is always allowed. Basically SSH is the same as RDP here.

Obsolesce

@JaredBusch said in SSH Access to Windows 10 Pro Workstations:

@DustinB3403 said in SSH Access to Windows 10 Pro Workstations:

@scottalanmiller said in SSH Access to Windows 10 Pro Workstations:

On Server, no issue. SSH the same as with Linux. SSH on Windows 10 is "single user" just like anything else on Windows 10.

So then why would they have the statement about "usually to correct problems" as to me this would be a two person use. One who is using the desktop and the other administrator who is working on fixing an issue via ssh (presumably while the other user is using said system).

I'm not bothering to reread anything, but MS has long allowed admin connections.

Yes this has been a known fact for as long as i can remember... Admins are exempt for administrative purposes.