similar to: Samba 3.0.2 Available for Download

I am having problems with the configuration of samba 3.0.1 on a Solaris 2.6 box. This box has no previous samba versions installed. When I try to configure samba I get the following error. # cd samba-3.0.1/source #./configure -with-ads 2>&1 |tree config.new.log fails with the following error:- checking for LDAP support... auto checking ldap.h usability... no checking ldap.h

Hello I have samba-3.0.2 installed into /usr/local/samba/ by means of cd /usr/src/samba-3.0.2/source ./configure --with-acl-support make make install When I run pdbedit -L I get a segfault: oberon root # pdbedit -L Segmentation fault (core dumped) This occurs after samba of unknown version from these two: 3.0.1pre2 3.0.2 has been reinstalled with samba-3.0.2 (gdb) bt #0 0x400f9bf9 in free

Hello, It appears that the FreeBSD port of Samba 3.0.x may be falling behind. The port maintainter does not use Winbind and thus has not kept up with the development of it. 3.0.1 will very shortly be ported to FreeBSD, currently it is still at 3.0.0. I know there have been some recent changes to Samba that help FreeBSD out, and I wanted to make sure that the port of Samba 3.0.x on FreeBSD stays

G'day: Folks, I'm at my wits end trying to join a WIN XP Professional client to a samba 3.0.4 domain running on Slackware 9.1. I haven't used windows since Win 95 days and am not up to speed with it at all. Also, i've tried the O'Reilly Using Samba book (2nd edition), read the samba docs, and browsed the mailing lists but there is so much information I'm even more

works with plaintext passwords (as fallback) NT4.0 incl. servicepack refuses to work (you may recognize this behaviour by repeating entering the login and the password a couple of times. Then you will be able to mount a share). (more on this topic in /usr/doc/packages/samba/ ENCRYPTION.txt). Solution: Well, either you may convince NT via its Windows registry to use plaintext passwords There is

works with plaintext passwords (as fallback) NT4.0 incl. servicepack refuses to work (you may recognize this behaviour by repeating entering the login and the password a couple of times. Then you will be able to mount a share). (more on this topic in /usr/doc/packages/samba/ ENCRYPTION.txt). Solution: Well, either you may convince NT via its Windows registry to use plaintext passwords There is

Dear Samba Team, I have recently upgraded from Samba 2.2.8a to Samba 3.0.2 where I first noticed the issue. I have also installed 3.0.2a to check if the problem I found may have already been fixed before submitting this issue. Here's the problem: After migrating and switching from passdb backend "smbpasswd" to the new "tdbsam" backend, I started having problems with

I see that mksmbpasswd.sh (plus a little editing) would be a good way to set up users with "NO PASSWORD" in bulk. But suppose I don't want the risk of the "NO PASSWORD" approach. Now somebody with root access must run smbpasswd for each user they want to activate. But can't I just do this anyway (with the -a 'add user' option), without ever having run

Hallo, i installed samba V2.0.3 on a linux server in a company. for better security i will use encypted passwords. for synchronisation of the unix password file and the samba password file i tried out the script mksmbpasswd script. my security settings at the server are easy and i set the permissions of the unix passwd file at 774 and also my smbpasswd file at 744. starting the script with the

Never mind, I figured this one out (I think!). Here is what I ran [System: RedHat 7.0/Samba 2.0.7ssl on P-90] cat /etc/passwd | /usr/bin/mksmbpasswd.sh >> smbpasswd (After backing-up the current 'smbpasswd', of course) This seemed to do the trick, however, all of the accounts where disabled by default. I figured this to be the intended behavior (for security with system

-----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

Software: OS: RedHat 9 SMB Ver: 3.0.0(+excel patch) OpenLDAP Ver: 2.0.27-8 (backend) I've noticed that when using ext3+acls when viewing permissions from a windows client, there will be two additional attributes, "CREATOR USER" and "CREATOR GROUP". Is this something from the translation between ext3acls -> windows? Not a big deal, just curious if I'm the

Hi, I'm using samba-3.0.28-0.fc8. I'm trying to build a file server for 100 users. I created a perl script that automatically adds the 100 users plus their passwords with success. Now I'm having difficulty creating a script using the smbpasswd command because passwords must be entered in stdin. I also tried smbpasswd -s option but it asks passwd in stdin. Is there a way that I can use

I have released rsync 3.0.2. This is a security release to fix a potential buffer overflow in the extended attribute support. For more details, see the rsync security advisory page: http://rsync.samba.org/security.html There is a patch there that can be applied to 2.6.9 (if you were using the xattrs.patch), 3.0.0, or 3.0.1. Those running a writable rsync daemon can opt to refuse the

I have released rsync 3.0.2. This is a security release to fix a potential buffer overflow in the extended attribute support. For more details, see the rsync security advisory page: http://rsync.samba.org/security.html There is a patch there that can be applied to 2.6.9 (if you were using the xattrs.patch), 3.0.0, or 3.0.1. Those running a writable rsync daemon can opt to refuse the

Hi, I have a 3.0.3 PDC with the configuration | netbios name = BERTHA | workgroup = MEITNER which is also represented by browse.dat: | bertha:~# cat /var/cache/samba/browse.dat | "MEITNER" c0001000 "BERTHA" "MEITNER" | "BERTHA" 400d9b2b "Lise-Meitner Fileservice" "MEITNER" However,

I've attached a perl script that I wrote to build smbpasswd from /etc/passwd. Please note that this writes a samba-2.0 format smbpasswd file. This script will: # - create accounts that exist in /etc/passwd and not in smbpasswd # - remove accounts that exist in smbpasswd and not in /etc/passwd # - preserve existing password, flags and LCT fields in smbpasswd # - sets new account passwords to

Hi everybody, I have a problem with Samba 3.0.2 using POSIX ACLs for shares. File written from an ACL group/user will get wrong permissions and are unchangeable for other users. First the important informations about the configuration and the setup: a) Base system: Debian 3.0.1 with all updates b) Samba: Self compiled binary within /opt/samba-3.0.2 used the following flags:

Hi, when I tried to build rsync-3.0.2 on i686-linux/gnu, I noticed 2 problems: ==================== (1) With the Linux kernel >=2.6.20, "make check" occasionally fails, due to subsecond timestamps sometimes being truncated and sometimes being rounded upwards (both on i686 and x86_64). Attached are two files demonstrating the problem: rsync-3.0.2-check-out with the relevant output