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

[ENHANCEMENT] Streamlining excluded directories #3

Open
Hasimir opened this issue Apr 6, 2016 · 1 comment
Open

[ENHANCEMENT] Streamlining excluded directories #3

Hasimir opened this issue Apr 6, 2016 · 1 comment
Assignees

Comments

@Hasimir
Copy link

Hasimir commented Apr 6, 2016

So it turns out I'm a bit slack and meant to do this last week, oops.

Excluding all hidden files or directories has the significan drawback of preventing gpgdir being used on things like IMAP mail folders, Maildir contents and anything in .config/ (including hexchat and xchat IRC logs) or .znc/ config and logs. No doubt everyone can come up with other examples of things they'd like to be able to compress encrypt and archive.

Nevertheless, the default behaviour of automatically excluding certain essential configuration files and directories needs to be protected. Principally the GPG home directory (traditionally ~/.gnupg/ on POSIX compliant systems) and the relevant shell rc files for the user.

Updating gpgdir to use the user's environment to determine which shell they use and exclude the relevant default rc or configuration files would be ideal, but a fallback of excluding the most common files (e.g. .bashrc, .bash_profile, .tcshrc, .cshrc, etc.). As for GPG's home directory, this should be determined with:

gpgconf --list-dirs

Normally the homedir value is the final line of the output of that command. The fallback should be the default of $HOME/.gnupg/

Note that systems which only use GPG Classic (i.e. GPG 1.4.x) will not have the gpgconf command. Some output may differ between GPG Stable (i.e. GPG 2.0.x) and GPG Modern (i.e. GPG 2.1.x). I've been referring to the output from GPG 2.1.11 here.

@mrash mrash self-assigned this Apr 10, 2016
@mrash
Copy link
Owner

mrash commented Apr 10, 2016

Thanks for opening this issue and for the detailed write up.

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