On Fri, Jan 18, 2013 at 06:04:03PM -0700, s. keeling wrote: > Incoming from Chris Bannister: > > On Thu, Jan 10, 2013 at 11:09:48AM -0700, Robert Holtzman wrote: > > > On Thu, Jan 10, 2013 at 07:33:16AM -0600, Dale A. Raby wrote: > > > > > > > set pgp_replyencrypt=yes > > > > set pgp_timeout=1800 > > > > set pgp_good_sign="^gpg: Good signature from" > > > > > > I have none of this in my .muttrc and have pgp capability. P shows the > > > pgp menu. This in mutt 1.5.20-9+squeeze2. > > > > root@tal:~# ls -al /etc/Muttrc.d/ > > total 40 > > drwxr-xr-x 2 root root 4096 Oct 2 18:56 . > > drwxr-xr-x 109 root root 12288 Jan 11 18:59 .. > > I'm surprised you'd put that in /etc/Muttrc.d; it's all world- > readable. It doesn't take advantage of today's encrypted $HOME > partitions. All of my mutt config is in ~/mutt, including my muttrc. > I have a ~/.muttrc symlink that points to it.
Why would generic gpg commands being world-readable be an issue? Those files are part of the mutt package on Debian/Ubuntu: $ dpkg-query -S /etc/Muttrc.d/gpg.rc mutt: /etc/Muttrc.d/gpg.rc There's nothing to be gained by reading them. [ Btw, mutt will parse ~/.mutt/muttrc if ~/.muttrc doesn't exist. If you dot-prefix your ~/mutt, then you could axe the need for the symlink. ] -- Brandon Sandrowicz