Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump the mailman-hyperkitty plugin to 1.2.0. #528

Merged
merged 1 commit into from
Apr 14, 2022
Merged

Conversation

robol
Copy link
Contributor

@robol robol commented Nov 23, 2021

This new version sends the api_key as an Authorization header instead of
a GET parameter, which fixes a security vulnerability. The change is needed
since Hyperkitty has been upgraded to 1.3.5.

As far as I can tell, this should fix #527; I have not directly tested the new images,
but I have run pip install mailman-hyperkitty==1.2.0 inside the container, and that was
enough to fix the archiver error.

This new version sends the api_key as an Authorization header instead of
a GET parameter, which fixes a security vulnerability. The change is needed
since Hyperkitty has been upgraded to 1.3.5.
@kiorky
Copy link

kiorky commented Jan 20, 2022

confirmed

@maxking maxking merged commit cb17f46 into maxking:main Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] mailman-core: hyperkitty needs an update to version 1.2.0
3 participants