Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
From:	"Hartmut Honisch" <hartmut_honisch AT web DOT de>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	RE: Subauthentication
Date:	Fri, 13 Dec 2002 14:51:05 +0100
Message-ID:	<NFBBLLCAILKHOEOHEFMHOEAKCEAA.hartmut_honisch@web.de>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
In-Reply-To:	<20021213140618.S7796@cygbert.vinschen.de>
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

> > However, we could of course just not support subauth on NT.
> Then we _could_
> > use the autoload stuff as it is now ...
>
> ...that sounds like the best approach to begin with.  For gods sake
> we have create_token which works on NT4.  The additional advantage
> of getting a fine logon session id would then require 2K or XP...
> which isn't too bad.

> If we require that stuff to work on NT4 from the beginning I fear we
> will get stuck in all the workaround and licensing hogwash.

It really wouldn't be a great effort to add NT4 support. I have a working
implementation of DLL that exports all the Lsa functions we need, and it
works on NT/2k/XP. And to work around the licensing problem, we could
distribute the sources _without_ the lib files from the DDK, plus DLL in
binary form. Even though the DDK license may prohibit the distribution of
its own files, it won't disallow the distribution of DLLs built with it.

And if a developer really wants to rebuild the dll, he'll have to download
the DDK from Microsoft to obtain the missing lib files.

Regards

Hartmut

- Raw text -