Update to mailman 2.1.23 #51327

Closed
opened 2017-04-26 17:15:20 +02:00 by Aaron Carlisle · 8 comments

Currently, we are running mailman 2.1.9 which is ten years old! We need to update to 2.1.23 released on 27-Aug-2016.
There is also 3.0 but this is still not ready for production use, maybe 3.1 but we need to at least update to 2.1.23 first.

http://www.list.org/

Currently, we are running mailman 2.1.9 which is ten years old! We need to update to 2.1.23 released on 27-Aug-2016. There is also 3.0 but this is still not ready for production use, maybe 3.1 but we need to at least update to 2.1.23 first. http://www.list.org/
Sergey Sharybin was assigned by Aaron Carlisle 2017-04-26 17:15:20 +02:00
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscribers: @Blendify, @Ton

Added subscribers: @Blendify, @Ton

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

We can't update easily, it has to do with FreeBSD etc etc. Not an issue for our dev site really.

We can't update easily, it has to do with FreeBSD etc etc. Not an issue for our dev site really.

Added subscriber: @LazyDodo

Added subscriber: @LazyDodo

Regardless if it's easy or not, i would really prefer if we did not store a giant cache of users passwords in clear text. might have been ok 10 years ago, but right now it's just bad security practice

Regardless if it's easy or not, i would really prefer if we did not store a giant cache of users passwords in clear text. might have been ok 10 years ago, but right now it's just bad security practice
Author

What is the exact issue that leaves us using such an old version with such bad security practices?

What is the exact issue that leaves us using such an old version with such bad security practices?

I strongly suggest not to discuss any technical specifics of our rack configuration here.

I strongly suggest not to discuss any technical specifics of our rack configuration here.
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-org#51327
No description provided.