-----BEGIN PGP SIGNED MESSAGE----- While telling the press and corporate/University IS that the problem had been fixed, Microsoft was preparing sanitized articles for the Microsoft Knowledge Base acknowledging it. Now there's a fix for WFW (only), dated September 28 if you believe the mod times on the FTP server. The fact that the problem was not even acknowledged on September 28 is a bit of a scandal. I'm a little peeved. I would be slightly less peeved if Microsoft would at least put the Wolverine security bug fix for WFW in ftp://ftp.microsoft.com/bussys/Clients/WFW, and stop distributing the version they have finally acknowledged to be bad. I can only guess that that's what they're doing now, and that they were planning on a nice, friendly press release in the morning. Sorry, Bill! You'll read it here first. See also http://www.c2.org/hackmsoft/. - -rich moderator of the win95netbugs list http://www-dccs.stanford.edu/NetConsult/Win95Net/faq.html Following are the full text of: http://www.microsoft.com:80/KB/PEROPSYS/win95/Q137872.htm http://www.microsoft.com:80/KB/PEROPSYS/windows/Q136418.htm Does anybody know the dates for these files? I know they weren't in the last KB archive distribution. Windows 95 Shared Folders on TCP/IP Networks ARTICLE ID: Q137872 The information in this article applies to: - Microsoft Windows 95 SYMPTOMS When you share a folder on a Windows 95-based computer, users on UNIX- based computers running the SMBCLIENT Samba network client who connect to the shared folder may have access to the entire drive on which the shared folder is located. CAUSE This problem can occur when all of the following conditions exist: - You use the Vserver.vxd file included with Windows 95. - You use the TCP/IP network protocol. - There are UNIX-based computers on the network. RESOLUTION Use user-level access control instead of share-level access control to share the folder. To use user-level access control to share a folder, follow these steps: 1. Stop sharing the folder. 2. Use the right mouse button to click Network Neighborhood, and then click Properties on the menu that appears. 3. On the Access Control tab, click the User-Level Access Control option button. 4. In the "Obtain list of users and groups from" box, specify the network domain or computer from which the master list of users should be obtained. 5. Click OK. 6. Share the folder again. NOTE: To use user-level access control, there must be a Microsoft Windows NT or Novell NetWare server on the network that can provide the master list of users. STATUS Microsoft has confirmed this to be a problem in Microsoft Windows 95. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. KBCategory: kbnetwork kb3rdparty KBSubcategory: win95 Additional reference words: 95 THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1995. Updated Vserver.386 File for Windows for Workgroups ARTICLE ID: Q136418 The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 SYMPTOMS When you share a folder on a Windows for Workgroups 3.11-based computer, users on UNIX-based computers running the SMBCLIENT Samba network client who connect to the shared folder may have access to the entire drive on which the shared folder is located. CAUSE This problem can occur when all of the following conditions exist: - You use the Vserver.386 file included with Windows for Workgroups 3.11. - You use the TCP/IP network protocol. - There are UNIX-based computers on the network. RESOLUTION To resolve this problem in Windows for Workgroups 3.11, follow these steps: 1. Download the Wfwvsrvr.exe file from one of the online services listed below to an empty directory. 2. In File Manager, double-click the Wfwvsrvr.exe file to expand the Vserver.386 file it contains. 3. Quit Windows for Workgroups. 4. Copy the new Vserver.386 file to the Windows\System directory, overwriting the existing version of the file. 5. Restart your computer. MORE INFORMATION You can download Wfwvsrvr.exe, a self-expanding file, from the Microsoft Software Library (MSL) on the following services: - The Microsoft Network On the Edit menu, click Go To, and then click Other Location on the menu that appears. Type MSSL in the "Type a Go word for a particular service" box, and then click OK. Double-click Microsoft Windows Software Library and then Microsoft Windows 3.x And Windows For Workgroups Software Library. - CompuServe GO MSL Search for Wfwvsrvr.exe Display results and download - Microsoft Download Service (MSDL) Dial (206) 936-6735 to connect to MSDL Download Wfwvsrvr.exe - Internet (anonymous FTP) ftp ftp.microsoft.com Change to the SOFTLIB/MSLFILES directory Get Wfwvsrvr.exe To download Wfwvsrvr.exe to your computer click . KBCategory: kbnetwork kbfile KBSubcategory: wfwg msnets 3rdpartynet Additional reference words: 3.11 msnWFWmisc THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1995. - -rich moderator of the win95netbugs list http://www-dccs.stanford.edu/NetConsult/Win95Net/faq.html -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMIX21Y3DXUbM57SdAQFlowP+Mdu+N6u85xLw5lgiSfw0xBU/Oc1iTC3c tDjSd0l/8+c79Xf35PX+xgj8Px8KvDpIu3wl2ElIuTXfB8eWh4WSzyDeF98ZlAMt TnKIzBaXOHGc3vgirbEte9JHfv0ItAFLh+3gARjHnQC1q9n7nYXKK8rK7eIIxOpS 8Vy8qSOm6LE= =XrYy -----END PGP SIGNATURE-----