Open Ladeburger opened 3 years ago
I have the same issue. The key.path
is configured in the yaml config file, and the key files themselves are available, as you can see below.
/etc/ma1sd/ma1sd.yaml:
key:
path: '/var/lib/ma1sd/keys'
$ cat /var/lib/ma1sd/keys/current
{"type":"Regular","algo":"ed25519","serial":"AAAADwEUfRgD"}
$ cat /var/lib/ma1sd/keys/regular/ed25519/AAAADwEUfRgD
{"version":"0","is_valid":true,"key":"..."}
After reading through some of the spec, I got this example to work by appending the serial in the keys file in place of the '0'.
From the example above,
curl 'http://localhost:8090/_matrix/identity/api/v1/pubkey/ed25519:AAAADwEUfRgD'
I'm not sure if this is correct, however, so I haven't opened a PR to adjust the documentation.
since no-one cared to update this issue, or the documentation... I will post this from 15 jan in the ma1sd matrix room.
The build documentation says that to validate the configuration one should check whether there is a signing key avail:
` $ curl 'http://localhost:8090/_matrix/identity/api/v1/pubkey/ed25519:0'
{"public_key":"..."} `
But i get an error:
curl 'http://localhost:8090/_matrix/identity/api/v1/pubkey/ed25519:0' {"errcode":"M_NOT_FOUND","error":"Key with ID ed25519:0 does not exist","success":false}
The Server says:
[XNIO-1 task-1] INFO io.kamax.mxisd.http.undertow.handler.identity.share.KeyGetHandler - Key ed25519:0 was requested [XNIO-1 task-1] INFO io.kamax.mxisd.http.undertow.handler.BasicHttpHandler - Request GET http://localhost:8090/_matrix/identity/api/v1/pubkey/ed25519:0 - Error M_NOT_FOUND: Key with ID ed25519:0 does not exist