Results 26 comments of Geert Hendrickx

FWIW, the bundled `openssl.Linux.x86_64` binary also segfaults when connecting to an TLSv1.3-only server. This is on Arch Linux, but without systemd-resolved, just using an external resolver from /etc/resolv.conf.

@Neilpang, can acme.sh reconsider this, too? (for new certificates, not for renewals)

It only prints this on startup: ``` SBFspotUploadDaemon Version 3.0.1 Loglevel=2 LogDir=/tmp/ ``` This is what systemd/journald has rotated away since you started the daemon. The regular "Uploading datapoint..." output...

Thanks! Two small nits; * it's logging the version banner twice (first three lines were already logged to stderr before this change) * timestamps are usually not included on stdout,...

And thirdly, could you write regular info logs to stdout (std::cout) instead of stderr?

ie. this works better for me: ``` // On linux systems when logdir is empty, log to console instead of file std::cout

This just stretches the race condition a little bit. A better solution is to just drop the `PIDFile` line and let systemd manage the opendkim process directly (systemd recommends this...

On EL8, it's packaged separately in `opendkim-tools`.

No idea why they decided to split this (as well as libopendkim), it has the same dependencies etc.

I'm also running two milters, one to sign with RSA and verify (it verifies both algorithms) and a second one to sign with Ed25519 (and not verify). This is not...