similar to: make errors, rsync 2.6.9 with acls patch

No material changes are made. --- Makefile | 10 +- convert.c => convert/convert.c | 803 +--------------------------------------- convert/convert.h | 76 ++++ convert/ext2.c | 791 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 873 insertions(+), 807 deletions(-) rename convert.c => convert/convert.c (74%) create mode

Look at the acl(5) man page and you'll see that the ACCESS CHECK ALGORITH starts: IF the effective user ID of the process matches the user ID of the file object owner ... ELSE IF the effective user ID of the process matches the qualifier of any entry of type ACL_USER, THEN IF the matching ACL_USER entry and the ACL_MASK entry contain the requested permissions, access is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 #$ setfacl -m u:mf:r bla #$ getfacl bla # file: bla # owner: root # group: root user::rw- user:mf:r-- group::r-- mask::r-- other::r-- It is readable by mf like intended. #$ chmod go-rwx bla #$ getfacl bla # file: bla # owner: root # group: root user::rw- user:mf:r-- #effective:--- group::r-- #effective:--- mask::--- other::--- It is not

https://bugzilla.samba.org/show_bug.cgi?id=14076 Bug ID: 14076 Summary: 3.13 - lib/sysacls.h:118:13: error: array type has incomplete element type 'struct acl' Product: rsync Version: 3.1.3 Hardware: x64 OS: All Status: NEW Severity: normal Priority: P5

Hi all, I have a setup like this. Pls let me know if it's possible or not. SAMBA + Local LDAP ---> SASLAUTHD --> Global LDAP Desc: I'd like to do Samba authentication to LDAP, passthrough to another LDAP using SASL. The current situation is: SSH authentication from LDAP user to that Samba box works. However, smb authentication doesn't work (yet). This is what's shown in

Hi, I've implemented an LDAPv2 server with samba support but find that smbpasswd does not work as expected. I am using berkeley db-4.1.25_p1, openldap-2.1.26, and samba-3.0.2a. Anybody have any clue why I get the following error when attempting to add samba support for a user (specifically a DB_KEYEXIST error). I get the following output (excerpt) from smbpasswd: ldapsam_add_sam_account:

I have really strange problem. I create a subdirectory in s directory with ALCs and default ACLs. The new subdirectory geins rwx permitions for ACL_GROUP_OBJ (Full Access for CREATOR GROUP in NT security dialog box). Any combination of parameters like (force) create mask, security mask etc. doesn't help as well as inherit acls or inherit permitions. I tried versions 2.2.7b, 2.2.8 and 2.2.8a

I'm trying to get an old FreeBSD 4.11 server to talk to a newer FreeBSD 7 server that is running rsync 3.0.4 but I am running into an error with extended file attributes: Basic steps: Applied the fileflags patch per the instructions: patch -p1 <patches/fileflags.diff ./prepare-source Ran the following configure line: ./configure --with-included-popt --disable-iconv

A bit of a minor off-topic issue, but on the off-chance that someone understands how ACLs work ... I've been trying to see if using default ACLs would help with the following issue: I have a third party application that is running as a non-root user ('user-a') and creating log files with mode 0600 (read/write only to the owner) in a log directory I have another application that

Hello trusty rsync list, I'm excited about --fake-super as it will replace too much work with none at all. I have gotten it to work under linux and I have a fair grasp with what is happening there. I have a problem, though, and that is, in the long term, I'll need to archive my Linux systems not to a Linux box, but to a Solaris 10 box. I understand that Solaris does have extended

meminfo.c32: Remove unneeded 'x' characters from output. Commit 5932f124 ("com32: change '%llx' to use PRIx64", committed on 2015-01-06) adds 1 "x" character per each of the 3 hex output columns for the 'INT 15h e820' value(s) in meminfo.c32. These 3 extra "x" characters are not really needed in this context, and they can make the resulting

Maybe I'm doing somthing really stupid, but while copying some windows share onto a samba server, on some random subdirectory robocopy says ERROR 87 (0x00000057) Copying NTFS Security to Destination Directory... The samba logfile has lots of these lines. modules/vfs_posixacl.c:349(smb_acl_to_posix) smb_acl_to_posix: ACL is invalid for set (Das Argument ist ung?ltig) The strange thing is

This patch adds all the missing commonly used UNIX attributes: st_dev, st_ino, st_nlink, st_rdev, st_blocks, st_blksize, st_ctime. In addition it extends st_atime and st_mtime to 64bits, and adds nanosecond resolution to all three timestamps. This is implemented as an extension to the ATTR message. This patch alone is sufficient for SSHFS to be able to use these attributes. The following two

Trying to get ACLs working, very basic setup: Virtual users are put into different acl_group via passdb. > u:{PLAIN}B::::::userdb_acl_groups=g The global acl file restricts what they can do. > * group-override=g > * group=g lr Shouldn't this mean, that the group rights override the user rights? The effect that I see though is, that the user "u" then may not do

Hi list, I'm getting stuck at the replication part for my BDC. Could someone familiar with OpenLDAP replication shed some light? I'm sure that password is correct Thanks for taking a look at! 1. slapd.conf (master) # $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.23.2.8 2003/05/24 23:19:14 kurt Exp $ # # See slapd.conf(5) for details on configuration options. # # include

Hi there! I can't get ACL working for master users. Login as master user works fine though, and I am able to access any mailbox using the auth_master_user_separator "*", tested e.g. via Python's imaplib: import imaplib imap = imaplib.IMAP4_SSL('imap.example.com') imap.login('foo at example.com*admin-acldemo', '**********') ('OK', [b'Logged

Hi there! I can't get ACL working for master users. Login as master user works fine though, and I am able to access any mailbox using the auth_master_user_separator "*", tested e.g. via Python's imaplib: >>> import imaplib >>> imap = imaplib.IMAP4_SSL('imap.example.com') >>> imap.login('foo at example.com*admin-acldemo',

On an i686 with glibc 2.5 installed I'm not able to compile rsync 3.0.2 and later. rsync 3.0.0 was no problem, this compiled. Also on an x86_64 with glibc 2.7 installed rsync compiled. Here is a script of the failing comilation: Script started on Sat May 10 07:33:39 2008 teddy@mail /usr/src/rsync-HEAD-20080508-0612GMT $ mkdir build teddy@mail /usr/src/rsync-HEAD-20080508-0612GMT $ cd build

Hello. Use <inttypes.h> PRIx64 instead of llx to get rid of gcc warning format ?%llx? expects type ?long long unsigned int?, but argument 2 has type ?uint64_t? -- MartinS diff --git a/com32/gpllib/acpi/xsdt.c b/com32/gpllib/acpi/xsdt.c index 208abc6..228b6c3 100644 --- a/com32/gpllib/acpi/xsdt.c +++ b/com32/gpllib/acpi/xsdt.c @@ -63,7 +63,7 @@ int parse_xsdt(s_acpi * acpi) /*

Hi folks. New to both dovecot and openldap. Trying to set up virtual domains using the wanderingbarque howto: http://www.wanderingbarque.com/mailserver.html Platform is RH enterprise 3. Only difference is I'm trying to use phamm instead of jamm: http://phamm.rhx.it/ dovecot doesn't seem to want to play nice with my openldap; everything else (postfix, etc) seems to work alright.