eugenesan

And it seems like Rar deals with the problem when packing and not when extracting: $ rar x stdin.rar5 $ $ ll stdin ---------- 1 username username 2 Feb 5 15:40 stdin

And it seems like Rar deals with the problem when packing and not when extracting: $ rar x stdin.rar5 $ $ ll stdin ---------- 1 eugenesan eugenesan 2 Feb 5 15:40 stdin

Indeed. Seems like Rar 6.x behaves more "Unixy" ;-) $ rar l stdin.rar5 RAR 6.23 Copyright (c) 1993-2023 Alexander Roshal 1 Aug 2023 Trial version Type 'rar -?' for help Archive: stdin.rar5 Details: RAR 5 Attributes Size Date Time Name ----------- --------- ---------- ----- ---- ---------- 2 2024-02-05 15:40 stdin ----------- --------- ---------- ----- ---- 2 1

This what I see when testing with RAR 6.23 on Linux $ cat 1.txt | rar -si a 2.rar $ rar l 2.rar RAR 6.23 Copyright (c) 1993-2023 Alexander Roshal 1 Aug 2023 Trial version Type 'rar -?' for help Archive: 2.rar Details: RAR 5 Attributes Size Date Time Name ----------- --------- ---------- ----- ---- -rw-r--r-- 4096 2024-02-05 15:13 stdin ----------- --------- ---------- ----- ---- 4096 1 $ rar x 2.rar $ ll stdin -rw-r--r-- 1 username username 4096 Feb 5 15:13 stdin

I see. Rar probably displays default permissions for the host system when attributes are empty and sets default permissions on extraction. I guess 7zip should do the same.

On my system with command line you've provided for RAR, it behaves as I showed earlier. Maybe different versions of RAR behave differently? RAR 6.23 Copyright (c) 1993-2023 Alexander Roshal 1 Aug 2023 Trial version Type 'rar -?' for help Archive: a.rar Details: RAR 5 Attributes Size Date Time Name ----------- --------- ---------- ----- ---- -rw-r--r-- 4096 2024-02-05 13:22 1.txt ----------- --------- ---------- ----- ---- 4096 1 -rw-r--r-- 1 username username 4096 Feb 5 13:22 1.txt

Mimicking p7zip behavior sounds good, especially since majority of recent Linux distributions switched to 7zip 23.01 from p7zip 16.02. Either approach will work as long as resulting files/dirs have sane permisions (644/755). Choose the the method that is easier to implement. FYI: This is the script that is packaged with 7zip to mimics p7zip's behavior: https://salsa.debian.org/debian/7zip/-/blob/master/debian/scripts/p7zip.sh

777 is the default for Windows oriented tools this is why Zip and Rar on Windows behave this way. On Unix 777 makes the file executable and readable/writable by everybody which is not ideal. Just tested Rar with -si, and it stores files in archive as 644 so ideally 7z -si should do the same. Also 7z does the same when storing regular files so it is consistent with existing behavior.