similar to: List problems now resolved

Hello List, In regards to RPM packages, what is the difference in the prebuilt ones for example the FC5 RPM's directly from samba.org or obtaining the latest .tar.gz and running ./makerpms.sh for the desired distribution. Does this way optimize for example - x86-64 or SMP ? Cheers, Adrian Sender. -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, We are discussing removing the capability to chaining passdb backends. It's a decent idea but overly complicates things IMO and unless it has wide spread use, we'll probably axe it soon (voting is starting up on the samba-tecnnical ml now). To give you an example of what I mean, is anyone using something like: passdb backend =

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, Just a heads up for everyone. We are aware of the problem and are continuing to work on resolving it. cheers, jerry ===================================================================== Samba ------- http://www.samba.org Centeris ----------- http://www.centeris.com "What man

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I'm looking to remove some more old code. Does anyone use either of these features currently? cheers, jerry ===================================================================== I live in a Reply-to-All world ----------------------- Samba ------- http://www.samba.org Centeris

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, We've brought a new wiki online at http://wiki.samba.org/ for Samba users and developers alike. The intent is to allow the community to fill the gap in dynamic or temporary documentation and other relevant information. Our thanks to Craig White who has volunteered to act as standing editor (at least at first). But in general, the wiki

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Warren Beldad wrote: > I have created a user with a password of 15 characters... > then disable: > -bash-3.00# smbpasswd -d user1 > Disabled user user1. > > Enable: > -bash-3.00# smbpasswd -e user1 > New SMB password: > > Why is this happening? Is there any limitation for > the number of password characters? >

CentOS4 RPMS for x86-64 would be awesome. --------------------------------------------------------------------------- Tony Hoover, Network Administrator KSU - Salina, College of Technology and Aviation (785) 826-2660 "Don't Blend in..." ---------------------------------------------------------------------------- -----Original Message----- From:

I just found out that when doing a new installation in works. But as soon as I change the netbios name in the smb.conf the trouble begins... Everything can connect, but then suddenly the error does appear. Does Samba cache it's initial netbios name somewhere? -----Oorspronkelijk bericht----- Van: Sander van Harmelen Verzonden: dinsdag 14 november 2006 13:59 Aan: Sander van Harmelen;

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Volker, Assume I have a member server named LINUX joined to a domain name AD. Now assume I have a local user named foo in my passdb and a user named foo in the domain as well. I'm modifying winbindd_util.c:parse_domain_user() to do a lookup_name() to try to figure out which domain to prepend to the username rather than just assuming its a domain

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Some people might find this discussion about upcoming changes in 3.0.22 interesting. It might also be helpful to get some feedback from the field on the ramifications of the changes. cheers, jerry ===================================================================== I live in a Reply-to-All world ----------------------- Samba

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here's a short list of parameters I'd like to remove from smb.conf. hosts equiv read bmpx wins partners ldap server ldap port homedir map nis homedir magic script magic output Comments? jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm watching the logs, and Samba is trying the following combinations for _Get_Pwnam() with the name UserName in the domain DOMAIN: domain+username DOMAIN+UserName DOMAIN+USERNAME and then it trys: username UserName USERNAME however, all 6 fail because what getent passwd shows is DOMAIN+username. Is there a configuration change that can fix

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Memory exhaustion DoS against smbd == CVE ID#: CAN-2006-1059 == == Versions: Samba Samba 3.0.1 - 3.0.22 (inclusive) == == Summary: smbd may allow internal structures == maintaining state for share connections == to grow unbounded. ==

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Memory exhaustion DoS against smbd == CVE ID#: CAN-2006-1059 == == Versions: Samba Samba 3.0.1 - 3.0.22 (inclusive) == == Summary: smbd may allow internal structures == maintaining state for share connections == to grow unbounded. ==

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a note: You might see a flood of bug report emails. I've fixed a problem with the MTA on bugzilla.samba.org. cheers, jerry ===================================================================== Samba ------- http://www.samba.org Centeris ----------- http://www.centeris.com

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, The migration is done and the new git repos are online. You can browse the repositories as well as find links to the documentation in the Samba wiki at http://gitweb.samba.org/ A few things, such as buildfarm integration, are still underway and will be completed in a few days. cheers, jerry - --

Hi All, Yesterday, I've upgraded my Samba server from 3.021c to 3.023 through yum upgrade samba*. I'm running Fedora Core 4 Kernel 2.6.17-1.2142 on this server. After upgrade has been completed, I lost the attributes of ownership and groups. I noticed that the uids/gids have changed for all AD accounts. This means that users can't have total access for their files and no access

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (CC'ing back on list) Gianluca Culot wrote: > When the users change their passwords on the AD domain server > it takes one hour before winbind starts refusing the old > password (as it is in cache, I suppose) Nope. This is a Windows DC bug. https://bugzilla.samba.org/show_bug.cgi?id=2874 Unless you have enabled "winbind

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've posted an updated version of my 3.0.24-gc dev branch to deal with the break in "force group" caused by the CVE-2007-2444 patch and backported the Vista related bug fixes from the Samba patches page. The bzr branch is hosted at http://people.samba.org/bzr/jerry/samba-3-0-24-gc.bzr/ The source tarball is available from

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fabio Muzzi wrote: > Hello drweb, > > Saturday, November 25, 2006, 4:32:17 PM, you wrote: > > > d> By command: > d> pdbedit -r gad -G 514 -d0 > d> I cann't change primary group. > > > I was looking through the list archives and found your post. I have > the same issue. Any solutions yet? >