Péter Szilágyi

@aliforever You can ram through your request by working around the encoder which dishonours the API and call it properly directly: ``` client.KV.Namespaces.Values.Update(context.Background(), "your-namespace", "key", kv.NamespaceValueUpdateParams{AccountID: "yout-account-id"}, option.WithRequestBody("*/*", []byte("test"))) ```

In the same vein, calculating the max encoding length is similarly broken, it returns 0 for an empty input instead of the required 1. This causes further pain requiring special...

CC @fjl

If I dump a self signed certificate into the slots too, then they show up. Seems like a nice thing to fix.

A counter example where things don't work out. If I drop a X25519 key into a slot, I cannot create a self-signed certificate, since that key type cannot sign. As...

Seems that was not the issue that sped things up, rather reading from the endpoints was done with a larger buffer as a side effect (I sized the buffer according...

As far as I understand the docs, the way to sign a pubkey via a 3rd party key is [CertificateParams](https://docs.rs/rcgen/0.13.2/rcgen/struct.CertificateParams.html)::[signed_by](https://docs.rs/rcgen/0.13.2/rcgen/struct.CertificateParams.html#method.signed_by), where the key to be signed is [PublicKeyData](https://docs.rs/rcgen/0.13.2/rcgen/trait.PublicKeyData.html). The PublicKeyData...

Another issue with `signed_by` is that it requires an `issuer` certificate, which I don't want to provide (it's the usual way, but for pinned root of trusts, you can also...

This is the spec with the x25519 FWIW https://datatracker.ietf.org/doc/html/rfc8410, though you're probably aware as Ed25519 is also included in it :) Seems parts got left out for now. Would be...

@chiro-hiro Please don't hijack this issue with an unrelated problem. @djc I need to embed an X25519 key into a cert. That is allowed by the spec. That is not...