Michael Richardson

You are certainly right that it could be better: send code! eBPF would let you put the list of hosts into some kind of map, but we don't have that...

The BPF does the filtering, and anything is possible with the right BPF compiled in. Decoding is a different kettle of fish, and that's done in the tcpdump code, not...

It's not the trailing :, but the introduction of the term with the leading : that triggers this.

> The coap gem now lives at: https://github.com/nning/coap I'm happy to adopt coap library.

> So maybe organize moving over the repo from @nning (Henning) to @mcr (you)? Better to https://github.com/ANIMaGUS-minerva, which is an org.

> I had to add a cast from `const char *` to `char *` for OpenSSL 1.0.2's X509V3_EXT_nconf(). Given how insecure OpenSSL 1.0.x is, do we really care? It would...

I'm working on the many fixes for things that wolfSSL does not really provide in compatibility mode. I don't think it will turn out well, alas.

I configured with: ```` bucardo add db fountain dbname=fountain host=fountain01.local,fountain02.local user=bucardo conn="sslmode=require;sslkey=/app/postgres/bucardo/prime256v1.key;sslcert=/app/postgres/bucardo/prime256v1.crt" ```` These keys are also installed in ~/.postgresql via symlinks. They work for psql. It took me awhile...

On a whim, I tried converting the private key to pkcs8: ```` bucardo@minerva-fountain:/app/postgres/bucardo$ openssl pkcs8 -nocrypt -in prime256v1.key -topk8 -out prime256v1.pkcs8 ```` But, same result: ```` bucardo@minerva-fountain:~$ bucardo add all...

> @mcr Maybe the part of Bucardo that is trying to make that database connection is running inside PL/Perl in the Postgres database, so trying to read that key file...