Re: [Dcrup] draft-ietf-dcrup-dkim-crypto-00

Yes, sorry.  You're right - it's the 255 byte limit of the individual
strings that's the issue.

And yes, the crudware will never be updated.

Best,

Peter

On Fri, May 19, 2017 at 6:03 PM, John R. Levine <johnl@iecc.com> wrote:

> In article <CAOj=BA0gKP9x5jgkZEUJD-EJvRSwC0dgmijwbDirsCQT4z0E4Q@mail.
> gmail.com>,
> Peter Goldstein  <peter@valimail.com> wrote:
>
>> The challenges with 2048 bit RSA are largely an issue of the limitations
>> of
>> the DNS infrastructure in use by the sending domain.  In some DNS
>> managers,
>> the Web UIs (and occasionally the underlying infrastructure) don't allow
>> domain owners to enter records that are larger than 512 octets.  Users of
>> these DNS managers generally cannot provision 2048 bit key DKIM TXT
>> records. ...
>>
>
> The problem isn't the 512 byte limit, since a 2K key is under 400
> bytes.  The problem is provisioning crudware that can't create TXT
> records with two strings.  But until the crudware is updated, which
> will likely be never, it's a problem.
>
> R's,
> John
>
>
> _______________________________________________
> Dcrup mailing list
> Dcrup@ietf.org
> https://www.ietf.org/mailman/listinfo/dcrup
>

-- 

[image: logo for sig file.png]

Bringing Trust to Email

Peter Goldstein | CTO & Co-Founder

peter@valimail.com
+1.415.793.5783