Re: [Ietf-dkim] DKIM Signature

2023-10-28 Thread Scott Kitterman
How many algorithms do you think is enough and why?

Scott K

On October 28, 2023 10:54:42 PM UTC, Thomas Vincent  
wrote:
>Future proofing? The history of encryption is riddled with examples of
>overconfidence.
>
>On Fri, Oct 27, 2023 at 2:02 PM John Levine  wrote:
>
>> It appears that Scott Kitterman   said:
>> >On October 27, 2023 2:56:30 PM UTC, "Murray S. Kucherawy" <
>> superu...@gmail.com> wrote:
>> >>On Sun, Oct 1, 2023 at 1:50 AM Jan Dušátko > 40dusatko@dmarc.ietf.org>
>> >>wrote:
>> >>
>> >>> I would like to ask to consider the possibility of defining a DKIM
>> >>> signature using Ed448. [...]
>>
>> >My view is that more encryption algorithms are bad for interoperability.
>> For DKIM signing/verifying to work, senders
>> >and verifiers need a common algorithm.  More choices make this more
>> complex to achieve.
>> >
>> >We standardized ed25119 as a hedge against unknown vulnerability in RSA.
>> ...
>>
>> Since we already have ed25519, why would we want ed448?  If ed25519 is a
>> ten ton steel
>> door on our cardboard box, ed448 is a fifteen ton steel door.
>>
>> R's,
>> John
>>
>> ___
>> Ietf-dkim mailing list
>> Ietf-dkim@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-dkim
>>

___
Ietf-dkim mailing list
Ietf-dkim@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-dkim


Re: [Ietf-dkim] DKIM Signature

2023-10-28 Thread Thomas Vincent
Future proofing? The history of encryption is riddled with examples of
overconfidence.

On Fri, Oct 27, 2023 at 2:02 PM John Levine  wrote:

> It appears that Scott Kitterman   said:
> >On October 27, 2023 2:56:30 PM UTC, "Murray S. Kucherawy" <
> superu...@gmail.com> wrote:
> >>On Sun, Oct 1, 2023 at 1:50 AM Jan Dušátko  40dusatko@dmarc.ietf.org>
> >>wrote:
> >>
> >>> I would like to ask to consider the possibility of defining a DKIM
> >>> signature using Ed448. [...]
>
> >My view is that more encryption algorithms are bad for interoperability.
> For DKIM signing/verifying to work, senders
> >and verifiers need a common algorithm.  More choices make this more
> complex to achieve.
> >
> >We standardized ed25119 as a hedge against unknown vulnerability in RSA.
> ...
>
> Since we already have ed25519, why would we want ed448?  If ed25519 is a
> ten ton steel
> door on our cardboard box, ed448 is a fifteen ton steel door.
>
> R's,
> John
>
> ___
> Ietf-dkim mailing list
> Ietf-dkim@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-dkim
>
___
Ietf-dkim mailing list
Ietf-dkim@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-dkim