public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: cygwin-licensing@cygwin.com
Subject: Re: 1NIWGYC.DLL ??
Date: Sun, 18 Dec 2005 19:01:00 -0000	[thread overview]
Message-ID: <20051218183739.GA4704@trixie.casa.cgf.cx> (raw)
In-Reply-To: <004801c60281$e7b6a020$2602a8c0@itefixb>

I was going to just let this go but, after talking to Corinna and
learning that we're on the same page about this, I guess I can't.

On Fri, Dec 16, 2005 at 09:47:17PM +0100, Tevfik Karag?lle wrote:
>Thanks for your feedback.  As long as I understand, what I intend to do
>does not violate Cygwin licensing.
>
>On Thu, Dec 15, 2005 at 06:35:24PM -0800, Brian Dessent wrote:
>
>>Just renaming the DLL and registry keys is not enough to avoid
>>conflicts with an existing cygwin1.dll.  You will also have to modifiy
>>the name of the shared memory region and all other shared objects.
>
>Ok.  Renaming DLLs, registry references and shared memory name
>(cygwin1S4??) would be worth to try then.
>
>>It seems like there is no benefit to this distribution if the user is
>>running cygwin anyway.  If they are running cygwin then they should
>>just use the openssh that comes with cygwin.
>
>I am not so sure about it.  I am a dedicated cygwin user since early
>90s.  However, I don't want to run an ssh daemon within my cygwin
>development environment, where I might try/test many different things.
>What I want to is to establish a secure channel to my machine remotely
>by using ssh daemon, running its own limited and safe environment for
>the sake of security.  The same applies for an rsync environment where
>a crucial operation like a remote backup can be initiated.  I think
>those special environments require their own setup.

You seem to have skipped over my observation that some cygwin
applications won't work very well in your 1NIWGYC.DLL environment.

I don't know what you mean by "cygwin development environment" but,
AFAIK, you are not developing the cygwin DLL.  If you are just
downloading the latest version of the cygwin distribution and don't want
to somehow destabilize your openssh setup then it seems like working
with the setup.exe and openssh maintainers is the best way to accomplish
this.

It really sounds like you are interested in providing workarounds for
what you perceive to be problems with the cygwin distribution rather
than working towards fixing the problems.  I suspect that your efforts
will just serve to confuse people and so I'm not happy with the way you
are proceeding and I will certainly publicly express my dissatisfaction
the first time someone posts a question about "your" version of openssh
and whatever-you-call-the-dll on the cygwin list.

So, yes, this is a GPL project and you can take the software, rename it
and massage it to do whatever you want with it.  That does not mean that
it is the right thing to do or that your efforts will be appreciated by
the people who are providing the software, however.

cgf

  parent reply	other threads:[~2005-12-18 19:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16 20:50 Tevfik Karagülle
2005-12-18 17:10 ` Reini Urban
2005-12-18 19:01 ` Christopher Faylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-19 12:20 Tevfik Karagülle
2005-12-16  2:19 Tevfik Karagülle
2005-12-16  2:57 ` Brian Dessent
2005-12-16  3:20   ` Christopher Faylor

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=20051218183739.GA4704@trixie.casa.cgf.cx \
    --to=me@cgf.cx \
    --cc=cygwin-licensing@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).