From: Assaf Gordon <assafgordon@gmail.com>
To: cygwin@cygwin.com
Subject: Cygwin, OpenSSH and multiple-user licensing (CAL)
Date: Thu, 26 Oct 2017 00:22:00 -0000 [thread overview]
Message-ID: <7da1d07c-68c0-43dd-2ad0-d145c229693c@gmail.com> (raw)
Hello,
When running OpenSSH server under cygwin on a windows machine,
does each SSH connection require a buying CAL (client access license)
from microsoft?
More concretely,
If I have a "Windows 10 Home" and I run Cygwin + OpenSSH server,
can multiple users connect and run programs at the same time?
(of course they technically can, but is it legally allowed?).
This assumes the users only run Cygwin programs, never any windows
programs, and not any RDS connections or GUI applications (not even X11).
Sorry if this is slightly off-topic for the technical list,
but I can't find any reliable information regarding this question.
The only somewhat-related post I've managed to found is this one
from 1999 about running Samba on Windows NT, saying:
If we overcome this, Samba will work on NT. I have done a research
on the legal/license implications of this, and look very
interesting:
* The legal limit of 10 connections to an NT workstation
dissapear => NT server value for NT workstation price, legal.
* No need for CAL (client access license) to connect to an NT
box => legal non Win clients, and the NT Terminal server client
implications seem interesting too.
(from http://www.cygwin.com/ml/cygwin/1999-09/msg00046.html )
Is running OpenSSH server considered the same as running samba?
Any feedback is appreciated.
Thanks,
- Assaf Gordon
--
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
next reply other threads:[~2017-10-26 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 0:22 Assaf Gordon [this message]
2017-10-26 0:36 ` Stephen John Smoogen
2017-10-26 20:54 ` Assaf Gordon
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=7da1d07c-68c0-43dd-2ad0-d145c229693c@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).