Control: clone 817858 -1
Control: retitle -1 gnupg: undocumented tsign behavior does not achieve what
dkg says it should
> Yes, i think it should.
Great!
> However, in my testing, it looks to me like neither gpg 1.4.x nor 2.1.x
> consider regex-scoped tsigs in their verification. This seems li
On Fri 2016-03-11 17:35:17 -0500, Clint Adams wrote:
> On Fri, Mar 11, 2016 at 04:42:40PM -0500, Daniel Kahn Gillmor wrote:
>> fwiw, it means "limit this trust signature to only cover certifications
>> of User IDs with e-mail addresses that have the given domain after the @
>> sign"
>>
>> So if i
On Fri, Mar 11, 2016 at 04:42:40PM -0500, Daniel Kahn Gillmor wrote:
> fwiw, it means "limit this trust signature to only cover certifications
> of User IDs with e-mail addresses that have the given domain after the @
> sign"
>
> So if i tsign ad...@example.org's key X with a domain of "example.or
On Thu 2016-03-10 19:59:24 -0500, Clint Adams wrote:
> Package: gnupg
> Version: 1.4.18-7
>
> When doing a 'tsign' in --edit-key, gpg says
>
> Please enter a domain to restrict this signature, or enter for none.
>
> The meaning of this does not appear to be documented.
fwiw, it means "limit th
4 matches
Mail list logo
