[Pkg-mailman-hackers] Bug#983681: Hyperkitty API token is not set in Hyperkitty configuration
Thomas Koch
thomas at koch.ro
Sun Feb 28 12:09:40 GMT 2021
Package: mailman3-web
Version: 0+20180916-8
The README.Debian.gz claims:
* A secure API token for the Hyperkitty archiver is generated and
set both in the Django and in the Hyperkitty configuration.
However I only see this token being set in MAILMAN_ARCHIVER_KEY in /etc/mailman3/mailman-web.py.
The api_key setting in section general of /etc/mailman3/mailman-hyperkitty.cfg is still "SecretArchiverAPIKey".
This has probably not yet been reported since the hyperkitty configuration still needs manual intervention anyways, e.g. enabling the archiver in mailman.cfg.
More information about the Pkg-mailman-hackers
mailing list