Shedi
I suggest upgrading rsync to a modern hash. For example, Blake3.
On Tue, Mar 12, 2024, 8:00?a.m. <rsync-request at lists.samba.org> wrote:
> Send rsync mailing list submissions to
> rsync at lists.samba.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.samba.org/mailman/listinfo/rsync
> or, via email, send a message with subject or body 'help' to
> rsync-request at lists.samba.org
>
> You can reach the person managing the list at
> rsync-owner at lists.samba.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of rsync digest..."
> To unsubscribe or change options:
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>
> ---------------------------------------
> Today's Topics:
>
> 1. Re: rsync segfaults when openssl fips is enabled
> (Shreenidhi Shedi)
>
>
>
> ---------- Forwarded message ----------
> From: Shreenidhi Shedi <shreenidhi.shedi at broadcom.com>
> To: rsync at lists.samba.org
> Cc: Tapas Kundu <tapas.kundu at broadcom.com>
> Bcc:
> Date: Tue, 12 Mar 2024 15:05:42 +0530
> Subject: Re: rsync segfaults when openssl fips is enabled
> Hi All,
>
> Any inputs on this issue?
>
> --
> Shedi
>
>
> On Wed, Feb 21, 2024 at 5:12?PM Shreenidhi Shedi <
> shreenidhi.shedi at broadcom.com> wrote:
>
>> Hi All,
>>
>> Copying the content from the GH issue as is.
>> Need your inputs on the same.
>> FWIW, the coredump files generated in linux have xattr values which are
>
>> 32 bytes.
>>
>> https://github.com/WayneD/rsync/issues/569
>>
>> Hi All,
>>
>> System details:
>>
>> root at ph3dev [ ~ ]# rsync --version
>> rsync version 3.2.4 protocol version 31
>> Capabilities:
>> 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
>> socketpairs, symlinks, symtimes, hardlinks, hardlink-specials,
>> hardlink-symlinks, IPv6, atimes, batchfiles, inplace, append, no
ACLs,
>> xattrs, optional protect-args, iconv, prealloc, stop-at, no
crtimesOptimizations:
>> SIMD-roll, no asm-roll, openssl-crypto, no asm-MD5
>> Checksum list:
>> xxh128 xxh3 xxh64 (xxhash) md5 md4 none
>> Compress list:
>> zstd lz4 zlibx zlib none
>>
>> OS:
>> Photon OS 3.0 with openssl fips enabled
>>
>> I'm using rsync like below:
>>
>> rsync -arXHpvxog <src> <dest>
>>
>> While doing so, if any file in src or dest location has a xattr value
which is more than 32 bytes long, rsync segfaults.
>>
>> root at ph3dev [ ~ ]# getfattr -d -m '' -- /opt/x
>> getfattr: Removing leading '/' from absolute path names
>> # file: opt/x
>> user.bla1="1234567890abcdef1234567890abcdef1" --------> 33
bytes long
>>
>> After examining the coredump file, this happens at;
>>
>> rsync/xattrs.c
>> Line 277 in 2f9b963
>>
>> sum_init(xattr_sum_nni, checksum_seed);
>>
>> Here md5 is used by default and md5 usage is prohibited in fips mode.
>>
>> Is there any way to workaround this problem? Also, why not use xxhash
for this operation like it's used by default during --checksum option.
>>
>> --
>> Shedi
>>
> _______________________________________
> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>
> rsync mailing list
> rsync at lists.samba.org
> https://lists.samba.org/mailman/listinfo/rsync
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.samba.org/pipermail/rsync/attachments/20240312/7515d6b0/attachment.htm>