[Samba] Strange behaviour of winbind on solaris 8
Dear All, I came across a really strange behaviour when using winbind on solaris 8. Normally nscd should be turned off because it's causing problems in the username resolution etc. When I turn it off I can login e.g. using ssh as an AD users but when i start a command like ls it gets put in the background immediately? When nscd is turn on and login again I can issue commands with no problems, but doing an ls -alrt on a directory gets stuck if a file is owned by user that is not a AD user. my /etc/nsswitch.conf # # /etc/nsswitch.dns: # # An example file that could be copied over to /etc/nsswitch.conf; it uses # DNS for hosts lookups, otherwise it does not use any other naming service. # # hosts: and services: in this file are used only if the # /etc/netconfig file has a - for nametoaddr_libs of inet transports. passwd: files [NOTFOUND=CONTINUE] winbind [NOTFOUND=return] group: files [NOTFOUND=CONTINUE] winbind [NOTFOUND=return] # You must also set up the /etc/resolv.conf file for DNS name # server lookup. See resolv.conf(4). hosts: files dns ipnodes:files # Uncomment the following line and comment out the above to resolve # both IPv4 and IPv6 addresses from the ipnodes databases. Note that # IPv4 addresses are searched in all of the ipnodes databases before # searching the hosts databases. Before turning this option on, consult # the Network Administration Guide for more details on using IPv6. #ipnodes: files dns networks: files protocols: files rpc:files ethers: files netmasks: files bootparams: files publickey: files # At present there isn't a 'files' backend for netgroup; the system will # figure it out pretty quickly, and won't use netgroups at all. netgroup: files automount: files aliases:files services: files sendmailvars: files printers: user files auth_attr: files prof_attr: files project:files -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Strange behaviour of winbind on solaris 8
Oliver Weinmann wrote: Dear All, I came across a really strange behaviour when using winbind on solaris 8. Normally nscd should be turned off because it's causing problems in the username resolution etc. When I turn it off I can login e.g. using ssh as an AD users but when i start a command like ls it gets put in the background immediately? When nscd is turn on and login again I can issue commands with no problems, but doing an ls -alrt on a directory gets stuck if a file is owned by user that is not a AD user. my /etc/nsswitch.conf # # /etc/nsswitch.dns: # # An example file that could be copied over to /etc/nsswitch.conf; it uses # DNS for hosts lookups, otherwise it does not use any other naming service. # # hosts: and services: in this file are used only if the # /etc/netconfig file has a - for nametoaddr_libs of inet transports. passwd: files [NOTFOUND=CONTINUE] winbind [NOTFOUND=return] group: files [NOTFOUND=CONTINUE] winbind [NOTFOUND=return] # You must also set up the /etc/resolv.conf file for DNS name # server lookup. See resolv.conf(4). hosts: files dns ipnodes:files # Uncomment the following line and comment out the above to resolve # both IPv4 and IPv6 addresses from the ipnodes databases. Note that # IPv4 addresses are searched in all of the ipnodes databases before # searching the hosts databases. Before turning this option on, consult # the Network Administration Guide for more details on using IPv6. #ipnodes: files dns networks: files protocols: files rpc:files ethers: files netmasks: files bootparams: files publickey: files # At present there isn't a 'files' backend for netgroup; the system will # figure it out pretty quickly, and won't use netgroups at all. netgroup: files automount: files aliases:files services: files sendmailvars: files printers: user files auth_attr: files prof_attr: files project:files Can you get the ls to work with numeric uids? And, I noticed that you don't have any entries for shadow... you're not using shadow passwords, right? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Strange behaviour of winbind on solaris 8
forgot to mention that the nss_winbind links are there: bash-2.03# ls -alrt /usr/lib/nss_w* lrwxrwxrwx 1 root other 28 Apr 23 14:30 /usr/lib/nss_winbind.so.2 - /usr/lib/libnss_winbind.so.1 lrwxrwxrwx 1 root other 28 Apr 23 14:30 /usr/lib/nss_winbind.so.1 - /usr/lib/libnss_winbind.so.1 lrwxrwxrwx 1 root other 28 Apr 23 14:30 /usr/lib/nss_winbind.so - /usr/lib/libnss_winbind.so.1 Changed the crle to only /usr/lib:/opt/csw/lib and disabled nscd at boot. After reboot i can no longer resolve usernames, wbinfo -t/-g/-u work fine. getent passwd and getent group are not showing AD users. when logging in as an AD users i can see the following in the /var/adm/messages logfile: Apr 28 13:20:09 rose8 sshd[516]: [ID 129890 auth.error] pam_winbind(sshd): request failed: No such user, PAM error was No account present for user (13), NT error was NT_STATUS_NO_SUCH_USER Apr 28 13:20:18 rose8 sshd[524]: [ID 800047 auth.error] error: PAM: No account present for user for illegal user oweinmann from vb8860.vegagroup.net On 4/28/08, Oliver Weinmann [EMAIL PROTECTED] wrote: I got: bash-2.03# ls -alrt /usr/lib/libnss_winbind.so* -rwxr-xr-x 1 root bin74744 Apr 21 14:45 /usr/lib/libnss_winbind.so.1 lrwxrwxrwx 1 root other 28 Apr 23 14:30 /usr/lib/libnss_winbind.so.2 - /usr/lib/libnss_winbind.so.1 lrwxrwxrwx 1 root other 28 Apr 23 14:30 /usr/lib/libnss_winbind.so - /usr/lib/libnss_winbind.so.1 so that's fine. i didn't have crle setup correctly since i have build against libraries from blastwave and they reside under /opt/csw/lib so i did: bash-2.03# crle -u -l /usr/lib:/usr/local/lib:/opt/csw/lib bash-2.03# crle Configuration file [version 4]: /var/ld/ld.config Default Library Path (ELF): /usr/lib:/usr/local/lib:/opt/csw/lib Trusted Directories (ELF):/usr/lib/secure (system default) Command line: crle -c /var/ld/ld.config -l /usr/lib:/usr/local/lib:/opt/csw/lib and I did change my nsswitch.conf to reflect the shadow entry. Still not working without nscd. :( I had no problems under Linux at all but under Solaris I'm lost. On 4/28/08, Scott Lovenberg [EMAIL PROTECTED] wrote: Oliver Weinmann wrote: On 4/28/08, Scott Lovenberg [EMAIL PROTECTED] wrote: Oliver Weinmann wrote: Dear All, I came across a really strange behaviour when using winbind on solaris 8. Normally nscd should be turned off because it's causing problems in the username resolution etc. When I turn it off I can login e.g. using ssh as an AD users but when i start a command like ls it gets put in the background immediately? When nscd is turn on and login again I can issue commands with no problems, but doing an ls -alrt on a directory gets stuck if a file is owned by user that is not a AD user. my /etc/nsswitch.conf # # /etc/nsswitch.dns: # # An example file that could be copied over to /etc/nsswitch.conf; it uses # DNS for hosts lookups, otherwise it does not use any other naming service. # # hosts: and services: in this file are used only if the # /etc/netconfig file has a - for nametoaddr_libs of inet transports. passwd: files [NOTFOUND=CONTINUE] winbind [NOTFOUND=return] group: files [NOTFOUND=CONTINUE] winbind [NOTFOUND=return] # You must also set up the /etc/resolv.conf file for DNS name # server lookup. See resolv.conf(4). hosts: files dns ipnodes:files # Uncomment the following line and comment out the above to resolve # both IPv4 and IPv6 addresses from the ipnodes databases. Note that # IPv4 addresses are searched in all of the ipnodes databases before # searching the hosts databases. Before turning this option on, consult # the Network Administration Guide for more details on using IPv6. #ipnodes: files dns networks: files protocols: files rpc:files ethers: files netmasks: files bootparams: files publickey: files # At present there isn't a 'files' backend for netgroup; the system will # figure it out pretty quickly, and won't use netgroups at all. netgroup: files automount: files aliases:files services: files sendmailvars: files printers: user files auth_attr: files prof_attr: files project:files Can you get the ls to work with numeric uids? And, I noticed that you don't have any entries for shadow... you're not using shadow passwords, right? I have no entry in nsswitch.conf for shadow. I'm mainly using AD users so I didn't add an entry for shadow pw's. I turned off nscd now and logged in as an AD user. The problem is not only when running ls. It happens on many commands: e.g. bash-2.03$ ls -alrt [1]+ Stopped ls
[Samba] Samba 3.2.0-pre3 packages in Debian - version of Samba in Debian lenny
The day after Karolin announced the release of 3.2.0-pre3, the Debian packaging team was able to upload .deb packages for it in Debian *experimental*. To use them, you need to already use Debian testing or unstable, then add this to /etc/apt/sources.list: deb http://ftp.fr.debian.org/debian experimental main contrib non-free (replace fr by your favorite mirror country code) If you do so, it is recommended to add: APT::Default-Release unstable; to /etc/apt/preferences... (replace with testing if you're using testing) You can then install the 3.2.0 packages with: apt-get install -t experimental samba PS: these packages should be usable for Ubuntu Hardy users (untested, though). You might want to replace unstable by hardy in /etc/apt/preferences, then. News about Samba in Debian lenny Debian lenny is due out for September 2008. From the news we currently have, it seems wiser to stick with 3.0.28a rather than a quite disruptive and uncertain 3.2.0 This is currently the plan of the packaging team for Samba in Debian (and Ubuntu). We will do our best to offer 3.2.0 packages for lenny on the backports.org server. Ubuntu Hardy will have 3.0.28a and the same is likely to be true for hardy+1 (8.10 or so). -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Maxtor NAS share problem
Rick Johnson wrote: Toby Bluhm wrote: Rick Johnson wrote: Adam Williams wrote: what are the settings on the share you're trying to mount? does it have something like valid users = rickj Well, that is hard to determine. If you're asking whether the drive has something like an smb.conf file containing share settings the answer is no. The only access I have to the Maxtor drive is via a browser interface. I have used the menu in that to set all files for full public access, but beyond that I have no finer control. (I have So in public mode, it's probably going to throw all user info away and map everything to a universal id. Have you looked closely at the file perm/ownership from the Windows client? Saved files as joe user then jane user - does it keep the distinction? I'll venture no. There is no Windows client. The Maxtor shows up in My Netowrk Places and is mapped as just another drive from Windows; in my particular case, as the Z drive. I meant client = the Windows PC. If it's possible, have you tried setting up individual users through the nas interface? Yes. The drive has been set up with different users since the beginning. Could also just work with the fact that no perm/owner info will be kept. Collect that info store it to a file. A recursive getfacl to collect setfacl to restore could do the trick. Judging by what I see through the web interface, there must be SOME type of user info stored, but how or where I don't know and can't see. I was talking about saving the Linux filesystem info. Do your rsync to the NAS, then do a recursive getfacl, redirecting the output to a file on the NAS. When you do an rsync back from the NAS, correct the owner/perms with setfacl. Better yet, look into dar - http://dar.linux.free.fr - a tar like backup designed for saving to files on disk. It shouldn't care (much) about the filesystem it's stored on. found via www.openmss.org that the underlying filesystem of the drive is Linux - reiser I think - but beyond that I have no data on the filesystem other than what I see when I smbmount the drive.) Perhaps there's a way to break into the Linux the nas is running change stuff to your suiting. I think this is a possibility and I've been looking for more info; unfortunately without success so far. I've heard many times of people with an appliance trying to do something beyond its intended function hitting a brick wall. Your situation is why I never recommend an appliance to anyone other than a pure, non-hacker, non-power type Windows user. A NAS type distro or even a full distro on a junker PC would be a better solution. More work, but better results. You're probably right. But since I've already got the drive I need to figure out a way to use it. Rick J. -- Toby Bluhm Alltech Medical Systems America, Inc. 30825 Aurora Road Suite 100 Solon Ohio 44139 440-424-2240 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.2.0-pre3 packages in Debian - version of Samba in Debian lenny
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Perrier wrote: | News about Samba in Debian lenny | | | Debian lenny is due out for September 2008. From the news we currently | have, it seems wiser to stick with 3.0.28a rather than a quite | disruptive and uncertain 3.2.0 This is currently the plan of the | packaging team for Samba in Debian (and Ubuntu). | | We will do our best to offer 3.2.0 packages for lenny on the | backports.org server. | | Ubuntu Hardy will have 3.0.28a and the same is likely to be true for | hardy+1 (8.10 or so). Christian, I really disagree here. What made you com to the decision that 3.0 is batter for a September Debian release? cheers, jerry - -- = Samba--- http://www.samba.org Likewise Software - http://www.likewisesoftware.com What man is a man who does not make the world better? --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIFcitIR7qMdg1EfYRAvlTAKDWSdlaV+BP4wkmuUDOHWo0Fi/HmQCfQFYN QJi6qea/vcUyCOkmz02+2Ko= =pia0 -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Strange behaviour of winbind on solaris 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oliver Weinmann wrote: | forgot to mention that the nss_winbind links are there: | | bash-2.03# ls -alrt /usr/lib/nss_w* | lrwxrwxrwx 1 root other 28 Apr 23 14:30 | /usr/lib/nss_winbind.so.2 - /usr/lib/libnss_winbind.so.1 | lrwxrwxrwx 1 root other 28 Apr 23 14:30 | /usr/lib/nss_winbind.so.1 - /usr/lib/libnss_winbind.so.1 | lrwxrwxrwx 1 root other 28 Apr 23 14:30 | /usr/lib/nss_winbind.so - /usr/lib/libnss_winbind.so.1 Check the perms on /usr/lib/libnss_winbind.so.1. Sounds like it might be rwx for root only. cheers, jerry - -- = Samba--- http://www.samba.org Likewise Software - http://www.likewisesoftware.com What man is a man who does not make the world better? --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIFcnJIR7qMdg1EfYRAp+uAKCoT5s9gRV+x0M+PUrFnYWVRtqmcwCg293J 0OxWwTr/wJPDW67YmZCAfQo= =6S2v -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Strange behaviour of winbind on solaris 8
Just for fun i changed the perms of /usr/lib/libnss_winbind.so to 777 bash-2.03# chmod 777 /usr/lib/libnss_winbind.so bash-2.03# ls -alrt /usr/lib/libnss_winbind.so -rwxrwxrwx 1 root other 74744 Apr 28 13:32 /usr/lib/libnss_winbind.so nscd is turned off. I can login as an AD users but I cant start any command. :( login as: oweinmann Using keyboard-interactive authentication. Password: Last login: Mon Apr 28 15:17:11 2008 from vb8860.vegagrou bash-2.03$ ls -alrt [1]+ Stopped ls -alrt bash-2.03$ id [2]+ Stopped id bash-2.03$ group [3]+ Stopped group bash-2.03$ echo TEST TEST bash-2.03$ Some commands are working and some others are put in background and the session closes after one or two minutes? When I turn on nscd everything is fine, except ls -alrt not working. On 4/28/08, Gerald (Jerry) Carter [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oliver Weinmann wrote: | forgot to mention that the nss_winbind links are there: | | bash-2.03# ls -alrt /usr/lib/nss_w* | lrwxrwxrwx 1 root other 28 Apr 23 14:30 | /usr/lib/nss_winbind.so.2 - /usr/lib/libnss_winbind.so.1 | lrwxrwxrwx 1 root other 28 Apr 23 14:30 | /usr/lib/nss_winbind.so.1 - /usr/lib/libnss_winbind.so.1 | lrwxrwxrwx 1 root other 28 Apr 23 14:30 | /usr/lib/nss_winbind.so - /usr/lib/libnss_winbind.so.1 Check the perms on /usr/lib/libnss_winbind.so.1. Sounds like it might be rwx for root only. cheers, jerry - -- = Samba--- http://www.samba.org Likewise Software - http://www.likewisesoftware.com What man is a man who does not make the world better? --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIFcnJIR7qMdg1EfYRAp+uAKCoT5s9gRV+x0M+PUrFnYWVRtqmcwCg293J 0OxWwTr/wJPDW67YmZCAfQo= =6S2v -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Samba 3.2.0-pre3 packages in Debian - version of Samba in Debian lenny
On Mon, Apr 28, 2008 at 01:54:26PM +0200, Christian Perrier wrote: Debian lenny is due out for September 2008. From the news we currently have, it seems wiser to stick with 3.0.28a rather than a quite 3.0.28a has known bugs in particular with trusts, so you will inevitably have to backport stuff from 3.0.28b that will be done by then. And, I have to agree with Jerry, having to live with .28a for the next decade in Debian might be not the best thing. Volker pgpEDAYdZe4ms.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Planning to start a new server
Hi, I have a samba server which act as file/print/wins server and PDC with ldap backend ACL support (samba-3.0.23). I plan to start a new server which replace the old one. My question is about the samba version, my first advice is the use samba-3.0.28a. But maybe is preferable to wait samba 3.2.0. What type of bugs samba-3.0.28a have ? The new sever will act as samba/print server and PDC with ldap backend ACL support . wins server will be on other servers (samba4wins) thanks Stéphane Purnelle --- Stéphane PURNELLE [EMAIL PROTECTED] Service Informatique Corman S.A. Tel : 00 32 087/342467 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Planning to start a new server
hi, El Mon, 28 Apr 2008 15:34:26 +0200 [EMAIL PROTECTED] ha escrit: Hi, I have a samba server which act as file/print/wins server and PDC with ldap backend ACL support (samba-3.0.23). I plan to start a new server which replace the old one. My question is about the samba version, my first advice is the use samba-3.0.28a. But maybe is preferable to wait samba 3.2.0. What type of bugs samba-3.0.28a have ? i'm using 3.0.24 on SLES 10 because the following ACL-related problems on 3.0.28 http://www.nabble.com/ACL-strange-behaviour-td16495631.html good luck! toni The new sever will act as samba/print server and PDC with ldap backend ACL support . wins server will be on other servers (samba4wins) thanks Stéphane Purnelle --- Stéphane PURNELLE [EMAIL PROTECTED] Service Informatique Corman S.A. Tel : 00 32 087/342467 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Planning to start a new server
have you tried (if possible) samba-3.0.28a ? I can read in change log : Fix ACL set bug when group being set is the primary group. I don't use the windows ACL management, I have a modified webmin file manager for manage ACL. thanks Stéphane --- Stéphane PURNELLE [EMAIL PROTECTED] Service Informatique Corman S.A. Tel : 00 32 087/342467 [EMAIL PROTECTED] a écrit sur 28/04/2008 16:15:16 : hi, El Mon, 28 Apr 2008 15:34:26 +0200 [EMAIL PROTECTED] ha escrit: Hi, I have a samba server which act as file/print/wins server and PDC with ldap backend ACL support (samba-3.0.23). I plan to start a new server which replace the old one. My question is about the samba version, my first advice is the use samba-3.0.28a. But maybe is preferable to wait samba 3.2.0. What type of bugs samba-3.0.28a have ? i'm using 3.0.24 on SLES 10 because the following ACL-related problems on 3.0.28 http://www.nabble.com/ACL-strange-behaviour-td16495631.html good luck! toni The new sever will act as samba/print server and PDC with ldap backend ACL support . wins server will be on other servers (samba4wins) thanks Stéphane Purnelle --- Stéphane PURNELLE [EMAIL PROTECTED] Service Informatique Corman S.A. Tel : 00 32 087/342467 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Monday, April 28 - Samba Mashup Report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ** Samba Mashup Report (SMR) for Monday April 28, 2008 ** Table of Contents: 0. Greetings to the Inaugural SMR (samba Mashup Report) 1. Plans in Motion for 6 Month Samba 3.x Release Cycles 2. Samba 3.2.0pre3 Released 3. Samba XP 2008 Concludes as YASC (yet another successful conference) 4. Samba Documentation repository moved from SVN to Git 5. Bugzilla Day for Samba 3.2 scheduled for Friday, May 9. 6. Call for developer reports === 0. Greetings to the Inaugural SMR (samba Mashup Report) === Several of Samba team members agreed during discussions held at Samba XP (see article #3) that periodic thread summaries from the recent development activities would be helpful for keeping the community and Samba OEM vendors up to date. So using editorial privilege, I've decided to term these as mashup reports. According to the pop culture definition from Wikipedia, mashup usually means: * A web application that combines data and/or functionality from more than one source * A musical genre of songs that consist entirely of parts of other songs * A video that is edited from more than one source to appear as one * In parts of the UK means a mash or pot of tea (colloq. Yorkshire), other areas brew or stand tea The second and third definitions are probably the most appropriate here. So without further ado, here's the inaugural bi-weekly (give or take a few days) report. cheers, jerry 1. Plans in Motion for 6 Month Release Cycle Based on feedback from the community, Samba Team members have agreed to put into place a six month release cycle on new Samba 3.x releases. The initial 3.2 release will start the clock on the next major development effort. In the thread beginning at [1], Jerry Carter (Samba Team member) proposed: Once a new release cycle is done, that version goes straight to bug fix mode and the next release cycle gets a new minor release number. So for example, assume 3.2.0 is released in the next 30 days. The 3.2 releases are immediately in maintenance mode meaning we can fix all the regressions and bugs we like. But no new features. The next 6 month cycle clock starts ticking and that becomes v3.3. Karolin (Seeger) will have the job of setting dates and we have to stick to them. Christian Perrier (a Debian samba package maintainer) pointed out this would be a lot of work and maybe not achievable. Jim McDonough (Samba Team member) highlighted Jerry's main point which is: ...it will definitely require a mind shift from the Wait, we have to have _my_ major piece mode that currently dominates scheduling of releases. The developer who writes the code has to decide if the code will be ready for the schedule, rather than delaying the schedule (and everyone's code) until the code is ready. === 2. Samba 3.2.0pre3 Released === The third Preview release of Samba 3.2.0 was released on Friday, April 25 [2]. This is the last scheduled preview release with an estimated date for RC1 set by Karolin Seeger (Samba 3.2 release manager) of May 23 [3]. The number and frequency of release candidates will be decided by the quality and feedback from the community testers of the pre3 release. And in preparation for committing to a 6 month release cycle, the Samba 3.3 development branch has been created to stem the rate of change in the 3.2 code [4][5]. Samba 3.3 is tentatively scheduled for delivery sometime in December, 2008. === 3. Samba XP 2008 Concludes as YASC (yet another successful conference) === The seventh annual Samba eXPerience Conference concluded in Goettingen, DE, on April 18th [6]. Talks were presented about topics such as: * Samba's relationship with the Protocol Freedom Information Foundation (PFIF) * SMB2 protocol details * The latest developments in projects such as the Linux CIFS file system, OpenChange, and of course Samba itself. This year marked a milestone as bother members of the Samba Team, Microsoft engineers, and developers from numerous companies openly presented and discussed details of CIFS and related protocol based upon newly available WSPP documentation. Conference pictures are available on-line now. The audio portion of talks as well as session slides will be available soon from the conference web site. === 4. Samba Documentation repository moved from SVN to Git === The Docbook/XML source of the Samba HOWTOs and man pages is no longer
[Samba] Re: interdomain trust between two samba pdc's
So is no one here doing interdomain trusts using two Samba PDC's on two different subnets? I have been struggling with this problem for a long time now, and would like some help with it. Thanks! On Fri, Apr 25, 2008 at 2:54 PM, SoUnD WrEcK [EMAIL PROTECTED] wrote: I have been trying off and on for some time now to get an interdomain trust relationship going between two samba pdc machines (DomainA=trusted DomainB=trusting). Both pdc's are running on Solaris boxes and NIS is involved (I doubt there is a NIS complication just because I can use accounts on DomainA on DomainB's samba, as long as I add them using smbpasswd manually). The situation is this. DomainA hosts most user accounts for my two networks. Therefore DomainA should be trusted and DomainB should be trusting. The documentation is confusing and does not describe this exact scenario (talks about samba with microsoft pdc's). I have tried every combination I can think of, but things still aren't working as they should. I have added an account for DomainB on DomainA. I then type smbpasswd -a -i DomainB, still working on DomainA. This seems to go through okay. However, when I type net rpc trustdom list on DomainA, I get the following: Trusted domains list: none Trusting domains list: Unable to find a suitable server domain controller is not responding DomainB I expect what I see for trusted, but for trusting, should I really be seeing those errors? What do they mean? Is the fact that DomainB is listed mean that it worked and I should ignore the errors? I guess I'll stop here and make sure there is not a problem with this step before I post further information about this process. Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] winbind v3.0.26a w. nss info = sfu; wbinfo fine, getent not
wbinfo can turn names into sids, sids into names, and sids into uids. However, getent passwd only finds users in the local /etc/passwd file. Same for getent group. /etc/nsswitch.conf says this: passwd: files winbind group: files winbind shadow: compat I strace'd the getent command. It said it couldn't find /lib/libnss_winbind.so.2, so I made that a symlink to /usr/local/samba/lib/nss_info/sfu.so. After that, the strace output showed it finding and reading the file. However, the command ended abruptly shortly after that, and I can't tell why. The samba logs don't seem to show anything at all on behalf of the getent command. Any ideas? Thanks winbind was compiled like so: ./configure --with-ads --with-krb5 --with-pam --with-winbind --enable-rfc2307bis --enable-schema-mapping --with-shared-modules=idmap_ad,idmap_rid,rfc2307 smb.conf like so: security = ADS workgroup = MYDOMAIN realm = mydomain.tld idmap domains = MYDOMAIN idmap config MYDOMAIN:backend = ad idmap config MYDOMAIN:default = yes idmap config MYDOMAIN:schema_mode = sfu idmap config MYDOMAIN:range= 500-45000 idmap alloc backend = tdb idmap alloc config:range = 45001-6 winbind cache time = 0 winbind enum groups = yes winbind enum users = yes winbind nested groups = yes winbind nss info = sfu winbind separator = + winbind use default domain = yes -- Jon Detert IT Systems Administrator, Milwaukee School of Engineering 1025 N. Broadway, Milwaukee, Wisconsin 53202, U.S.A. -- Bad beer is like bad art. If you endure enough of it, eventually you forget the alternatives. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbfs / cifs mount error - password too long
Hi all, when trying to mount a windows file share using the commands below, mount exits immediately with message password too long before even attempting the mount: mount -t smbfs -o username=a user,password=12345678901234567 //server/share /mnt/target mount -t cifs -o user=a user,password=12345678901234567,sec=ntlmv2 //server/share /mnt/target But the commands below works (with a 16 characters password): mount -t smbfs -o username=a user,password=1234567890123456 //server/share /mnt/target mount -t cifs -o user=a user,password=1234567890123456,sec=ntlmv2 //server/share /mnt/target It also works if I omit the password option and type it in when prompted (though this is not a good option as I do multiple mounts in a script). Is it something I have done wrong or is this a problem with the new version? (Note: This problem started after I upgraded to Xubuntu 8.04 which uses smbfs 3.0.28a, however, it was fine in Xubuntu 7.10 (3.0.26a? - can't remember the exact version...) ) Thanks! Kok-Yan End of message -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA with NetApp filer
I'm newbies in SAMBA and NetApp filer , I use Filer with OpenLDAP as an authentication and authorization server , but look like NetApp doesn't work properly ( can't authentication ) , NetApp engineer suggest me that NetApp work properly with pure ActiveDirectory Environment. not SAMBA + OpenLDAP backend like me have. so I solve this problem by make Samba as native PDC and use OpenLDAP as database backend. So authentication are complete but next problem is home directory are not automatic create. then i try to solve this by mount NetApp CIFS share as '\homedir' and use mount.cifs to mount as local dir but not work too. even if i can mount CIFS on Filer but owner and permission after mount not work properly every file that i create on Filer are permission 777 and owner is who mount file system . but In correct way i want 'owner is who pass authentication and access only by owner ' So if i authenticate through Filer permission is ok. ( but must change permission by hand ) 1. It's possible that I use remote storage ( Filer ) as Samba local file ? 2. If it can , How do i ? everything on above is ok and correct if i use samba on local filesystem mount.cifs 192.168.1.2\\homedir /var/samba/cifs2 -o username=smb-perm,gid=513(domain users ) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Problem with PDC functionality after client upgrade
Hello, New_server - Ubuntu 6.06.2 LTS (recently updated from Breezy) w/Samba 3.0.22-lubuntu3.6 Old_server - RedHat 8 w/Samba 2.2.5-10 - yes, I know this is old - usually when something works I try not to mess with it. The RedHat server is functioning as the PDC for this network. Prior to upgrading the New_server everything was working fine - shares on New_server were accessible just as they should be. After upgrading New_server, there now there appears to be a problem with domain validation of users/passwords on this computer. When trying to connect to a share on New_server from a Windows box, I get the following error: C:\Documents and Settings\user\Desktopnet use n: \\New_server\share System error 58 has occurred. The specified server cannot perform the requested operation. I erased the machine account from Old_server and re-added it, then tried net join: [EMAIL PROTECTED]:/scripts# net join root's password: [2008/04/28 08:31:12, 0] utils/net_ads.c:ads_startup(191) ads_connect: Transport endpoint is not connected Joined domain LAN. [EMAIL PROTECTED]:/scripts# It appears the network has been joined but I'm still not able to validate users/passwords via the PDC, and I don't understand the apparent error that has been generated here. Also when running testparm on New_server I get the following message: Loaded services file OK. WARNING: passdb expand explicit = yes is deprecated Server role: ROLE_DOMAIN_MEMBER but I do not have the parameter passdb expand explicit defined in smb.conf. Here is the [global] section: [global] netbios name=New_server server string=Backup Server workgroup = LAN encrypt passwords = true security=domain password server=* passdb backend=tdbsam hosts allow=192.168.254. guest account=guest map to guest = Bad Password And here is the [global] section on Old_server: [global] netbios name=Old_server server string=PDC File Server workgroup=dandb encrypt passwords=yes ## SUPPORT FOR WINS DOMAIN LOGONS ## wins support=yes domain master=yes local master=yes preferred master=yes os level=255 security=user domain logons=yes logon script=%U.bat domain admin group=root user administrator ## ## END WINS/DOMAIN SECTION Any assistance would be greatly appreciated. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: samba Digest, Vol 64, Issue 25
On 4/28/2008, Narendra KA ([EMAIL PROTECTED]) wrote: There are usually some registry changes required for an XP to connect to a Samba server. I use this: Windows Registry Editor Version 5.00 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters requiresignorseal = REG_DWORD 0x signsecurechannel = REG_DWORD 0x Actually, these haven't been required for quite some time... -- Best regards, Charles -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Monday, April 28 - Samba Mashup Report
On 4/28/2008 11:50 AM, Gerald (Jerry) Carter wrote:
** Samba Mashup Report (SMR) for Monday April 28, 2008 **
snip
Hi Gerry,
I've been biding my time, hoping to hear something from you guys about
this before posting, but I'm tired of waiting... ;)
I'm dying to hear feedback from the developers as to first impressions
of the documentation that you guys were able to secure from Microsoft of
its core protocols, and how you see this affecting future development of
Samba.
Specifically - I would imagine that it will/could dramatically speed up
the development process, and at the same time allow for the quick fixing
of problem areas where there has had to have been a lot of 'guessing'
('reverse engineering')...
--
Best regards,
Charles
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Maxtor NAS share problem
Scott Lovenberg wrote: I have tried telnet and ssh directly, but I haven't scanned for open ports. How do I do that? Rick J. Use NMap with NMapFE (nmap frontend) on Linux, or something like YAPS (yet another port scanner) on Windows. Any crappy port scanner will do, you don't need anything like stealth scanning (I hope!). Which ever one you use, do a service scan, or scan the first 1024 ports. You could try something fancier like a SYN or XMAS scan if it's a BSD based appliance. Also, does it have a USB port or any other interface? Like anything else, it's just about getting your foot in the door, after that, you just need a bit of leverage. ;) The thing is, most of these boxes have to have a way for the upstream vendor to upgrade the firmware, which is usually just an IMG of the compressed OS, so they're usually not completely locked down. Below are the port scan results: Starting nmap 3.93 ( http://www.insecure.org/nmap/ ) at 2008-04-28 18:17 UTC Interesting ports on 192.168.2.17: (The 65532 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 445/tcp open microsoft-ds 4301/tcp open unknown MAC Address: 00:10:75:00:FD:91 (Maxtor) Nmap finished: 1 IP address (1 host up) scanned in 15.124 seconds The device does have two USB ports in addition to the ethernet port. FWIW, new firmware can be downloaded into the device via the browser interface, so perhaps there is some way to use port 80 to see the filesystem? Best Regards, Rick J. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Maxtor NAS share problem
Scott Lovenberg wrote: Scott Lovenberg wrote: Rick Johnson wrote: Toby Bluhm wrote: Rick Johnson wrote: Adam Williams wrote: what are the settings on the share you're trying to mount? does it have something like valid users = rickj Well, that is hard to determine. If you're asking whether the drive has something like an smb.conf file containing share settings the answer is no. The only access I have to the Maxtor drive is via a browser interface. I have used the menu in that to set all files for full public access, but beyond that I have no finer control. (I have So in public mode, it's probably going to throw all user info away and map everything to a universal id. Have you looked closely at the file perm/ownership from the Windows client? Saved files as joe user then jane user - does it keep the distinction? I'll venture no. There is no Windows client. The Maxtor shows up in My Netowrk Places and is mapped as just another drive from Windows; in my particular case, as the Z drive. If it's possible, have you tried setting up individual users through the nas interface? Yes. The drive has been set up with different users since the beginning. Could also just work with the fact that no perm/owner info will be kept. Collect that info store it to a file. A recursive getfacl to collect setfacl to restore could do the trick. Judging by what I see through the web interface, there must be SOME type of user info stored, but how or where I don't know and can't see. found via www.openmss.org that the underlying filesystem of the drive is Linux - reiser I think - but beyond that I have no data on the filesystem other than what I see when I smbmount the drive.) Perhaps there's a way to break into the Linux the nas is running change stuff to your suiting. I think this is a possibility and I've been looking for more info; unfortunately without success so far. I've heard many times of people with an appliance trying to do something beyond its intended function hitting a brick wall. Your situation is why I never recommend an appliance to anyone other than a pure, non-hacker, non-power type Windows user. A NAS type distro or even a full distro on a junker PC would be a better solution. More work, but better results. You're probably right. But since I've already got the drive I need to figure out a way to use it. Rick J. Have you scanned for open ports? These things usually have SSH or telnet or some other maintenance port open with a known default user/pass. After looking at www.openmss.org a bit, it seems that it keeps users in nvram. Looks like you can update the firmware via the web interface, and that will give you an SSHD to log in to. That might be either the best way to go about this, or the fastest way to brick the appliance. :) (The 65532 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 445/tcp open microsoft-ds 4301/tcp open unknown MAC Address: 00:10:75:00:FD:91 (Maxtor) Well, it's about as useful to me as a brick right now, so maybe I've got nothing to lose! ;-) Seriously though, I don't know SSHD so what does that mean exactly? All I know is that SSH is a sort of secure telnet, but I've never used it much. Best Regards, Rick J. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Maxtor NAS share problem
Toby Bluhm wrote: Judging by what I see through the web interface, there must be SOME type of user info stored, but how or where I don't know and can't see. I was talking about saving the Linux filesystem info. Do your rsync to the NAS, then do a recursive getfacl, redirecting the output to a file on the NAS. When you do an rsync back from the NAS, correct the owner/perms with setfacl. Trouble is that I CAN'T do my rsync to the NAS drive because it doesn't give me the access privileges I need to write to the NAS. The rsync wants to change owner and the NAS won't let it do that. Better yet, look into dar - http://dar.linux.free.fr - a tar like backup designed for saving to files on disk. It shouldn't care (much) about the filesystem it's stored on. Thanks. I'll check it out! Best Regards, Rick J. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba fails diagnosis.txt test #5 nmblookup
I am using diagnosis.txt on a connection between Kubuntu Gutsy Gibbon and a Windows XP machine with service pack 1 and 2 installed. !== DIAGNOSIS.txt for Samba release 2.0.7 26 Apr 2000 Contributor:Andrew Tridgell Updated:November 1, 1999 Subject:DIAGNOSING YOUR SAMBA SERVER diagnosis.txt fails on test #5. TEST 5: --- run the command nmblookup -B winpro '*' You should get the PCs IP address back. If you don't then the client software on the PC isn't installed correctly, or isn't started, or you got the name of the PC wrong. If winpro doesn't resolve via DNS then use the IP address of the client in the above test. The result is: added interface ip=10.22.44.4 bcast=10.22.44.255 nmask=255.255.255.0 added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0 Socket opened. querying * on 10.22.44.11 name_query failed to find name * How can I test whether the client software on the PC (Windows XP) isn't installed correctly, or isn't started? I'm pretty sure the name of the PC is correct. What client software should I be looking for? Larry -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: interdomain trust between two samba pdc's
i think you have to create the trusts on both DOMAINS as they only work in one direction. the official samba how to and reference guide briefly touches on the subject. SoUnD WrEcK wrote: So is no one here doing interdomain trusts using two Samba PDC's on two different subnets? I have been struggling with this problem for a long time now, and would like some help with it. Thanks! On Fri, Apr 25, 2008 at 2:54 PM, SoUnD WrEcK [EMAIL PROTECTED] wrote: I have been trying off and on for some time now to get an interdomain trust relationship going between two samba pdc machines (DomainA=trusted DomainB=trusting). Both pdc's are running on Solaris boxes and NIS is involved (I doubt there is a NIS complication just because I can use accounts on DomainA on DomainB's samba, as long as I add them using smbpasswd manually). The situation is this. DomainA hosts most user accounts for my two networks. Therefore DomainA should be trusted and DomainB should be trusting. The documentation is confusing and does not describe this exact scenario (talks about samba with microsoft pdc's). I have tried every combination I can think of, but things still aren't working as they should. I have added an account for DomainB on DomainA. I then type smbpasswd -a -i DomainB, still working on DomainA. This seems to go through okay. However, when I type net rpc trustdom list on DomainA, I get the following: Trusted domains list: none Trusting domains list: Unable to find a suitable server domain controller is not responding DomainB I expect what I see for trusted, but for trusting, should I really be seeing those errors? What do they mean? Is the fact that DomainB is listed mean that it worked and I should ignore the errors? I guess I'll stop here and make sure there is not a problem with this step before I post further information about this process. Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Unable to access linux files from windows using samba configured in linux Vmware
Squeezer99 wrote: take out the space between the , and password=abc and the extra / on //home/abc when i tried mount -t cifs //192.168.248.195/home/abc /mnt -o username=abc,password=abc it is giving the following error mount error 5 = Input/Output error Refer to the mount.cifs(8) manual page (e.g man mount.cifs ) -- View this message in context: http://www.nabble.com/Unable-to-access-linux-files-from-windows-using-samba-configured-in-linux-Vmware-tp16847019p16952913.html Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
You have a new comment on your page on ssbbw4u.
You have a new comment on your page on ssbbw4u. To view the new comment, visit: http://ssbbw4u.ning.com/profiles/comment/list?attachedTo=1y097hdzlqda6attachedToType=Userxgsi=1#chatter-2000563:Comment:11192 -- To control which emails you receive on ssbbw4u, go to: http://ssbbw4u.ning.com/profiles/profile/emailSettings PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Monday, April 28 - Samba Mashup Report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ** Samba Mashup Report (SMR) for Monday April 28, 2008 ** Table of Contents: 0. Greetings to the Inaugural SMR (samba Mashup Report) 1. Plans in Motion for 6 Month Samba 3.x Release Cycles 2. Samba 3.2.0pre3 Released 3. Samba XP 2008 Concludes as YASC (yet another successful conference) 4. Samba Documentation repository moved from SVN to Git 5. Bugzilla Day for Samba 3.2 scheduled for Friday, May 9. 6. Call for developer reports === 0. Greetings to the Inaugural SMR (samba Mashup Report) === Several of Samba team members agreed during discussions held at Samba XP (see article #3) that periodic thread summaries from the recent development activities would be helpful for keeping the community and Samba OEM vendors up to date. So using editorial privilege, I've decided to term these as mashup reports. According to the pop culture definition from Wikipedia, mashup usually means: * A web application that combines data and/or functionality from more than one source * A musical genre of songs that consist entirely of parts of other songs * A video that is edited from more than one source to appear as one * In parts of the UK means a mash or pot of tea (colloq. Yorkshire), other areas brew or stand tea The second and third definitions are probably the most appropriate here. So without further ado, here's the inaugural bi-weekly (give or take a few days) report. cheers, jerry 1. Plans in Motion for 6 Month Release Cycle Based on feedback from the community, Samba Team members have agreed to put into place a six month release cycle on new Samba 3.x releases. The initial 3.2 release will start the clock on the next major development effort. In the thread beginning at [1], Jerry Carter (Samba Team member) proposed: Once a new release cycle is done, that version goes straight to bug fix mode and the next release cycle gets a new minor release number. So for example, assume 3.2.0 is released in the next 30 days. The 3.2 releases are immediately in maintenance mode meaning we can fix all the regressions and bugs we like. But no new features. The next 6 month cycle clock starts ticking and that becomes v3.3. Karolin (Seeger) will have the job of setting dates and we have to stick to them. Christian Perrier (a Debian samba package maintainer) pointed out this would be a lot of work and maybe not achievable. Jim McDonough (Samba Team member) highlighted Jerry's main point which is: ...it will definitely require a mind shift from the Wait, we have to have _my_ major piece mode that currently dominates scheduling of releases. The developer who writes the code has to decide if the code will be ready for the schedule, rather than delaying the schedule (and everyone's code) until the code is ready. === 2. Samba 3.2.0pre3 Released === The third Preview release of Samba 3.2.0 was released on Friday, April 25 [2]. This is the last scheduled preview release with an estimated date for RC1 set by Karolin Seeger (Samba 3.2 release manager) of May 23 [3]. The number and frequency of release candidates will be decided by the quality and feedback from the community testers of the pre3 release. And in preparation for committing to a 6 month release cycle, the Samba 3.3 development branch has been created to stem the rate of change in the 3.2 code [4][5]. Samba 3.3 is tentatively scheduled for delivery sometime in December, 2008. === 3. Samba XP 2008 Concludes as YASC (yet another successful conference) === The seventh annual Samba eXPerience Conference concluded in Goettingen, DE, on April 18th [6]. Talks were presented about topics such as: * Samba's relationship with the Protocol Freedom Information Foundation (PFIF) * SMB2 protocol details * The latest developments in projects such as the Linux CIFS file system, OpenChange, and of course Samba itself. This year marked a milestone as bother members of the Samba Team, Microsoft engineers, and developers from numerous companies openly presented and discussed details of CIFS and related protocol based upon newly available WSPP documentation. Conference pictures are available on-line now. The audio portion of talks as well as session slides will be available soon from the conference web site. === 4. Samba Documentation repository moved from SVN to Git === The Docbook/XML source of the Samba HOWTOs and man pages is no longer
[SCM] Samba Shared Repository - branch v3-2-test updated - release-3-2-0pre2-2259-ge805c3a
The branch, v3-2-test has been updated via e805c3a2184d86b8e56716b228bc5a240957dad0 (commit) from 2883e554f45ca01dbfc205baa0b4149d2f2a01e8 (commit) http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-test - Log - commit e805c3a2184d86b8e56716b228bc5a240957dad0 Author: Karolin Seeger [EMAIL PROTECTED] Date: Mon Apr 28 09:19:41 2008 +0200 WHATSNEW: Preparation for 3.2.0rc1. Karolin --- Summary of changes: WHATSNEW.txt | 11 --- 1 files changed, 8 insertions(+), 3 deletions(-) Changeset truncated at 500 lines: diff --git a/WHATSNEW.txt b/WHATSNEW.txt index 3b56d6c..766ab79 100644 --- a/WHATSNEW.txt +++ b/WHATSNEW.txt @@ -1,9 +1,9 @@ = - Release Notes for Samba 3.2.0pre3 - Apr 25, 2008 + Release Notes for Samba 3.2.0rc1 + May 23, 2008 = -This is the third preview release of Samba 3.2.0. This is *not* +This is the first release candidate of Samba 3.2.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. @@ -207,6 +207,11 @@ smb.conf changes New special meaning of include = registry. +Changes since 3.2.0pre3: +--- + + + Changes since 3.2.0pre2: --- -- Samba Shared Repository
[SCM] Samba Shared Repository - branch v3-2-stable updated - release-3-2-0pre3-1-g791a3a4
The branch, v3-2-stable has been updated via 791a3a48fb1cacf1c3074e5a3d744be8b14f98e6 (commit) from be08a479dc09c74245a1e11b69150748be4a4ec8 (commit) http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-stable - Log - commit 791a3a48fb1cacf1c3074e5a3d744be8b14f98e6 Author: Karolin Seeger [EMAIL PROTECTED] Date: Mon Apr 28 09:19:41 2008 +0200 WHATSNEW: Preparation for 3.2.0rc1. Karolin (cherry picked from commit e805c3a2184d86b8e56716b228bc5a240957dad0) --- Summary of changes: WHATSNEW.txt | 11 --- 1 files changed, 8 insertions(+), 3 deletions(-) Changeset truncated at 500 lines: diff --git a/WHATSNEW.txt b/WHATSNEW.txt index a38eb0b..7c5153f 100644 --- a/WHATSNEW.txt +++ b/WHATSNEW.txt @@ -1,9 +1,9 @@ = - Release Notes for Samba 3.2.0pre3 - Apr 25, 2008 + Release Notes for Samba 3.2.0rc1 + May 23, 2008 = -This is the third preview release of Samba 3.2.0. This is *not* +This is the first release candidate of Samba 3.2.0. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. @@ -204,6 +204,11 @@ smb.conf changes New special meaning of include = registry. +Changes since 3.2.0pre3: +--- + + + Changes since 3.2.0pre2: --- -- Samba Shared Repository
[SCM] Samba Shared Repository - branch v3-2-test updated - release-3-2-0pre2-2260-gbfb91c0
The branch, v3-2-test has been updated via bfb91c078c28f528581058ba22d31c32616aa869 (commit) from e805c3a2184d86b8e56716b228bc5a240957dad0 (commit) http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-test - Log - commit bfb91c078c28f528581058ba22d31c32616aa869 Author: Karolin Seeger [EMAIL PROTECTED] Date: Mon Apr 28 10:01:12 2008 +0200 WHATSNEW: Add changes from Steven Danneman. Karolin --- Summary of changes: WHATSNEW.txt |4 1 files changed, 4 insertions(+), 0 deletions(-) Changeset truncated at 500 lines: diff --git a/WHATSNEW.txt b/WHATSNEW.txt index 766ab79..a20738b 100644 --- a/WHATSNEW.txt +++ b/WHATSNEW.txt @@ -211,6 +211,10 @@ Changes since 3.2.0pre3: --- +o Steven Danneman [EMAIL PROTECTED](none) +* Bug 5419: Fix memory leak in ads_do_search_all_args() when enumerating + 1000s of entries + Changes since 3.2.0pre2: --- -- Samba Shared Repository
[SCM] Samba Shared Repository - branch v3-2-stable updated - release-3-2-0pre3-3-gec6306d
The branch, v3-2-stable has been updated
via ec6306db8f82f237ab3ebb9f1a4098dbc1cb05de (commit)
via 64edcda438023c4c8d95f1cc5f70627bda357305 (commit)
from 791a3a48fb1cacf1c3074e5a3d744be8b14f98e6 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-stable
- Log -
commit ec6306db8f82f237ab3ebb9f1a4098dbc1cb05de
Author: Karolin Seeger [EMAIL PROTECTED]
Date: Mon Apr 28 10:01:12 2008 +0200
WHATSNEW: Add changes from Steven Danneman.
Karolin
(cherry picked from commit bfb91c078c28f528581058ba22d31c32616aa869)
commit 64edcda438023c4c8d95f1cc5f70627bda357305
Author: Steven Danneman [EMAIL PROTECTED](none)
Date: Fri Apr 25 18:34:46 2008 -0700
Fix bug 5419: memory leak in ads_do_search_all_args() when enumerating
1000s of entries
The ads_do_search_all_args() function attempts to string together several
LDAPMessage structures, returned across several paged ldap requests, into a
single LDAPMessage structure. It does this by pulling entries off the
second
LDAPMessage structure and appending them to the first via the OpenLDAP
specific
ldap_add_result_entry() call.
The problem with this approach is it skips non-entry messages such as the
result, and controls. These messages are leaked.
The short term solution as suggested by Volker is to replace the
ads_*_entry()
calls with ads_*_message() calls so we don't leak any messages.
This fixes the leak but doesn't remove the dependence on the OpenLDAP
specific
implementation of ldap_add_result_entry().
(cherry picked from commit fe9f48bfe8d31812d9644682903c04f1e93c2987)
---
Summary of changes:
WHATSNEW.txt|4
source/include/ads_protos.h |2 ++
source/libads/ldap.c| 26 --
3 files changed, 30 insertions(+), 2 deletions(-)
Changeset truncated at 500 lines:
diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 7c5153f..05abdc4 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -208,6 +208,10 @@ Changes since 3.2.0pre3:
---
+o Steven Danneman [EMAIL PROTECTED](none)
+* Bug 5419: Fix memory leak in ads_do_search_all_args() when enumerating
+ 1000s of entries
+
Changes since 3.2.0pre2:
---
diff --git a/source/include/ads_protos.h b/source/include/ads_protos.h
index 738df3e..a372010 100644
--- a/source/include/ads_protos.h
+++ b/source/include/ads_protos.h
@@ -89,6 +89,8 @@ ADS_STATUS ads_search_retry_sid(ADS_STRUCT *ads, LDAPMessage
**res,
LDAPMessage *ads_first_entry(ADS_STRUCT *ads, LDAPMessage *res);
LDAPMessage *ads_next_entry(ADS_STRUCT *ads, LDAPMessage *res);
+LDAPMessage *ads_first_message(ADS_STRUCT *ads, LDAPMessage *res);
+LDAPMessage *ads_next_message(ADS_STRUCT *ads, LDAPMessage *res);
void ads_process_results(ADS_STRUCT *ads, LDAPMessage *res,
bool (*fn)(ADS_STRUCT *,char *, void **, void *),
void *data_area);
diff --git a/source/libads/ldap.c b/source/libads/ldap.c
index b0f27b5..9321302 100644
--- a/source/libads/ldap.c
+++ b/source/libads/ldap.c
@@ -870,8 +870,8 @@ static ADS_STATUS ads_do_paged_search(ADS_STRUCT *ads,
const char *bind_path,
/* this relies on the way that ldap_add_result_entry() works
internally. I hope
that this works on all ldap libs, but I have only tested
with openldap */
- for (msg = ads_first_entry(ads, res2); msg; msg = next) {
- next = ads_next_entry(ads, msg);
+ for (msg = ads_first_message(ads, res2); msg; msg = next) {
+ next = ads_next_message(ads, msg);
ldap_add_result_entry((LDAPMessage **)res, msg);
}
/* note that we do not free res2, as the memory is now
@@ -2091,6 +2091,28 @@ int ads_count_replies(ADS_STRUCT *ads, void *res)
}
/**
+ * pull the first message from a ADS result
+ * @param ads connection to ads server
+ * @param res Results of search
+ * @return first message from result
+ **/
+ LDAPMessage *ads_first_message(ADS_STRUCT *ads, LDAPMessage *res)
+{
+ return ldap_first_message(ads-ldap.ld, res);
+}
+
+/**
+ * pull the next message from a ADS result
+ * @param ads connection to ads server
+ * @param res Results of search
+ * @return next message from result
+ **/
+ LDAPMessage *ads_next_message(ADS_STRUCT *ads, LDAPMessage *res)
+{
+ return ldap_next_message(ads-ldap.ld, res);
+}
+
+/**
* pull a single string from a ADS result
* @param ads connection to ads server
* @param mem_ctx TALLOC_CTX to use for allocating result string
--
Samba Shared Repository
[SCM] Samba Shared Repository - branch v3-2-stable updated - release-3-2-0pre3-4-gffe50b9
The branch, v3-2-stable has been updated
via ffe50b90b04b204e985ee62a0795c9bffd446a54 (commit)
from ec6306db8f82f237ab3ebb9f1a4098dbc1cb05de (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-stable
- Log -
commit ffe50b90b04b204e985ee62a0795c9bffd446a54
Author: Volker Lendecke [EMAIL PROTECTED]
Date: Fri Apr 25 17:04:44 2008 +0200
Revert mount.cifs: Zero mountpassword content before freeing.
This reverts commit d99a31848bd2172c15500dd61ce30fef963c1ac6.
(cherry picked from commit 46614ca3eca67aee4c1ab699e85493f9832e4b37)
---
Summary of changes:
source/client/mount.cifs.c | 27 +++
1 files changed, 3 insertions(+), 24 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source/client/mount.cifs.c b/source/client/mount.cifs.c
index 7432dac..1b67a5e 100644
--- a/source/client/mount.cifs.c
+++ b/source/client/mount.cifs.c
@@ -160,9 +160,6 @@ static void mount_cifs_usage(void)
printf(\nTo display the version number of the mount helper:);
printf(\n\t%s -V\n,thisprogram);
- if(mountpassword) {
- memset(mountpassword,0,MOUNT_PASSWD_SIZE);
- }
SAFE_FREE(mountpassword);
exit(1);
}
@@ -222,9 +219,6 @@ static int open_cred_file(char * file_name)
if(length 4086) {
printf(mount.cifs failed due to
malformed username in credentials file);
memset(line_buf,0,4096);
- if(mountpassword) {
-
memset(mountpassword,0,MOUNT_PASSWD_SIZE);
- }
exit(1);
} else {
got_user = 1;
@@ -291,9 +285,6 @@ static int open_cred_file(char * file_name)
}
fclose(fs);
- if(line_buf) {
- memset(line_buf,0,4096);
- }
SAFE_FREE(line_buf);
return 0;
}
@@ -328,7 +319,6 @@ static int get_password_from_file(int file_descript, char *
filename)
rc = read(file_descript,c,1);
if(rc 0) {
printf(mount.cifs failed. Error %s reading password
file\n,strerror(errno));
- memset(mountpassword,0,MOUNT_PASSWD_SIZE);
if(filename != NULL)
close(file_descript);
exit(1);
@@ -1119,9 +1109,6 @@ int main(int argc, char ** argv)
MOUNT_CIFS_VERSION_MAJOR,
MOUNT_CIFS_VERSION_MINOR,
MOUNT_CIFS_VENDOR_SUFFIX);
- if(mountpassword) {
- memset(mountpassword,0,MOUNT_PASSWD_SIZE);
- }
exit (0);
case 'w':
flags = ~MS_RDONLY;
@@ -1207,7 +1194,7 @@ int main(int argc, char ** argv)
if (getenv(PASSWD)) {
if(mountpassword == NULL)
- mountpassword = (char *)calloc(MOUNT_PASSWD_SIZE+1,1);
+ mountpassword = (char *)calloc(65,1);
if(mountpassword) {
strlcpy(mountpassword,getenv(PASSWD),MOUNT_PASSWD_SIZE);
got_password = 1;
@@ -1442,16 +1429,8 @@ mount_exit:
SAFE_FREE(mountpassword);
}
- if(options) {
- memset(options,0,optlen);
- SAFE_FREE(options);
- }
-
- if(orgoptions) {
- memset(orgoptions,0,orgoptlen);
- SAFE_FREE(orgoptions);
- }
-
+ SAFE_FREE(options);
+ SAFE_FREE(orgoptions);
SAFE_FREE(resolved_path);
SAFE_FREE(share_name);
return rc;
--
Samba Shared Repository
[SCM] Samba Shared Repository - branch v3-3-test updated - release-3-2-0pre2-2227-g70f6966
The branch, v3-3-test has been updated via 70f6966099788f4bdb0298a68d4cb0b90964dd8f (commit) from f1a5405409c396df394611e2a234522572d2860a (commit) http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-3-test - Log - commit 70f6966099788f4bdb0298a68d4cb0b90964dd8f Author: Karolin Seeger [EMAIL PROTECTED] Date: Mon Apr 28 15:26:57 2008 +0200 man smbcacls: Correct possible flag values. This patch fixes bug #620. Thanks to Satoh Fumiyasu [EMAIL PROTECTED]! Karolin --- Summary of changes: docs-xml/manpages-3/smbcacls.1.xml |7 +++ 1 files changed, 3 insertions(+), 4 deletions(-) Changeset truncated at 500 lines: diff --git a/docs-xml/manpages-3/smbcacls.1.xml b/docs-xml/manpages-3/smbcacls.1.xml index 695d58a..5be6b25 100644 --- a/docs-xml/manpages-3/smbcacls.1.xml +++ b/docs-xml/manpages-3/smbcacls.1.xml @@ -182,10 +182,9 @@ ACL:lt;sid or namegt;:lt;typegt;/lt;flagsgt;/lt;maskgt; resides. The type, flags and mask values determine the type of access granted to the SID. /para - paraThe type can be either 0 or 1 corresponding to ALLOWED or - DENIED access to the SID. The flags values are generally - zero for file ACLs and either 9 or 2 for directory ACLs. Some - common flags are: /para + paraThe type can be either ALLOWED or DENIED to allow/deny access + to the SID. The flags values are generally zero for file ACLs and + either 9 or 2 for directory ACLs. Some common flags are: /para itemizedlist listitemparaconstant#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1/constant/para/listitem -- Samba Shared Repository
[SCM] Samba Shared Repository - branch v3-2-test updated - release-3-2-0pre2-2261-g15e51b5
The branch, v3-2-test has been updated via 15e51b59777e0d0b6d6fac24764fbfb5f84e0365 (commit) from bfb91c078c28f528581058ba22d31c32616aa869 (commit) http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-test - Log - commit 15e51b59777e0d0b6d6fac24764fbfb5f84e0365 Author: Karolin Seeger [EMAIL PROTECTED] Date: Mon Apr 28 15:26:57 2008 +0200 man smbcacls: Correct possible flag values. This patch fixes bug #620. Thanks to Satoh Fumiyasu [EMAIL PROTECTED]! Karolin (cherry picked from commit 70f6966099788f4bdb0298a68d4cb0b90964dd8f) --- Summary of changes: docs-xml/manpages-3/smbcacls.1.xml |7 +++ 1 files changed, 3 insertions(+), 4 deletions(-) Changeset truncated at 500 lines: diff --git a/docs-xml/manpages-3/smbcacls.1.xml b/docs-xml/manpages-3/smbcacls.1.xml index 695d58a..5be6b25 100644 --- a/docs-xml/manpages-3/smbcacls.1.xml +++ b/docs-xml/manpages-3/smbcacls.1.xml @@ -182,10 +182,9 @@ ACL:lt;sid or namegt;:lt;typegt;/lt;flagsgt;/lt;maskgt; resides. The type, flags and mask values determine the type of access granted to the SID. /para - paraThe type can be either 0 or 1 corresponding to ALLOWED or - DENIED access to the SID. The flags values are generally - zero for file ACLs and either 9 or 2 for directory ACLs. Some - common flags are: /para + paraThe type can be either ALLOWED or DENIED to allow/deny access + to the SID. The flags values are generally zero for file ACLs and + either 9 or 2 for directory ACLs. Some common flags are: /para itemizedlist listitemparaconstant#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1/constant/para/listitem -- Samba Shared Repository
[SCM] Samba Shared Repository - branch v3-2-stable updated - release-3-2-0pre3-5-g79677ea
The branch, v3-2-stable has been updated via 79677ea9da38ad56347cfcbdc1f2ee0ebab407e6 (commit) from ffe50b90b04b204e985ee62a0795c9bffd446a54 (commit) http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-stable - Log - commit 79677ea9da38ad56347cfcbdc1f2ee0ebab407e6 Author: Karolin Seeger [EMAIL PROTECTED] Date: Mon Apr 28 15:26:57 2008 +0200 man smbcacls: Correct possible flag values. This patch fixes bug #620. Thanks to Satoh Fumiyasu [EMAIL PROTECTED]! Karolin (cherry picked from commit 70f6966099788f4bdb0298a68d4cb0b90964dd8f) --- Summary of changes: docs-xml/manpages-3/smbcacls.1.xml |7 +++ 1 files changed, 3 insertions(+), 4 deletions(-) Changeset truncated at 500 lines: diff --git a/docs-xml/manpages-3/smbcacls.1.xml b/docs-xml/manpages-3/smbcacls.1.xml index 695d58a..5be6b25 100644 --- a/docs-xml/manpages-3/smbcacls.1.xml +++ b/docs-xml/manpages-3/smbcacls.1.xml @@ -182,10 +182,9 @@ ACL:lt;sid or namegt;:lt;typegt;/lt;flagsgt;/lt;maskgt; resides. The type, flags and mask values determine the type of access granted to the SID. /para - paraThe type can be either 0 or 1 corresponding to ALLOWED or - DENIED access to the SID. The flags values are generally - zero for file ACLs and either 9 or 2 for directory ACLs. Some - common flags are: /para + paraThe type can be either ALLOWED or DENIED to allow/deny access + to the SID. The flags values are generally zero for file ACLs and + either 9 or 2 for directory ACLs. Some common flags are: /para itemizedlist listitemparaconstant#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1/constant/para/listitem -- Samba Shared Repository
svn commit: samba-web r1185 - in trunk: . mashup
Author: jerry Date: 2008-04-28 16:09:11 + (Mon, 28 Apr 2008) New Revision: 1185 WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=revroot=samba-webrev=1185 Log: Adding the first edition of SMR Added: trunk/mashup/ trunk/mashup/SMR-04-28-2008.html Changeset: Added: trunk/mashup/SMR-04-28-2008.html === --- trunk/mashup/SMR-04-28-2008.html2008-04-25 16:26:38 UTC (rev 1184) +++ trunk/mashup/SMR-04-28-2008.html2008-04-28 16:09:11 UTC (rev 1185) @@ -0,0 +1,204 @@ +!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN +http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; +html xmlns=http://www.w3.org/1999/xhtml; + +head +titleSamba Mashup Report - April 28, 2008/title +/head + +body + + H2Samba Mashup Report - April 28, 2008/H2 + +p +pre +Table of Contents: + + a href=#section00./a Greetings to the Inaugural SMR (samba Mashup Report) + a href=#section11./a Plans in Motion for 6 Month Samba 3.x Release Cycles + a href=#section22./a Samba 3.2.0pre3 Released + a href=#section33./a Samba XP 2008 Concludes as YASC (yet another successful + conference) + a href=#section44./a Samba Documentation repository moved from SVN to Git + a href=#section55./a Bugzilla Day for Samba 3.2 scheduled for Friday, May 9. + a href=#section66./a Call for developer reports + + +=== +a name=section00./a Greetings to the Inaugural SMR (samba Mashup Report) +=== + +Several of Samba team members agreed during discussions +held at Samba XP (see article #3) that periodic thread +summaries from the recent development activities would +be helpful for keeping the community and Samba OEM vendors +up to date. So using editorial privilege, I've decided to +term these as mashup reports. + +According to the pop culture definition from Wikipedia, +mashup usually means: + +* A web application that combines data and/or + functionality from more than one source +* A musical genre of songs that consist entirely of + parts of other songs +* A video that is edited from more than one source + to appear as one +* In parts of the UK means a mash or pot of tea + (colloq. Yorkshire), other areas brew or stand tea + +The second and third definitions are probably the most +appropriate here. So without further ado, here's the +inaugural bi-weekly (give or take a few days) report. + +cheers, jerry + + + +a name=section11./a Plans in Motion for 6 Month Release Cycle + + +Based on feedback from the community, Samba Team members have +agreed to put into place a six month release cycle on new +Samba 3.x releases. The initial 3.2 release will start the +clock on the next major development effort. + +In the thread beginning at [1], Jerry Carter (Samba Team +member) proposed: + +Once a new release cycle is done, that version goes +straight to bug fix mode and the next release cycle gets +a new minor release number. + +So for example, assume 3.2.0 is released in the next +30 days. The 3.2 releases are immediately in maintenance +mode meaning we can fix all the regressions and bugs we +like. But no new features. The next 6 month cycle clock +starts ticking and that becomes v3.3. + +Karolin (Seeger) will have the job of setting dates and +we have to stick to them. + +Christian Perrier (a Debian samba package maintainer) pointed +out this would be a lot of work and maybe not achievable. +Jim McDonough (Samba Team member) highlighted Jerry's main +point which is: + +...it will definitely require a mind shift from the Wait, +we have to have _my_ major piece mode that currently +dominates scheduling of releases. The developer who writes +the code has to decide if the code will be ready for the +schedule, rather than delaying the schedule (and everyone's +code) until the code is ready. + + +=== +a name=section22./a Samba 3.2.0pre3 Released +=== + +The third Preview release of Samba 3.2.0 was released on +Friday, April 25 [2]. This is the last scheduled preview +release with an estimated date for RC1 set by Karolin Seeger +(Samba 3.2 release manager) of May 23 [3]. The number and +frequency of release candidates will be decided by the +quality and feedback from the community testers of the pre3 +release. + +And in preparation for committing to a 6 month release cycle, +the Samba 3.3 development branch has been created to stem +the rate of change in the 3.2 code [4][5]. Samba 3.3 is +tentatively scheduled for delivery sometime in December, 2008. + + + +=== +a name=section33./a Samba XP 2008 Concludes as YASC (yet another + successful
[SCM] Samba Shared Repository - branch v3-3-test updated - release-3-2-0pre2-2228-gfbd9907
The branch, v3-3-test has been updated
via fbd99071f99cadd21aa2b8971f745a323a9cda13 (commit)
from 70f6966099788f4bdb0298a68d4cb0b90964dd8f (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-3-test
- Log -
commit fbd99071f99cadd21aa2b8971f745a323a9cda13
Author: Jeremy Allison [EMAIL PROTECTED]
Date: Mon Apr 28 15:06:08 2008 -0700
Fix bug found by Igor Mammedov [EMAIL PROTECTED] where we are
not returning a directory value for a QPATHINFO on a msdfs link
with a non-dfs path. Windows does this.
Jeremy.
---
Summary of changes:
source/smbd/trans2.c | 56 +
1 files changed, 42 insertions(+), 14 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source/smbd/trans2.c b/source/smbd/trans2.c
index 709eb39..41f2a15 100644
--- a/source/smbd/trans2.c
+++ b/source/smbd/trans2.c
@@ -1196,6 +1196,32 @@ static NTSTATUS unix_perms_from_wire( connection_struct
*conn,
}
/
+ Needed to show the msdfs symlinks as directories. Modifies psbuf
+ to be a directory if it's a msdfs link.
+/
+
+static bool check_msdfs_link(connection_struct *conn,
+ const char *pathname,
+ SMB_STRUCT_STAT *psbuf)
+{
+ int saved_errno = errno;
+ if(lp_host_msdfs()
+ lp_msdfs_root(SNUM(conn))
+ is_msdfs_link(conn, pathname, psbuf)) {
+
+ DEBUG(5,(check_msdfs_link: Masquerading msdfs link %s
+ as a directory\n,
+ pathname));
+ psbuf-st_mode = (psbuf-st_mode 0xFFF) | S_IFDIR;
+ errno = saved_errno;
+ return true;
+ }
+ errno = saved_errno;
+ return false;
+}
+
+
+/
Get a level dependent lanman2 dir entry.
/
@@ -1360,16 +1386,8 @@ static bool get_lanman2_dir_entry(TALLOC_CTX *ctx,
/* Needed to show the msdfs symlinks as
* directories */
- if(lp_host_msdfs()
- lp_msdfs_root(SNUM(conn))
- ((ms_dfs_link = is_msdfs_link(conn,
pathreal, sbuf)) == True)) {
- DEBUG(5,(get_lanman2_dir_entry:
Masquerading msdfs link %s
- as a directory\n,
- pathreal));
- sbuf.st_mode = (sbuf.st_mode 0xFFF) |
S_IFDIR;
-
- } else {
-
+ ms_dfs_link = check_msdfs_link(conn, pathreal,
sbuf);
+ if (!ms_dfs_link) {
DEBUG(5,(get_lanman2_dir_entry:Couldn't stat [%s] (%s)\n,
pathreal,strerror(errno)));
TALLOC_FREE(pathreal);
@@ -3806,6 +3824,7 @@ static void call_trans2qfilepathinfo(connection_struct
*conn,
struct ea_list *ea_list = NULL;
uint32 access_mask = 0x12019F; /* Default - GENERIC_EXECUTE mapping
from Windows */
char *lock_data = NULL;
+ bool ms_dfs_link = false;
TALLOC_CTX *ctx = talloc_tos();
if (!params) {
@@ -3959,10 +3978,15 @@ static void call_trans2qfilepathinfo(connection_struct
*conn,
reply_unixerror(req, ERRDOS, ERRbadpath);
return;
}
+
} else if (!VALID_STAT(sbuf) SMB_VFS_STAT(conn,fname,sbuf)
(info_level != SMB_INFO_IS_NAME_VALID)) {
- DEBUG(3,(call_trans2qfilepathinfo: SMB_VFS_STAT of %s
failed (%s)\n,fname,strerror(errno)));
- reply_unixerror(req, ERRDOS, ERRbadpath);
- return;
+ ms_dfs_link = check_msdfs_link(conn,fname,sbuf);
+
+ if (!ms_dfs_link) {
+ DEBUG(3,(call_trans2qfilepathinfo:
SMB_VFS_STAT of %s failed (%s)\n,fname,strerror(errno)));
+ reply_unixerror(req, ERRDOS, ERRbadpath);
+ return;
+ }
}
fileid = vfs_file_id_from_sbuf(conn, sbuf);
@@ -3987,7 +4011,11 @@ static void call_trans2qfilepathinfo(connection_struct
*conn,
else
base_name = p+1;
- mode = dos_mode(conn,fname,sbuf);
+ if (ms_dfs_link) {
+
[SCM] Samba Shared Repository - branch v3-2-test updated - release-3-2-0pre2-2262-g1b2f189
The branch, v3-2-test has been updated
via 1b2f189e1f78a52a4d1e224bb5d20d77bb192d56 (commit)
from 15e51b59777e0d0b6d6fac24764fbfb5f84e0365 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-test
- Log -
commit 1b2f189e1f78a52a4d1e224bb5d20d77bb192d56
Author: Jeremy Allison [EMAIL PROTECTED]
Date: Mon Apr 28 15:06:14 2008 -0700
Fix bug found by Igor Mammedov [EMAIL PROTECTED] where we are
not returning a directory value for a QPATHINFO on a msdfs link
with a non-dfs path. Windows does this.
Jeremy.
---
Summary of changes:
source/smbd/trans2.c | 56 +
1 files changed, 42 insertions(+), 14 deletions(-)
Changeset truncated at 500 lines:
diff --git a/source/smbd/trans2.c b/source/smbd/trans2.c
index 709eb39..41f2a15 100644
--- a/source/smbd/trans2.c
+++ b/source/smbd/trans2.c
@@ -1196,6 +1196,32 @@ static NTSTATUS unix_perms_from_wire( connection_struct
*conn,
}
/
+ Needed to show the msdfs symlinks as directories. Modifies psbuf
+ to be a directory if it's a msdfs link.
+/
+
+static bool check_msdfs_link(connection_struct *conn,
+ const char *pathname,
+ SMB_STRUCT_STAT *psbuf)
+{
+ int saved_errno = errno;
+ if(lp_host_msdfs()
+ lp_msdfs_root(SNUM(conn))
+ is_msdfs_link(conn, pathname, psbuf)) {
+
+ DEBUG(5,(check_msdfs_link: Masquerading msdfs link %s
+ as a directory\n,
+ pathname));
+ psbuf-st_mode = (psbuf-st_mode 0xFFF) | S_IFDIR;
+ errno = saved_errno;
+ return true;
+ }
+ errno = saved_errno;
+ return false;
+}
+
+
+/
Get a level dependent lanman2 dir entry.
/
@@ -1360,16 +1386,8 @@ static bool get_lanman2_dir_entry(TALLOC_CTX *ctx,
/* Needed to show the msdfs symlinks as
* directories */
- if(lp_host_msdfs()
- lp_msdfs_root(SNUM(conn))
- ((ms_dfs_link = is_msdfs_link(conn,
pathreal, sbuf)) == True)) {
- DEBUG(5,(get_lanman2_dir_entry:
Masquerading msdfs link %s
- as a directory\n,
- pathreal));
- sbuf.st_mode = (sbuf.st_mode 0xFFF) |
S_IFDIR;
-
- } else {
-
+ ms_dfs_link = check_msdfs_link(conn, pathreal,
sbuf);
+ if (!ms_dfs_link) {
DEBUG(5,(get_lanman2_dir_entry:Couldn't stat [%s] (%s)\n,
pathreal,strerror(errno)));
TALLOC_FREE(pathreal);
@@ -3806,6 +3824,7 @@ static void call_trans2qfilepathinfo(connection_struct
*conn,
struct ea_list *ea_list = NULL;
uint32 access_mask = 0x12019F; /* Default - GENERIC_EXECUTE mapping
from Windows */
char *lock_data = NULL;
+ bool ms_dfs_link = false;
TALLOC_CTX *ctx = talloc_tos();
if (!params) {
@@ -3959,10 +3978,15 @@ static void call_trans2qfilepathinfo(connection_struct
*conn,
reply_unixerror(req, ERRDOS, ERRbadpath);
return;
}
+
} else if (!VALID_STAT(sbuf) SMB_VFS_STAT(conn,fname,sbuf)
(info_level != SMB_INFO_IS_NAME_VALID)) {
- DEBUG(3,(call_trans2qfilepathinfo: SMB_VFS_STAT of %s
failed (%s)\n,fname,strerror(errno)));
- reply_unixerror(req, ERRDOS, ERRbadpath);
- return;
+ ms_dfs_link = check_msdfs_link(conn,fname,sbuf);
+
+ if (!ms_dfs_link) {
+ DEBUG(3,(call_trans2qfilepathinfo:
SMB_VFS_STAT of %s failed (%s)\n,fname,strerror(errno)));
+ reply_unixerror(req, ERRDOS, ERRbadpath);
+ return;
+ }
}
fileid = vfs_file_id_from_sbuf(conn, sbuf);
@@ -3987,7 +4011,11 @@ static void call_trans2qfilepathinfo(connection_struct
*conn,
else
base_name = p+1;
- mode = dos_mode(conn,fname,sbuf);
+ if (ms_dfs_link) {
+
Build status as of Tue Apr 29 00:00:02 2008
URL: http://build.samba.org/ --- /home/build/master/cache/broken_results.txt.old 2008-04-28 00:00:38.0 + +++ /home/build/master/cache/broken_results.txt 2008-04-29 00:00:56.0 + @@ -1,4 +1,4 @@ -Build status as of Mon Apr 28 00:00:01 2008 +Build status as of Tue Apr 29 00:00:02 2008 Build counts: Tree Total Broken Panic @@ -8,14 +8,14 @@ distcc 1 0 0 ldb 27 10 0 libreplace 26 8 0 -lorikeet-heimdal 24 19 0 +lorikeet-heimdal 24 20 0 pidl 16 13 0 ppp 9 0 0 rsync27 9 0 samba-docs 0 0 0 samba-gtk4 4 0 -samba_3_2_test 28 17 0 -samba_4_0_test 27 22 1 +samba_3_2_test 28 18 0 +samba_4_0_test 27 23 1 smb-build25 4 0 talloc 27 5 0 tdb 27 10 0
