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

Re-assign permissions when adding users #161

Closed
nenebale opened this issue Feb 11, 2016 · 3 comments
Closed

Re-assign permissions when adding users #161

nenebale opened this issue Feb 11, 2016 · 3 comments
Labels

Comments

@nenebale
Copy link

@nenebale nenebale commented Feb 11, 2016

Hi everyone!

First, I wanted to say thanks for this awesome piece of software! I am planning to use it as main storage of passwords inside our company for 15+ people.

I wanted to know if it was possible to have a "reassign permission" functionality for all passwords in a folder. For now, every time permissions change I have to open every password in the edit view and close it to re-encrypt it for the new keys.

I am not really familiar with C++ code but I would be glad to help achieving this.

Thanks a lot!
Lionel

@annejan
Copy link
Member

@annejan annejan commented Feb 11, 2016

Yes, this issue has high-priority for me, since it is a very seriously lacking feature
To do it in pass mode is easy but to do it for non-pass systems is harder.

Related: #150

@nenebale
Copy link
Author

@nenebale nenebale commented Feb 11, 2016

Then why not implementing it for pass first and only show the notice in the user window to non-pass users?

I see you talked about a button in #150 - in my opinion, this shouldn't require any user-interaction as it is an expected behaviour and not something one might be surprised of if it happened automatically.

@annejan
Copy link
Member

@annejan annejan commented Feb 11, 2016

I have a test for that planned this weekend (pass first and non-pass later).

There shouldn't be a button imo, and it should always happen.

The only thing discussed is a configuration option to disable the (correct) behaviour and return to the lazy (current) behaviour.
On large trees re-coding can take an immense amount of time.

@annejan annejan removed the duplicate label Mar 6, 2016
annejan added a commit that referenced this issue Jun 10, 2016
@annejan annejan closed this in 97573b5 Jun 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants