We have been notified about a potential issue with gpg. When de/en-crypting files,
it will always automatically place them world-readable by default. Examples:

de-crypting

% gpg sikrit.gpg
% ll sikrit*

  -rw-r--r-- 1 gp users  12 Sep 17 09:41 sikrit
  -rw------- 1 gp users 480 Sep 17 09:40 sikrit.gpg

en-crypting

% chmod go= sikrit
% ll sikrit

-rw------- 1 gp users 12 Sep 17 09:38 sikrit

% gpg -e -r foo sikrit
% wipe sikrit
% ll sikrit.gpg

  -rw-r--r-- 1 gp users 480 Sep 17 09:40 sikrit.gpg

One usually expects that files which get encrypted also contain sensitive content.
Otherwise encryption would not have made that much sense anyway, right? Thus when
de-crypting, you therefore possibly also do not want everybody (ie world-readable)
to be able to read the file's (sensitive) content again in the end.

Feedback is welcome.

(Yes, we are aware of umask(1p), but still...)