On Fri, Jan 20, 2017 at 5:40 AM, Marek Marczykowski-Górecki <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Fri, Jan 20, 2017 at 03:12:54AM -0500, Jean-Philippe Ouellet wrote: >> I would like to bring this list's attention to the availability of >> what I believe to be a good non-OpenPGP solution to the problem of >> cryptographically verifying code. >> >> The OpenBSD community has had very similar discussions internally >> several years ago, and they resulted in the implementation of a >> minimal non-OpenPGP signature creation & verification tool called >> signify, using the NaCl primitives [1]. It has been successfully used >> for package, release, and advisory signing for several years now, and >> has been audited both within and without the OpenBSD community. > > While the tool looks interesting, it solve somehow different problem > than we have. The tool is only about signing data, with asymmetric > crypto (so a key pair is needed). But in our case, we have problem with > both integrity protection and encryption
Indeed. I propose it mainly in the context of dom0 package verification, where we have the inconsistency of trusting pgp there while explicitly avoiding doing so elsewhere in Qubes, as discussed previously in this thread. Sorry for the ambiguity. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CABQWM_AVQnE7Q9z%2BWV6W7DMA6NPOXPOS2XrGWRQOenbgG%2BO%3DgA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
