On Mon, 23 Jan 2017 13:34, pe...@digitalbrains.com said:
> (FWIW, I don't think you can currently do either. Possibly you can
> change the s2k-count via the agent protocol, but that might not pertain
No, that is not possible. Right now the agent always uses AES and S2K
paremeters which require o
On 23/01/17 12:34, Peter Lebbing wrote:
> On 23/01/17 12:54, John Lane wrote:
>> Ok, so - if I understand you correctly - when I *export* the secret key
>> I can choose which algorithms are applied to the exported copy ?
>
> No, I meant that the bug report (turned feature request) is about
> choos
On 23/01/17 12:54, John Lane wrote:
> Ok, so - if I understand you correctly - when I *export* the secret key
> I can choose which algorithms are applied to the exported copy ?
No, I meant that the bug report (turned feature request) is about
choosing the options for export. As long as the bug is
On 23/01/17 11:01, John Lane wrote:
> I've been reading about symmetric encryption of the private key.
>
> When I tried to experiment with the `--s2k` options, attempting to
> change the passphrase on my key, I found that they were ignored.
GnuPG 2.1 handles the private key in a completely differ
On 23/01/17 11:22, Peter Lebbing wrote:
> It's close to what you're talking about, but not exactly. That is
> specifically about *exporting* an OpenPGP secret key, not how it is
> *stored* in your keyring. The protection on private-keys-v1.d is
> implemented differently than the protection of the
I've been reading about symmetric encryption of the private key.
When I tried to experiment with the `--s2k` options, attempting to
change the passphrase on my key, I found that they were ignored. A brief
search identified issue 1800 [1] on the bug tracker which was last
updated in 2015, some 20 m
