Subauthentication

Corinna Vinschen vinschen@redhat.com
Fri Dec 13 04:07:00 GMT 2002


On Mon, Dec 09, 2002 at 10:12:16PM +0100, Hartmut Honisch wrote:
> I see a legal issue though. If I understand the NT4 DDK license agreement
> correctly, we're not allowed to freely distribute  lsadll.lib and ntdll.lib
> (even though it's available for free), which would be required to create
> cyglsa.dll. However, we should are allowed to use the lib-files to create a
> dll (=> cyglsa.dll) and distribute that dll instead. If a developer wants to
> build cyglsa.dll himself, he'll have to download the NT4 DDK from somewhere,
> but I think that will be necessary very rarely.

A question:  When building the subauth dll, do you have to build
two versions, one for NT4 and one for 2k/XP?  

Otherwise to workaround licensing... any chance to use autoload
techniques as in cygwin/autoload.cc?  Otherwise we could just
change the creation of the subauth dll in the subauth directory
so that the make doesn't stop even though building of the dll
failed due to missing libs.  At least we shouldn't have the
situation that a developer needs the DDK to build Cygwin.

> Finally some remarks to using network resources. Subauthentication is only
> supported for network logons, and those don't create logon sessions. So, at
> first, when I was in a ssh session and wanted to connect network resources,
> Windows' "net use" returned an error message telling me that there was no
> active logon session. But there is a workaround for that: _Always_ specify
> username and password ("net use \\server\share mypassword
> /user:Domain\user"), and you _will_ be able to connect to the network
> resources.

That's completely ok.  It's way better than having no access to
network shares.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.



More information about the Cygwin-developers mailing list