similar to: [Announce] Samba 4.13.3 Available for Download

Release Announcements --------------------- This is the latest stable release of the Samba 4.12 release series. Changes since 4.12.10 --------------------- o Jeremy Allison <jra at samba.org> * BUG 14210: libcli: smb2: Never print length if smb2_signing_key_valid() fails for crypto blob. * BUG 14486: s3: modules: gluster. Fix the error I made in preventing talloc leaks

Release Announcements --------------------- This is the latest stable release of the Samba 4.12 release series. Changes since 4.12.10 --------------------- o Jeremy Allison <jra at samba.org> * BUG 14210: libcli: smb2: Never print length if smb2_signing_key_valid() fails for crypto blob. * BUG 14486: s3: modules: gluster. Fix the error I made in preventing talloc leaks

I am trying to build a linux file server as a domain member w/W2K-ADS . I have: Slackware 10.1 freshly loaded KRB5 1.4 Sleepycat DB 4.3.7 (needed for openLDAP build) OpenLDAP 2.3.23 When building Samba 3.0.11, I recieve the following errors. Using FLAGS = -I/usr/local/include -O -Iinclude -I/usr/local/samba-3.0.11/source/include -I/usr/local /samba-3.0.11/source/ubiqx

Nearly identical results on AIX 5.2 and RedHat 7.3. In both cases: ./configure --with-winbind --with-ads --with-ldap --with-krb5 AIX 5.2: Compiling client/clitar.c client/clitar.c:91: error: parse error before '*' token client/clitar.c:91: warning: data definition has no type or storage class client/clitar.c: In function `tar_parseargs': client/clitar.c:1754: error: `regex_t'

Samba 3.0.11 won't compile on my Solaris 8 machine. It keeps getting compile errors in clitar, although I am using exactly the same configuration options as in Samba 3.0.10. Here is the basic configuration from config.log $ ./configure --with-ldap --with-ads --with-acl-support --with-pam --with-krb5=/usr/local --enable-shared --without-gnu-ld --with-mysql-prefix=/usr/local/mysql

Hi I have problem with smbclient in samba3 rc2, rc4. When I start tar backup with it: smbclient //comp-32/volume pass -U user -d0 -Tc /dev/tape0 > /dev/null [2003/09/23 08:27:46, 0] client/clitar.c:do_tar(830) directory \Kart-32\ [2003/09/23 08:27:46, 0] client/clitar.c:do_tar(830) directory \Kart-32\mairs\ [2003/09/23 08:27:46, 0]

Hello. I am trying to compile samba 3.0.11 on OpenBSD 3.6. At first i tried the ./configure with a number of switches, but when the make failed, i redid it with just plain "./configure && make". The configure works fine. The make runs for awhile but dies with this: Linking bin/swat /usr/local/kerberos/lib/libkrb5.so.3.2: warning: mktemp() possibly used unsafely; consider

(Samba 3.0.1, RedHat 9, share is a w2k3, security = ADS) Here is a snippet of debug level 3 output of an smbclient tar operation, with error at the end. Command is: # smbclient \\\\snapper\\dfs <password> -U Administrator -E -W CISWINNET -D home -d3 -Tqca /tmp/test.tar [2004/01/14 15:05:10, 3] lib/util.c:dos_clean_name(549) dos_clean_name

(Erm, sorry about that...) I was talking about errors of the type: Got 0 bytes. The problem was sporatic, and seemed to be load/speed based. That is, the faster the Linux box, the more errors we had. A look through clitar.c led me to a solution. Currently, clitar.c is written to pad a file with zeros if a file read error occurs. This is normal. All of our errors were of the 0 byte length

My setup is Samba/smbclient version 3.0.1 on linux RedHat 9. \\snapper\dfs is a dfs share on snapper, a Win2k3 Active Directory server. My smb.conf contains: [global] realm = ciswinnet.cis.uab.edu workgroup=CISWINNET security = ADS encrypt passwords = yes password server = snapper.cis.uab.edu client use spnego = yes I am trying to run the following command: smbclient \\\\snapper\\dfs

As of release samba-1.9.16p11, the X option (exclude file) for tar creates doesn't work recursively; if the exclude file is a directory, files that are in the directory or subdirectories are not excluded from the tar create. I would like the exclude feature to work recursively, and attached is a patch to do it. The exclude feature works the same way for both create and extracts. ***

There's a race condition: when a file increases in size when being archived by the tar function in smbclient, the resulting tar file is created with an invalid format. The tar header for the file has the wrong length, and many tar programs will abort when they get to the invalid header/file. I've seen this happen when using smbclient/tar to back up a Win98 computer, and there's

Greetings, I am currently having a problem using smbclient (Samba v2.05a) running on Solaris 2.5.1 to restore a tar file from a tape drive onto a Win NT share. smbclient works successfully when using a tar file on disk, but is skipping the tar file (created by a third party) on the tape drive. The command used is as follows: smbclient //celeborn/test -U peter -T x /dev/rmt/0 The problem

> On Tue, 8 Feb 2005, Celeste Suliin Burris wrote: > > > Samba 3.0.11 won't compile on my Solaris 8 machine. It keeps getting > > compile errors in clitar [snip] I'm having this same problem. > Wonder why it is failing with #ifdef HAVE_REGEX_H ? That > macro is not defined anywhere. We don't even test for > regex.h anyways. Can you check > and see

smbclient can create GNU tar files with long file names, but cannot restore them. The included patch will rectify this. This patch is against 1.9.18.p4. -Rob -- Rob Riggs Devil's Thumb Entertainment Network Administrator Boulder, CO - (303) 938-1200 rob@DevilsThumb.COM http://www.DevilsThumb.COM/~rob "The notion of errors is

Using Sun Forte C (6.2 I think) on Solaris 2.9 UltraSparc Here's the errors: - Using FLAGS = -O -I./popt -Iinclude -I./include -I./ubiqx -I./smbwrapper -I/usr/local//include -I/usr/local//include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DLOGFILEBASE="/usr/local/samba/var" -DCONFIGFILE="/usr/local/samba/lib/smb.conf"

Solaris 9, Sun Forte C (6.2), latest CVS Here's the env ./configure --with-readline=/usr/local/ --with-quotas --with-utmp --with-acl-support --with-syslog --with-libsmbclient --without-winbind Using FLAGS = -O -I./popt -Iinclude -I./include -I./ubiqx -I./smbwrapper -I/usr/local//include -I/usr/local//include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64

Hi, I recently upgraded to 1.9.18p8, and noticed that smbtar no longer automatically includes system files. I can't seem to find a way to include the 'tarmode system' command in the smbtar shell script. If I add a -c "tarmode system" to the $SMBCLIENT command line at the end of the smbtar shell script, I get no tarred files at all. Can anybody help me with this?

I've set up the following and can open a home share for me (sylveg). I've created a group on W2KADS and on OURSAMBALINUX called oadmin and added me as a member in both. I created a samba share called o_drive (see smb.conf below) w/ the linux dir /home/o_drive and valid users = %D+oadmnin. The /home dir is: drwxr-xr-x 2 root root 4096 2004-09-03 15:16 ftp/ drwx------ 2 root root

I am running redhat 7.1 and would like to build the samba 2.2.0 rpms, but I rec'd an error. Is there something obvious I am doing wrong? I tried 2.0.7 just to see if that would work, but it failed with different issues. I know it says to submit a bug report, but I would assume I am at fault since I've never built an rpm from source before. Compiling client/clitar.c client/client.c: In