X-Spam-Check-By: sourceware.org Message-ID: <46BCA278.2000706@cox.net> Date: Fri, 10 Aug 2007 12:38:00 -0500 From: Jeff Bromberger User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: LSA Authentication Packages Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hello Corinna, I found a post you made in late 2006 about the authentication package you created. I have created a very simple "dummy" auth package to do some testing (for my own project, this is unrelated to cygwin). I install it by listing it after msv1_0 in the registry. One thing that is confusing is that LSA calls my LsaApLogonTerminate function a couple of times right at the end of boot up, even though I have never received a call to LsaApLogonUser. I get a call to LsaApInitializePackage and return success. Then a few seconds later I get called into LsaApLogonTerminate. My first platform to test on was server 2003 x64. I received these terminate calls on that platform, but it didn't seem to cause any problems there. But now I am trying it on server 2003 32-bit and LSA causes an exception immediately after calling my LsaApLogonTerminate Function. My function does nothing, just like yours, so I was curious if you ever ran into this problem or had any idea why it might be happening. Thank you for your time! Jeff -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/