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

Add a note or warning to a rule to be printed to the user #68

Closed
sunhasgothishaton opened this issue Dec 10, 2020 · 3 comments
Closed

Comments

@sunhasgothishaton
Copy link

Sometimes during a migration, a command has to be run e.g. to reset a system running

I just tried to manually migrate gnupg from ~/.gnupg to ~/.local/share/gnupg and for one of my tests, I had to run "gpgconf --kill gpg-agent" before I was able to create a private key. They key agent was still looking in the old directory.

Does antidot support the running of commands during migration?

@doron-cohen
Copy link
Owner

Not right now. I am parted about running commands. On one hand it will make this tool a lot powerful and I am sure there are other use cases as well. On the other hand, it will introduce security issues and will make this tool more like a script runner. I did think about adding the option to include a warning or a note that will be printed for a specific rule. That will make it easy to let the user know this command needs to be run after the migration.

@sunhasgothishaton
Copy link
Author

I agree with you about it being a security issue, good call on that.

I like the idea to inform the user to run the commands after migration, it keeps the user in control too.

@jedahan
Copy link
Contributor

jedahan commented Dec 10, 2020

Very much like the current simplicity of the application. Adding friendly directions for the user is nice though.

@doron-cohen doron-cohen changed the title run a command during migration Add a note or warning to a rule to be printed to the user Dec 10, 2020
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

3 participants