similar to: bugzilla.samba.org temporarily down due to server migration

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom, Try this patch. I lost your original message but this should fix the problem with 'logon path = \\%L\profile\%U\%a' confusing WinXP with Win2K. cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team

Thanks for the response, Jerry. Is there a way for me to verify this is happening? Winbindd has been running for a few days now, and I just did a netstat and the only connections to a DC are to the off-site one, the PDC. Thanks. Sven -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: Thursday, May 22, 2003 10:19 PM To: SRuth@LANDAM.com Cc:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use at your own risk. One of the main additions in this release is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use at your own risk. One of the main additions in this release is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate snapshot of the Samba 3.0.5 code base and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and in provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at your own risk. There have been several bug fixes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate snapshot of the Samba 3.0.5 code base and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and in provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at your own risk. There have been several bug fixes

>From: "Gerald (Jerry) Carter" <jerry@samba.org> >To: Leandro <llattan@uyuyuy.com> >CC: samba@lists.samba.org, jra@samba.org >Subject: write list [was Re: [Samba] BUG IN SAMBA 3.0.4: FORCE USER] >Date: Mon, 17 May 2004 12:16:38 -0500 (CDT) > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >On Mon, 17 May 2004, Leandro wrote: > > >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all. What message is 2210 in Toolbar ? I tried to take a look at commctrl.h, but I wasn't able to figure it out. I'm receiving the folliwing messages: err:toolbar:ToolbarWindowProc unknown msg 2210 wp=00000001 lp=0001002a err:toolbar:ToolbarWindowProc unknown msg 2210 wp=00000001 lp=0001002d This is the message the ToolbarWindowProc

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all. I understand the following could be considered a little off topic on this list, so please forgive me. Our company is considering to promote an european funded research project, which should use wine as one of his major components. We are looking for a research institute within european community willing to be funded for doing the research

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all I would like to share with all the wine users my appreciation for wine developers. I was able to install and run Eudora 5.1 without any problem. The only problem I encountered was in the setup, where if you choose to run the wizard instead of the advanced setup the system freezes. I'm using wine from the last CVS on a RH Linux 6.2

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all. I've a problem with printing from an application. My environment: a no windows installation based on Debian (testing). I've successfully installed a printer, and I'm able to print. However, when I print from this application, a huge (40MB) postscript file is created. Can anyone provide any suggestion? Thank you all in advance

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the second release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use it at your own risk. The source code can be downloaded from :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the second release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use it at your own risk. The source code can be downloaded from :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Preface - ------- Here are the informal plans for the actual 3.0.0 release: We, the Samba Team, hope that this will be the final RC before the real 3.0.0 release. Unless there is a severe bug in the Samba source that would affect a large number of the community, the source/ directory in RC3 will stay the same for 3.0.0. The docs/ directory

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Preface - ------- Here are the informal plans for the actual 3.0.0 release: We, the Samba Team, hope that this will be the final RC before the real 3.0.0 release. Unless there is a severe bug in the Samba source that would affect a large number of the community, the source/ directory in RC3 will stay the same for 3.0.0. The docs/ directory

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the fourth release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use it at your own risk. The main issue addressed in this release

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the fourth release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use it at your own risk. The main issue addressed in this release

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Flowers, Chocolate, a weekend at the beach, and Samba 3.0.2a. Samba 3.0.2a is a minor patch release for the 3.0.2 code base to address, in particular, a problem when using pdbedit to sanitize (--force-initialized-passwords) Samba's tdbsam backend. This is the latest stable release of Samba. This is the version that all production Samba servers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Flowers, Chocolate, a weekend at the beach, and Samba 3.0.2a. Samba 3.0.2a is a minor patch release for the 3.0.2 code base to address, in particular, a problem when using pdbedit to sanitize (--force-initialized-passwords) Samba's tdbsam backend. This is the latest stable release of Samba. This is the version that all production Samba servers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Subject: Possible Buffer Overrun in smbd CVE #: CAN-2004-0882 Affected Versions: Samba 3.0.x <= 3.0.7 Summary: A possible buffer overrun in smbd could lead to code execution by a remote user Patch Availability - ------------------ A patch for Samba 3.0.7 (samba-3.0.7-CAN-2004-0882.patch) is available from