Update to mailman 2.1.23 #51327
Labels
No Label
legacy module
Rendering & Cycles
legacy module
User Interface
legacy project
Cycles
legacy project
Documentation
legacy project
Infrastructure: blender.org
legacy project
Infrastructure: Blender Web Assets
legacy project
Infrastructure: Websites
legacy project
User Interface
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-org#51327
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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/
Changed status to: 'Open'
Added subscribers: @Blendify, @Ton
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.
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
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.