• Import of external Letsencrypt Certificates from NPM+ as pkcs12 contai

    From Deucе@VERT to GitLab note in main/sbbs on Wed Apr 22 08:28:07 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1111#note_8843

    So, the root cause here appears to be that you can't import a certificate without a subjectName DN. TLS since 2017 has not, by itself, required a DN and Let's Encrypt, when creating the short-lived for https certs, does not include one.

    The TLS cert for Synchronet is used by a fairly large number of "things" though, some of which may actually require a DN... a full audit needs to be done before blindly chopping that requirement out of Cryptlib.

    ---
    ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net
  • From Stephan Gebbers@VERT to GitLab note in main/sbbs on Wed Apr 22 09:24:36 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1111#note_8844

    Ok, thanks for taking care of it. In the meantime i try to switch the letsencrypt ACME_profile that NPMplus is using from shortlived/tlsserver to classic.

    https://letsencrypt.org/docs/profiles/

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net