On 2 Apr 2024, at 15:24, Werner Koch wrote:
>
> On Tue, 2 Apr 2024 12:39, Andrew Gallagher said:
>
>> Are you saying that this is *not* a novel failure mode? Because we’ve
>
> No. We had v2, v3 and v4 keyes in all kind of combinations in the past
> (even as part of subkeys) and back then the
On Tue, 2 Apr 2024 12:39, Andrew Gallagher said:
> Are you saying that this is *not* a novel failure mode? Because we’ve
No. We had v2, v3 and v4 keyes in all kind of combinations in the past
(even as part of subkeys) and back then the two OpenPGP implementations
had no problems with that. The
Hi, Werner, all.
Please let me take this opportunity to ask you for trustable documentation,
or any other resource, which could help interested users like myself in
providing the gpg-agent with ssh client and daemon errands, on both fresh
and not-so-fresh OS installs. Please consider SELinux conte
On 2 Apr 2024, at 11:58, Werner Koch wrote:
>
> On Fri, 29 Mar 2024 13:00, Andrew Gallagher said:
>
>> V5 subkeys of v4 primary keys would appear to introduce a novel
>> failure mode. It should be noted that in crypto-refresh, adding a
>
> Nope.
Are you saying that this is *not* a novel failur
On Fri, 29 Mar 2024 13:00, Andrew Gallagher said:
> V5 subkeys of v4 primary keys would appear to introduce a novel
> failure mode. It should be noted that in crypto-refresh, adding a
Nope. A v5 key has nothing to do a v4 signature and having different
algorithm on the primary key and the subkey
