search for: apostolou

...2020 6:06:34 PM CET, Kevin Korb via rsync wrote: > Permissions don't require super. Any place where permissions can't be > stored certainly can't handle xattrs either. So, I wouldn't expect > --fake-super to affect --perms at all. > > On 3/12/20 12:46 PM, Dimitrios Apostolou via rsync wrote: >> rsync --perms -M--fake-super src dst >> >> For me, this command means that rsync should save the original >> perms in the >> xattr, and leave the real file mode to the umask default. >> Currently it also >> modifies the real file mode...

...? On Thursday, March 12, 2020 6:26:18 PM CET, Kevin Korb via rsync wrote: > I would expect that the sending rsync would only send the perms provided > modified by the --chmod. I wouldn't expect the receiver to even know > the other permissions. > > On 3/12/20 1:23 PM, Dimitrios Apostolou via rsync wrote: >> Thank you for the feedback, I'm glad to see that different people see >> the issue >> differently. As a followup question, what would you expect this to do: >> >> rsync --perms --chmod g+rX -M--fake-super src dst >> >> I would expe...

I would expect that the sending rsync would only send the perms provided modified by the --chmod. I wouldn't expect the receiver to even know the other permissions. On 3/12/20 1:23 PM, Dimitrios Apostolou via rsync wrote: > Thank you for the feedback, I'm glad to see that different people see > the issue > differently. As a followup question, what would you expect this to do: > > rsync --perms --chmod g+rX -M--fake-super src dst > > I would expect it to store the original...

...even stored in the xattr. They don't need to be there but they may as well be. They don't take much space. The real question would be when rsync reads the file to restore it and the file perms are different than the ones in the xattr which set does it use? On 3/16/20 10:01 AM, Dimitrios Apostolou via rsync wrote: > Thanks. This is a bit counter-intuitive to me. So how would you tell > rsync to store the original permissions in the xattr, but do not touch > the real file mode? > > On Thursday, March 12, 2020 6:26:18 PM CET, Kevin Korb via rsync wrote: >> I would expect...

On 2020-03-17 00:03:03 [+0100], Dimitrios Apostolou via rsync wrote: > On Thursday, February 20, 2020 10:34:53 PM CET, Sebastian Andrzej Siewior > via rsync wrote: > > > > I'm still not sure if rsync requires a cryptographic hash _or_ if a > > strong hash like xxHash64 would be just fine for the job. > > I'm f...

Hi All, I cannot get my Samba server 2.2.8 working with winbind correctly on Solaris 8. I intend to use this to transparently authenticate squid 2.5stable2. I compiled samba using gcc 2.95.3. configure options were ./configure --with-winbind-auth-challenge --with-winbind --with-pam root# ./wbinfo -t Secret is good root# ./wbinfo -u 0xc0000022 The same thing with wbinfo -g. getent group

Hello list! Combining -M--fake-super with --chmod ends up changing the permissions stored in the fake-super xattrs. I.e. the permissions stored in the xattr, are affected by --chmod. The desirable behaviour for me would be for --chmod to modify the real permissions of the destination files. The use case is writing a backup as a non-root user, having it readable by the group (g+rX), while also

rsync --perms -M--fake-super src dst For me, this command means that rsync should save the original perms in the xattr, and leave the real file mode to the umask default. Currently it also modifies the real file mode, and there is no way to store something different in the xattr. According to an old bug report that I found, more people would like --fake-super to be a complete attribute

When I try it the chmod works on both the real permissions and the permissions in the xatttr. Maybe the behavior has changed since whatever version you have (3.1.3 here) but this probably wouldn't help you either. On 12/8/19 7:56 PM, Dimitrios Apostolou via rsync wrote: > Hello list! > > Combining -M--fake-super with --chmod ends up changing the permissions > stored in the fake-super xattrs. I.e. the permissions stored in the > xattr, are > affected by --chmod. > > The desirable behaviour for me would be for --chmod to mo...

Permissions don't require super. Any place where permissions can't be stored certainly can't handle xattrs either. So, I wouldn't expect --fake-super to affect --perms at all. On 3/12/20 12:46 PM, Dimitrios Apostolou via rsync wrote: > rsync --perms -M--fake-super src dst > > For me, this command means that rsync should save the original perms in the > xattr, and leave the real file mode to the umask default. Currently it also > modifies the real file mode, and there is no way to store something...

https://bugzilla.samba.org/show_bug.cgi?id=7112 Summary: --fake-super should use default permissions for real files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org

On 2020-02-20 20:06:39 [+0100], Markus Ueberall wrote: > On 2020-02-09 23:19, Sebastian Andrzej Siewior wrote: > > [...] > > My primar motivation to use SHA1 for checksumming (by default) instead > > of MD5 is not the additional security bits but performance. On a decent > > x86 box the SHA1 performance is almost the same as MD5's but with > > acceleration it

...Fix pixman/Makefile.am to work with Solaris make Andr? Tupinamb? (1): Add SSE2 implementations of many compositing operations. Antoine Azar (1): Optimize operators based on source or dest opacity. Dimitrios Apostolou (1): Fix compilation on SGI Frederic Plourde (1): Add CopyAreammx fast path for argb32 SRC xrgb32 and abgr32 SRC xbgr32 Julien Cristau (3): Remove prototype for nonexistent pixman_image_set_filte...