similar to: regression in 3.2.4? Homedir not retrieved with idmap_ad backend

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've been trying to get Samba 3.2 to work in the past few days, and I'm running into a few problems which I have been unable to solve myself. My first problem isn't blocking for me, but it seems not consistent with documentation. I can't join my server using a domain admin's kerberos ticket. I need to specify "-U

Some empirical testing shows that if I am using the idmap_ad module the template homedir parameter in smb.conf is ignored. I would just like to determine if this is the correct behaviour or if I am doing something wrong. JAB. -- Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk Fife, United Kingdom.

Heya, I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s a problem with the default setup of Ubuntu. Ubuntu uses network-manager to start the network in the background, which in turn causes puppet to start before the network is up. Puppet will then exit because it can''t resolve the server name. Currently I "solve" this problem by uninstalling

I'm testing winbind 3.3.1-1ubuntu1 (jaunty) and my user stored in AD is consistently being returned with a UID of 1000, rather than 10031, which is whats stored in LDAP/AD under uidNumber. If I install the 3.2.3-1ubuntu3.4 packages from intrepid, 'id bryanm' correctly returns 10031, but when upgrading back to 3.3.1-1ubuntu1, I get the wrong UID again. I did an install from source as

On 10 March 2016 at 08:51, Mick Jordan wrote: | I am trying to build R-3.2.4 on an Oracle Enterprise Linux system, where | I have previously built R-3.1.3 and predecessors without problems. I ran Well that is pretty much why R Core asks us to build early, and build often. | "./configure --with-x=no" ok. The make fails in src/extra/xz with what | looks like a Makefile problem: | |

Puppet 3.2.4 is now available. 3.2.4 addresses two security vulnerabilties discovered in the 3.x series of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and CVE-2013-4761. All users of Puppet 3.2.3 and earlier are strongly encouraged to upgrade to 3.2.4. For more information on these vulnerabilities, please visit http://puppetlabs.com/security/cve/cve-2013-4761

To be honest, I'm not sure wether these alternate data stream files were created under 3.2.0 3.2.2 or 3.2.4. I just noticed that they are here and report. How can I make sure that these files will not be created again (some kind of test case that records alternate data streams) ? Is there any possibility to disable this alternate data stream feature ? Fran?ois -------- Original Message

Hi, I'm trying to check the result of my build of 3.2.4 on Solaris 10, but smbd dies shortly after starting: Running Test suite LD_LIBRARY_PATH=/opt/ws/dists/samba-3.2.4/source/bin CREATE TEST ENVIRONMENT IN './st'...DONE STARTING NMBD...DONE STARTING WINBINDD...DONE STARTING SMBD...DONE delaying for nbt name registration smbd failed with status 1! I looked at the smbd_test.log

I am trying to build R-3.2.4 on an Oracle Enterprise Linux system, where I have previously built R-3.1.3 and predecessors without problems. I ran "./configure --with-x=no" ok. The make fails in src/extra/xz with what looks like a Makefile problem: liblzma.a: $(liblzma_a_OBJECTS) $rm -f $@ $(AR) -cr $@ $(liblzma_a_OBJECTS) $(RANLIB) $@ What I see in the make log is:

My CRAN mirror still says this: The latest release (Thursday 2016-03-10, Very Secure Dishes) R-3.2.4.tar.gz, read what's new in the latest version. Should that not be updated? Anyone who has not seen that post won't know to look further. On Wed, 16-Mar-2016 at 08:39PM +0000, Peter Dalgaard wrote: |> The 3.2.4 release had two annoyances which we would rather not have |> in

I have released rsync 3.2.4. Another typical release with both bug fixes and some enhancements. It also contains a security fix for the bundled zlib 1.2.8, which may or may not be used in your particular build configuration. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.4 You can download the source tar file and its signature from

I have released rsync 3.2.4. Another typical release with both bug fixes and some enhancements. It also contains a security fix for the bundled zlib 1.2.8, which may or may not be used in your particular build configuration. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.4 You can download the source tar file and its signature from

I'm hoping someone has seen this before and knows how to resolve it. I am using samba 3.2.4 with a Windows 2008 AD. Samba is configured with security = ADS and works correctly from computers logged into the domain, but does not allow users that are not in the domain to login by specifying their username, without domain included, when trying to access a share. The user can access the share

Hi All, I installed OpenSUSE 11.0, updated samba server to 3.2.4 version. Added two users in linux and samba with user names "test1" and "Test2". (Please note the capital letter in Test2). Created two shares in /srv/samba/shares "test1" and "Test2". The permissions of the shares are as below. drwx------ 2 test1 users 4096 2009-12-11 12:42 test1 drwx------

The 3.2.4 release had two annoyances which we would rather not have in an "ultra-stable" release, designed to hang around for the duration of the 3.3 series. One was a relatively minor Makefile issue affecting system using R's bundled lzma library. The other, rather more serious, affected printing and formatting of POSIXlt objects, which would unpredictably get the Daylight Savings

Thanks for the info, Dirk. The tarball builds don't run make check (because of a policy decision that it is better to have the sources available on all platforms for testing than to have none if it breaks on a single platform). However the build as of tonight has no problem with make check on the build machine. Did you by any chance forget that Matrix is a recommended package and expected to

hi , i have a few problems with usmgr on Version 3.2.4 ( Version 3.2.4-8.1-1931-SUSE-SL11.0 ) samba pdc ldap the download version from ms http://www.microsoft.com/Downloads/details.aspx?FamilyID=c0011ab8-3178-4701-a791-eafba0f42de2&displaylang=en doesnt work giving "device attached to the system is not functioning" whatever i do a old version from usermgr works partially but magic

Hello I have strange authentication problem. My distribution is Centos 5.2 and it`s 64 bit. I Have compiled Samba 3.2.4 from source with following configure options: --with-logfilebase=/var/log/samba \ --with-configdir=/etc/samba \ --with-piddir=/var/run \ --enable-cups \ --with-acl-support \ --with-ads \ --with-automount \ --with-fhs \ --with-pam \ --with-pam_smbpass \ --with-libsmbclient \

I'm hoping somebody can point me to the right documentation for setting up the following scenario. Earlier this year I had Samba 3.0.28a working as a member server of a (Windows Server 2003) AD domain, using Solaris 10 and Heimdal Kerberos. I was able to log into the server using AD accounts, getent passwd worked, etc. I was using "secruity=ads" with these settings (among other):

On 4 March 2016 at 09:11, peter dalgaard wrote: | Thanks for the info, Dirk. | | The tarball builds don't run make check (because of a policy decision that it is better to have the sources available on all platforms for testing than to have none if it breaks on a single platform). However the build as of tonight has no problem with make check on the build machine. Did you by any chance forget