Bas Couwenberg

I'm not a fan off including all these JavaScript bits. Thankfully we don't have to build those bits from source, because the Node.js ecosystem is too much of a pain...

SWIG development is very slow, don't count on change there.

An `openssl.cnf` like this used to work on buster and bullseye: ``` $ cat /tmp/openssl.cnf openssl_conf = openssl_init config_diagnostics = 1 [openssl_init] providers = provider_sect [provider_sect] default = default_sect [default_sect]...

Appending `@SECLEVEL={0,1}` makes no difference: ``` $ cat /tmp/openssl.cnf openssl_conf = openssl_init config_diagnostics = 1 [openssl_init] providers = provider_sect [provider_sect] default = default_sect [default_sect] activate = 1 ssl_conf = ssl_sect...

> `strace` shows that the file gets read, but it seems that the `ssl_conf` option is ignored. OpenSSL 3.0.11 on bookworm apparently requires the `ssl_conf` option in the `openssl_init` section...

> I think I will try (the workaround) shortly, cause I need to update a buster system to bullseye (at least) but (still) need to monitor vintage systems with broken^Wold...

Again a trivial change, likely not copyrightable but if it is, I'm fine with the relicensing.

To quote myself: > It's pretty much the same change as for pycoast & trollsift, likely not copyrightable but if it is, I'm fine with the relicensing.