From: aranea@aixah.de (Luis Ressel)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] gpg policy
Date: Wed, 28 Dec 2016 17:48:56 +0100 [thread overview]
Message-ID: <20161228174856.6ff883c5@gentp.lnet> (raw)
In-Reply-To: <e44ac0c6-05b1-18e6-86e1-d82729bb4ffd@gmail.com>
On Wed, 28 Dec 2016 17:40:39 +0100
Dominick Grift via refpolicy <refpolicy@oss.tresys.com> 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
prev parent reply other threads:[~2016-12-28 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 16:32 [refpolicy] gpg policy Luis Ressel
2016-12-28 16:40 ` Dominick Grift
2016-12-28 16:48 ` Luis Ressel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161228174856.6ff883c5@gentp.lnet \
--to=aranea@aixah.de \
--cc=refpolicy@oss.tresys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.