OpenAFS was first - really Re: SP2 first incompatibility: DivX.

From: Jeffrey Altman (jaltman_at_SECURE-ENDPOINTS.COM)
Date: 08/12/04

  • Next message: John Singler: "Re: XP SP2 nmap incompatibility" 
    Date:         Thu, 12 Aug 2004 16:57:14 -0400
To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM

    Ok. If we are going to start listing incompatibilties then
    I must point out that OpenAFS.org was provided information
    on Saturday night regarding the following problem:

    * If OpenAFS for Windows version 1.3.66 is installed on a
        machine when XP SP2 is applied, the machine will not finish
        booting after the reboot.

    The cause of the problem was traced with the help of the
    Windows Security team to a new restriction on DLL initialization
    which was added to the Service Pack some time between the
    July 14th build and the final release.

    The restriction is that network operations which open an incoming
    port may no longer be performed during the PROCESS_ATTACH phase of DLL
    initialization. Doing so will cause the operation to block indefinitely.

    OpenAFS for Windows includes a WinLogon Event Handler DLL and
    Network Provider DLL which up until the 1.3.70 release on Monday
    initialized a library during the PROCESS_ATTACH. This library
    opens a incoming UDP socket for RX communications. With the new
    restriction in place this causes a deadlock situation when Winlogon.exe
    executes as the Event Handler DLL cannot finish loading and never fails.

    Although the Network Provider DLL initialized in the same fashion,
    Network Providers are executed asynchronously as a child process to
    WinLogon.exe. Hence, the functionality of the DLL will fail but it
    will not interrupt the boot process.

    All users of AFS prior to OpenAFS 1.3.70 are urged to upgrade before
    installing XP SP2. The announcement letter is copied here:

    http://lists.openafs.org/pipermail/openafs-info/2004-August/014424.html

    Jeffrey Altman
    OpenAFS for Windows Gatekeeper
    Secure Endpoints Inc.

    -----
    NTBugtraq Editor's Note:

    Want to reply to the person who sent this message? This list is configured such that just hitting reply is going to result in the message coming to the list, not to the individual who sent the message. This was done to help reduce the number of Out of Office messages posters received. So if you want to send a reply just to the poster, you'll have to copy their email address out of the message and place it in your TO: field.
    -----

  • Next message: John Singler: "Re: XP SP2 nmap incompatibility"

    Relevant Pages

    • Re: This is a follow-up to one of my posts
      ... DLL initialization is caused by the loading of the DLL. ... Whenever Windows ... loads a DLL it calls an entry point in the DLL passing a special flag ...
      (microsoft.public.windowsxp.general)
    • RE: write windows network filter!
      ... the best option seemed to be to write a "Network Provider" DLL. ... > windows platform, but I'm not sure how to intercept ...
      (Security-Basics)
    • Re: .Net packaging/wrapper application?
      ... it just didn't work well in reality due to DLL ... Windows works is to look in the executable's directory for a needed DLL ... the way apps used to work when they developed Windows. ... Looks to me like Jim is looking for the .NET equivalent of compiling ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Unnown process... 5eplorer.exe
      ... do not remove the cause (a "super"-hidden .dll program) but only remove ... symptom files and registry settings. ... It has all permissions but 'copy' denied to everyone, ... then by using the Windows XP Recovery Console. ...
      (microsoft.public.win2000.general)
    • Re: WinSxS, functional under 2k ?
      ... The newSide-by-Side Assembly technology was introduced with Windows XP to help reduce or eliminate DLL Hell. ... If you recall earlier Windows versions, like Windows 95, when you installed an application you were warned if the installer tried to replace a DLL from the system folder with an older version and you were asked if you wanted to accept the change. ... Until Windows XP it wasn't so easy to use different versions of shared system DLLs, that is what the new Side-by-Side assemblies attempts to resolve. ...
      (microsoft.public.win2000.general)