similar to: [PATCH v2 1/2] xattrs: Skip security.evm extended attribute

https://bugzilla.samba.org/show_bug.cgi?id=8475 Summary: memory leak around free_xattr() and rsync_xal_free(), with -aX, 200 bytes per file and per directory Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=13113 Bug ID: 13113 Summary: receive_xattr heap overflow when prepending RSYNC_PREFIX Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned

Destroy ACL-s on destination when no ACL-s differens between source and destination. Bug is somehow related with function send_file_name() called with negative file descriptor f. There is no such bug in 2.6.9 version, but there options "-X -A --deleted" can't be used (we have "Internal error: wrong write used in receiver."). If I fix this, avoid calling send_acl() &

On Thu, 2022-12-01 at 11:41 +0100, Roberto Sassu wrote: > From: Roberto Sassu <roberto.sassu at huawei.com> > > Currently, evm_inode_init_security() processes a single LSM xattr from > the array passed by security_inode_init_security(), and calculates the > HMAC on it and other inode metadata. > > Given that initxattrs() callbacks, called by >

I recently found a bug in the xattrs patch, where it would apply the wrong xattrs to some files in a transfer. While looking at the code, I think I found another one (it sure looks wrong, but I haven't figured out how to demonstrate it yet). Anyway, here's the patch: The first hunk fixes the apparent bug. The second hunk fixes the demonstratable bug. I haven't (yet) looked to see

On Thu, Dec 1, 2022 at 5:42?AM Roberto Sassu <roberto.sassu at huaweicloud.com> wrote: > > From: Roberto Sassu <roberto.sassu at huawei.com> > > One of the major goals of LSM stacking is to run multiple LSMs side by side > without interfering with each other. The ultimate decision will depend on > individual LSM decision. > > Several changes need to be made to

From: Roberto Sassu <roberto.sassu at huawei.com> One of the major goals of LSM stacking is to run multiple LSMs side by side without interfering with each other. The ultimate decision will depend on individual LSM decision. Several changes need to be made to the LSM infrastructure to be able to support that. This patch set tackles one of them: gives to each LSM the ability to specify one

I've found a(nother) bug with the xattr code: kiwiw:~/x terpstra$ uname -a Darwin kiwiw.lan 8.10.0 Darwin Kernel Version 8.10.0: Wed May 23 16:50:59 PDT 2007; root:xnu-792.21.3~1/RELEASE_PPC Power Macintosh powerpc kiwiw:~/x terpstra$ echo test > bar kiwiw:~/x terpstra$ xattr --set broken demo bar kiwiw:~/x terpstra$ chmod 0444 bar kiwiw:~/x terpstra$ rsync-3.0 -aHAXSx bar

https://bugzilla.samba.org/show_bug.cgi?id=13112 Bug ID: 13112 Summary: receive_xattr heap overread with non null terminated name and xattr filter Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

From: Roberto Sassu <roberto.sassu at huawei.com> One of the major goals of LSM stacking is to run multiple LSMs side by side without interfering with each other. The ultimate decision will depend on individual LSM decision. Several changes need to be made to the LSM infrastructure to be able to support that. This patch set tackles one of them: gives to each LSM the ability to specify one

https://bugzilla.samba.org/show_bug.cgi?id=8665 Summary: Crash in free_xattr(), from recv_generator() Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chris at onthe.net.au

After creating the initial LSM security extended attribute, call evm_inode_post_init_security() to create the ''security.evm'' extended attribute. Signed-off-by: Mimi Zohar <zohar@us.ibm.com> --- fs/btrfs/xattr.c | 39 +++++++++++++++++++++++++++++---------- 1 files changed, 29 insertions(+), 10 deletions(-) diff --git a/fs/btrfs/xattr.c b/fs/btrfs/xattr.c index

After creating the initial LSM security extended attribute, call evm_inode_post_init_security() to create the ''security.evm'' extended attribute. Signed-off-by: Mimi Zohar <zohar@us.ibm.com> --- fs/btrfs/xattr.c | 39 +++++++++++++++++++++++++++++---------- 1 files changed, 29 insertions(+), 10 deletions(-) diff --git a/fs/btrfs/xattr.c b/fs/btrfs/xattr.c index

Stefan Berger wrote: > The security.evm extended attribute is fully owned by the Linux kernel > and cannot be directly written from userspace. Therefore, we can always > skip it. > --- (see below "...")... Please put this on a switch or option. The security.evm field seems only special on Mandatory Access systems (from https://lwn.net/Articles/449719/), and seems

Yep Zane -----Original Message----- From: rsync-bounces+zane_brady=trimble.com@lists.samba.org [mailto:rsync-bounces+zane_brady=trimble.com@lists.samba.org] On Behalf Of rsync-request@lists.samba.org Sent: Friday, February 01, 2008 7:01 AM To: rsync@lists.samba.org Subject: rsync Digest, Vol 62, Issue 1 Send rsync mailing list submissions to rsync@lists.samba.org To subscribe or unsubscribe

On 01/06/2017 12:27 AM, L. A. Walsh wrote: > Stefan Berger wrote: >> The security.evm extended attribute is fully owned by the Linux kernel >> and cannot be directly written from userspace. Therefore, we can always >> skip it. > --- (see below "...")... > > Please put this on a switch or option. > > The security.evm field seems only special on

Hi, I''ve just started to do some work using ActiveLDAP and Rails. I''ve managed to get some basic login code that works to authenticate users, but I would like to be able to maintain that connection for the User Model so that the ACL''s in LDAP for each user will be used correctly as the various controller queries are made. I haven''t quite sorted out how to

Thanks Wayne and everybody, This is a huge boost to have a modern rsync for OSX. We're all grateful. Rob D PS I did notice that we lost the bsd flags test in 3.0. It was ok in pre10.... thanks again bbouncer Verifying: basic-permissions ... ok Verifying: timestamps ... Sub-test: modification time ... ok ok Verifying: symlinks ... ok Verifying:

Hi Folks Can anyone help me with the following error - is it serious; is the file transferred; are the other files transferred? [morgan@morgansmachine ~]$ rsync -a -X -A -z -v /home/morgan/Documents 192.168.1.30:/home/morgan/Documents morgan@192.168.1.30's password: building file list ... done rsync: rsync_xal_set:

Hello, I found that using rsync on OS X can give some problems when it comes to Extended Attributes (-X flag). The server I use has Ubuntu with the filesystem XFS and I am trying to backup a OS X system to it. The problem is as far as I understand it that Linux Kernel has a liming on 64k f?r Extended Attributes and OS X don?t have this limit. Some error output. rsync: rsync_xal_set: