On Sun, Apr 23, 2017 at 03:08:43PM +0100, Paul Saunders wrote: > Because ZNC uses a key+certificate+intermediate+dhparam file format, > this makes it difficult to use letsencrypt certificates (where the tools > tend to result in separate key and certificate+intermediate files) with > ZNC.
Quite unrelated to the feature request in itself (which is good and
probably save me the following code), it's all but hard to add something
like this to deploy_cert hook:
local tmpkey=$(mktemp -p /srv/znc/ssl tmp.XXXXXXXXX)
chmod 660 "${tmpkey}"
cat "${KEYFILE}" "${CERTFILE}" "${CHAINFILE}" > "${tmpkey}"
mv -f "${tmpkey}" /srv/znc/ssl/znc.pem
> Upstream has developed a patch[1] which allows for separate key and dhparam
> files, but it appears that either this patch hasn't been released or
> hasn't made it to debian.
Simply that commit has yet to appear on any release.
upstream git master is currently quite different than 1.6.x.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
