On April 14, 2024 12:51:26 AM UTC, Steffen Nurpmeso wrote:
>Hello.
>
>Thanks to Hanno Böck (known from ossec and more) i was pointed to
>my falsely published ED25519 DKIM key.
>Until now that simply was the complete ED25519 public key, just
>like for RSA, instead of extracting the actual
Scott Kitterman wrote in
<5368ac9a-51d5-4aec-ab19-613dbead7...@kitterman.com>:
|On April 14, 2024 12:51:26 AM UTC, Steffen Nurpmeso \
|wrote:
|>Hello.
|>
|>Thanks to Hanno Böck (known from ossec and more) i was pointed to
|>my falsely published ED25519 DKIM key.
|>Until now that simply
Steffen Nurpmeso wrote in
<20240414005126.pzjJO4pr@steffen%sdaoden.eu>:
|Thanks to Hanno Böck (known from ossec and more) i was pointed to
|my falsely published ED25519 DKIM key.
|Until now that simply was the complete ED25519 public key, just
|like for RSA, instead of extracting the actual
It appears that Steffen Nurpmeso said:
> |I realize that RFC 8463 says repeatedly that the base64-encoded
> |representation of an ED25519 key is 44 bytes, and that the
> |examples go for this. Still there is no wording that the entire
> |ASN.1 structure shall be thrown away.
Yeah, I should
Hello.
Thanks to Hanno Böck (known from ossec and more) i was pointed to
my falsely published ED25519 DKIM key.
Until now that simply was the complete ED25519 public key, just
like for RSA, instead of extracting the actual "bitstring data"
from the standardized ASN.1 container, which starts at
John Levine wrote in
<20240414010739.d752f8861...@ary.qy>:
|It appears that Steffen Nurpmeso said:
|>|I realize that RFC 8463 says repeatedly that the base64-encoded
|>|representation of an ED25519 key is 44 bytes, and that the
|>|examples go for this. Still there is no wording that the
On April 14, 2024 1:53:07 AM UTC, Steffen Nurpmeso wrote:
>Scott Kitterman wrote in
> <5368ac9a-51d5-4aec-ab19-613dbead7...@kitterman.com>:
> |On April 14, 2024 12:51:26 AM UTC, Steffen Nurpmeso \
> |wrote:
> |>Hello.
> |>
> |>Thanks to Hanno Böck (known from ossec and more) i was pointed to
>
