>
> You're welcome to a copy, however...
>
> I'm at this moment totally rewriting it to serve a new system we're
> developing to replace what the original ND_GINA provided.
>
> The new version is a vastly stripped-down derivative of the
> original. The are three noteworthy functionality points it adds to
> a desktop system:
>
> 1) cooperates with a daemon on the NT Domain Controller to
> automatically (one-way) synchronize your NT password with that of
> your central (e.g. Kerberos) account at login. An IIS
> authentication filter could extend the same capability to IIS, so
> you could host authenticated websites on IIS, and rely on NTDomain
> credentials that would be sync'd with your canonical auth reference
> (e.g. AFS/Kerb). Upload of password changes (NT->AFS) can be done
> by employing Microsoft's "Services for Unix" package, which
> intercepts passwd changes initiated on NT, and forwards them (in
> cleartext) to a Unix daemon which will change the canonical auth
> device.
>
> 2) recognizes a variable in your NT account's Profile Path, and
> transforms it in such a way as to enable the Transarc AFS client to
> retrieve your roaming profile from AFS. (i.e. it recognizes the
> string "\\%Computername%" in your ProfPath, and replaces that
> variable with the actual name of the current computer, so that your
> profile path handed to Winlogon ends up resembling
> \\THISPC-afs\all\blah\blah for the current login session. Without
> making that transform, the Transarc AFSD dies a horrible death when
> asked to retrieve a file from a path containing the "%"'s. (hint
> to Transarc here :-)
>
> 3) Processes a logOUT script, to provide the missing NT
> functionality (NT by default only processes a logIN script).
>
> So, the new GINA merely facilitates the cooperation between an NT4
> Domain and AFS, but could be easily modified to synchronize NT with
> almost any other system (e.g. DCE, etc).
>
> Gone from the new GINA are all the calls to scripts and local
> generation of new user accounts at each login. We'll be relying on
> built-in NT Domain functionality for all the things that our
> original GINA (plus its scripts) had to perform. System mangement
> of the NT desktops is left to other tools (e.g. SMS, Tivoli,
> Platinum, etc.)
>
> Still want the old code?
>
Firstly, I give unstined praise for you and your product.
I think the new GINA will help us, but as soon as possible
we need authentication module to use in Web Applications
such as Active Server Pages, and Windows Applcation such as
Visual Basic, Access, etc.
Is the old GINA fit for these purpose?
If so, I want to get the old one.
If we use it, what is the requirements of AFS NT?
Should we have AFS 3.5 for windows?
Finally, when will you finish rewriting the new GINA?
Thanks in advance,
Hoon.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Kwon Oh-Hoon (�� ����)
POSTECH Computing Center Researcher
Personal E-Mail : [EMAIL PROTECTED]
Official E-Mail : [EMAIL PROTECTED], [EMAIL PROTECTED]
Homepage : http://www.postech.ac.kr/~dolphin
Telephone : +82-562-279-2568
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
