Michael Reid
Michael Reid
SABnzbd 4.2.2 creates files with incorrect permissions (600 instead of 666) when using 7za to unpack
@Safihre, could this maybe be an upstream issue? @JustAndreww, can you indicate if this unpack function had the correct permissions in previous versions? It would be helpful in understanding if...
SABnzbd 4.2.2 creates files with incorrect permissions (600 instead of 666) when using 7za to unpack
@Safihre, I've done a few tests with the test nzb you provided. It normally downloads and extracts to `downloads/complete/test_zip`, with permissions like these: ``` $ ls -all total 4380 drwxrwxrwx+...
SABnzbd 4.2.2 creates files with incorrect permissions (600 instead of 666) when using 7za to unpack
In my opinion, if `7za` can't set permissions directly through arguments, it's more practical to use existing post-download methods. Introducing another workaround (like umask) doesn't seem necessary to me.
SABnzbd 4.2.2 creates files with incorrect permissions (600 instead of 666) when using 7za to unpack
@Safihre, based on my understanding, it seems that this issue is not exclusive to Synology but rather could potentially affect any Linux implementation. Would you concur with this assessment? If...
SABnzbd 4.2.2 creates files with incorrect permissions (600 instead of 666) when using 7za to unpack
From [Wikipedia on 7z](https://en.wikipedia.org/wiki/7z): > The 7z format does not store [filesystem permissions](https://en.wikipedia.org/wiki/Filesystem_permissions) (such as [UNIX](https://en.wikipedia.org/wiki/UNIX) owner/group permissions or [NTFS](https://en.wikipedia.org/wiki/NTFS) [ACLs](https://en.wikipedia.org/wiki/Access_control_list)), and hence can be inappropriate for backup/archival purposes.
SABnzbd 4.2.2 creates files with incorrect permissions (600 instead of 666) when using 7za to unpack
@BenjV, isn't that the same advice we already provide in the [Permission Management](https://github.com/SynoCommunity/spksrc/wiki/Permission-Management) wiki? If so, then there is nothing to address in the package or the upstream software. If...
SABnzbd 4.2.2 creates files with incorrect permissions (600 instead of 666) when using 7za to unpack
> Now, going back to `sabnzbd`, adding a simple `umask 0113` (for 0664) or `umask 0111` (for 0666) in the startup script may resolve the issue. Again, this may have...
@tearfur, we've noted users on Synology experiencing this issue since v4.0.2 in some cases. I am working with a user to help diagnose the issue (https://github.com/SynoCommunity/spksrc/issues/5999) and wanted to know...
Hey @mikedld, when you have a moment, I'd value your insights on this matter. It's been impacting certain Synology users since v4.0.2 in specific instances. If there's any specific diagnostic...
Hey @mikedld, I'm circling back on this matter. As mentioned earlier, a user demonstrated that this issue wasn't present in v4.0.2, which you assisted me in bringing to the Synology...