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.

Sign up for GitHub

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

Jump to bottom

Config and resume file created with executable permission #3979

Closed
0xcrypto opened this issue Jul 25, 2023 · 1 comment · Fixed by #4039
Closed

Config and resume file created with executable permission #3979

0xcrypto opened this issue Jul 25, 2023 · 1 comment · Fixed by #4039
Assignees
@dogancanbakir
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@0xcrypto
Copy link

Nuclei version: v2.9.9

Current Behavior:

Configuration file at ~/.config/nuclei/config.yaml and resume file at ~/.config/nuclei/resume-[unique-string].cfg are being created with permission set to 755

Expected Behavior:

Files should have permission set to 644

Steps To Reproduce:

Run nuclei to generate the config file. If you have old config file at ~/.config/nuclei/config.yaml, it should have the executable permission already. Check with:

stat -f %A ~/.config/nuclei/config.yaml  # or use ls -l ~/.config/nuclei/config.yaml

Anything else:

Related to #2180
@0xcrypto 0xcrypto added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Jul 25, 2023
@Mzack9999
Copy link
Member

Mzack9999 commented Jul 27, 2023 •
edited
Loading

Potential improvement: define standard permission set in utils/permissions and reuse everywhere

Depends on projectdiscovery/utils#225

@Mzack9999 Mzack9999 mentioned this issue Jul 27, 2023
Closed
@dogancanbakir dogancanbakir self-assigned this Jul 28, 2023
@dogancanbakir dogancanbakir mentioned this issue Aug 10, 2023
Merged
4 tasks
@dogancanbakir dogancanbakir linked a pull request Aug 10, 2023 that will close this issue
use default perms #4039
Merged
4 tasks
@dogancanbakir dogancanbakir added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dogancanbakir dogancanbakir

Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

use default perms projectdiscovery/nuclei
3 participants
@0xcrypto @Mzack9999 @dogancanbakir