Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New directory is created with hardcoded permission #1

Closed
am0z opened this issue Nov 1, 2021 · 2 comments
Closed

New directory is created with hardcoded permission #1

am0z opened this issue Nov 1, 2021 · 2 comments

Comments

@am0z
Copy link

am0z commented Nov 1, 2021

atool/atool

Line 1131 in f37b2c1

if (!mkdir($dir, 0700)) {

Quick backstory. I have this problem that I wrote to the author but his email bounces.

Anyway I have a shared volume that several users use to aunpack and copy files. Since atool creates new directories with 700 hardcoded it ignores specific filesystem permission I set using setfact. I'm not sure if it's a bug or a feature.

I don't know why I'm creating this ticket here. Archlinux still uses upstream from nongnu.org. Have no idea how to get this potential fix there.

Cheers!

@z3ntu
Copy link
Owner

z3ntu commented Nov 8, 2021

Hi, can you try if this works for you? a967924

Tbh I'm also bummed that original upstream is dead, so I'm maintaining this "fork" for myself, mostly for the zstd support.

@am0z
Copy link
Author

am0z commented Nov 8, 2021

Yep, this was easy to test. Can confirm it fixes the issue I was having.

@z3ntu z3ntu closed this as completed in a967924 Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants