On Mon, 15 Feb 2016 at 13:19:55 +0100, Lachlan Gunn wrote:
>> The gzipped tarball format looks really overkill. How about an OpenPGP
>> keyring (possibly armored)? No need for caff here, gpg(1) can do this
>> alone:
>>
>> gpg --export >/tmp/keyring.gpg
>>
>> (you could also add ‘--export-optio
> The gzipped tarball format looks really overkill. How about an OpenPGP
> keyring (possibly armored)? No need for caff here, gpg(1) can do this
> alone:
>
> gpg --export >/tmp/keyring.gpg
>
> (you could also add ‘--export-options export-minimal’)
My reason for suggesting a tarball is that
On Fri, 12 Feb 2016 at 23:08:12 +0100, Guilhem Moulin wrote:
> How about an option ‘--signed-key-file’ (and ‘--lsigned-key-file’ for
> local sigs)? Caff would export all signed keys in the specified file.
By the way, this is essentially
gpg --homedir ~/.caff/gnupghome --export
--
Guilhem.
On Fri, 12 Feb 2016 at 15:34:27 +0100, Lachlan Gunn wrote:
> I am interested in using CAFF on an airgapped machine, which at the
> moment is somewhat non-obvious. If I can find the time, I would like to
> develop some kind of CSR-like workflow, would others be interested in this?
> The kind of wo
Package: signing-party
Version: 2.2-1
Severity: wishlist
Hello,
I am interested in using CAFF on an airgapped machine, which at the
moment is somewhat non-obvious. If I can find the time, I would like to
develop some kind of CSR-like workflow, would others be interested in this?
The kind of work
5 matches
Mail list logo
