> On 28 Oct 2024, at 08:06, Viktor Dukhovni via mailop
> wrote:
>
> On Mon, Oct 28, 2024 at 07:48:42AM +, Pete Long wrote:
>
>>> On 28 Oct 2024, at 05:32, Viktor Dukhovni via mailop
>>> wrote:
>>>
>>> Mind you, why is there a trailing "#" at the end of the "p=" value,
>>> that's not a
On Sun 27/Oct/2024 18:35:29 +0100 John Levine via mailop wrote:
It appears that Viktor Dukhovni via mailop said:
On Sat, Oct 26, 2024 at 02:16:51PM -0400, John Levine via mailop wrote:
I wrote the RFC and I still haven't gotten around to it.
I hope you saw my note about returning to SPKI en
Thanks Viktor. I ran these commands I found in search result to generate a new
DKIM key pair yesterday and the public key does end up with a hash symbol:
# openssl genrsa -out valar_dkim_private.pem 2048
# openssl ec -in valar_dkim_private.pem -pubout -outform der | openssl base64 -A
openssl
On Mon, Oct 28, 2024 at 07:48:42AM +, Pete Long wrote:
> > On 28 Oct 2024, at 05:32, Viktor Dukhovni via mailop
> > wrote:
> >
> > Mind you, why is there a trailing "#" at the end of the "p=" value,
> > that's not a valid Base64 character, and is not expected here. The
> > correct encoding
> On 28 Oct 2024, at 05:32, Viktor Dukhovni via mailop
> wrote:
>
> Mind you, why is there a trailing "#" at the end of the "p=" value,
> that's not a valid Base64 character, and is not expected here. The
> correct encoding is without the trailing "#":
>
>"v=DKIM1; k=rsa;
> p=MIIBIjANBg
