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

Attempt recursive chmod +w before encrypting #2

Open
JElchison opened this issue Apr 16, 2018 · 0 comments
Open

Attempt recursive chmod +w before encrypting #2

JElchison opened this issue Apr 16, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@JElchison
Copy link
Owner

Right now, lockbox will skip encrypting any files that aren't writable, even if they're owned by the current user. Attempting recursive chmod +w before encrypting would maximize the files that could be encrypted.

However, this may not be what the user desires. Consider an argument to opt-in or opt-out? Or maybe an interactive question?
@JElchison JElchison added the enhancement New feature or request label Apr 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JElchison