From: Assaf Gordon <assafgordon@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin, OpenSSH and multiple-user licensing (CAL)
Date: Thu, 26 Oct 2017 20:54:00 -0000 [thread overview]
Message-ID: <cc75be24-c5f9-db49-1af0-0ab1321065b3@gmail.com> (raw)
In-Reply-To: <7da1d07c-68c0-43dd-2ad0-d145c229693c@gmail.com>
Follow-up:
On 2017-10-25 06:22 PM, Assaf Gordon wrote:
> When running OpenSSH server under cygwin on a windows machine,
> does each SSH connection require a buying CAL (client access license)
> from microsoft?
Wes Miller, Research VP at Microsoft [1] answered my similar question
on the PowerShell/OpenSSH github project [2].
Basically, an OpenSSH server (PowerShell,Cygwin and any other[3]) fall
under the same restrictions as other remote access types.
For windows "server" editions: CALs required for all users connecting to
SSH.
For "desktop/client/home/pro" editions: governed by the same limitation
as remote connections. Only one user at a time (and likely only the
"Primary user") can access the machine remotely.
[1] Wes Miller: https://twitter.com/getwired
[2] Github answer:
https://github.com/PowerShell/Win32-OpenSSH/issues/926#issuecomment-339786079
[3] different vendors do not alter the answer (e.g. Microsoft program vs
cygwin program): https://twitter.com/getwired/status/923643485911224331
regards,
- Assaf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2017-10-26 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 0:22 Assaf Gordon
2017-10-26 0:36 ` Stephen John Smoogen
2017-10-26 20:54 ` Assaf Gordon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc75be24-c5f9-db49-1af0-0ab1321065b3@gmail.com \
--to=assafgordon@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).