From: aranea@aixah.de (Luis Ressel) Date: Wed, 28 Dec 2016 17:48:56 +0100 Subject: [refpolicy] gpg policy In-Reply-To: References: <20161228173233.6aa17b2d@gentp.lnet> Message-ID: <20161228174856.6ff883c5@gentp.lnet> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com On Wed, 28 Dec 2016 17:40:39 +0100 Dominick Grift via refpolicy wrote: > I am a bit confused about what you consider gpg_secret_t data. > > gpg creates/maintains the private key. This is the thing I would want > to protect. Only gpg itself ever needs access to that file. Thus no > confined application should ever have any access to this private key I guess my wording wasn't precise enough. By "gpg-related program", I mean gpg, gpg-agent, dirmngr and scdaemon. I don't want to expose any data in ~/.gnupg to third-party programs. I'm just trying to segregate the different components of gpg (the tools mentioned above) from each other; for example, as you remarked in your previous mail, dirmngr shouldn't have access to private key material. Regards, Luis -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20161228/6562cfde/attachment.bin