I think this is the right time to do this.
Stuart Henderson wrote:
> On 2019/03/30 13:43, Theo de Raadt wrote:
> > I think we should switch, waiting doesn't help.
> >
> > Reyk Floeter wrote:
> >
> > > I like the idea of switching it to the proper ID.
> > >
> > > Reyk
> > >
> > > > Am 30.03.
On 2019/03/30 13:43, Theo de Raadt wrote:
> I think we should switch, waiting doesn't help.
>
> Reyk Floeter wrote:
>
> > I like the idea of switching it to the proper ID.
> >
> > Reyk
> >
> > > Am 30.03.2019 um 20:31 schrieb Stuart Henderson :
> > >
> > > curve25519 had a proper ID (31) assi
1:53 PM
To: tech@openbsd.org
Cc: r...@openbsd.org; s...@spacehopper.org
Subject: [EXTERNAL] Re: iked curve25519
+1 for adding ID 31
Maybe add the proper one but also keep the old to give people some time to
update their stuff if this is a problem.
There should be more than enough reserved IDs.
+1 for adding ID 31
Maybe add the proper one but also keep the old to give people some time
to update their stuff if this is a problem.
There should be more than enough reserved IDs.
On 3/30/19 8:35 PM, Reyk Floeter wrote:
> I like the idea of switching it to the proper ID.
>
> Reyk
>
>> Am 30.
I think we should switch, waiting doesn't help.
Reyk Floeter wrote:
> I like the idea of switching it to the proper ID.
>
> Reyk
>
> > Am 30.03.2019 um 20:31 schrieb Stuart Henderson :
> >
> > curve25519 had a proper ID (31) assigned in 2016 but we still have
> > the draft private-use ID in i
I like the idea of switching it to the proper ID.
Reyk
> Am 30.03.2019 um 20:31 schrieb Stuart Henderson :
>
> curve25519 had a proper ID (31) assigned in 2016 but we still have
> the draft private-use ID in iked. Any thoughts on whether we can just
> cut across to the proper ID, or whether that
curve25519 had a proper ID (31) assigned in 2016 but we still have
the draft private-use ID in iked. Any thoughts on whether we can just
cut across to the proper ID, or whether that will be too painful?
Are many people using this already?
