Bug 28231

Summary:	TB maintenence keeps resetting security.tls.version.min after it has been manually reset
Product:	Mageia	Reporter:	Frank Griffin <ftg>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	thunderbird	CVE:
Status comment:

Description Frank Griffin 2021-01-27 03:21:37 CET

TB has decided that it has to be our TLS nanny and only wants to support versions >= 3 going forward.  My employer's sh***y Exchange mailserver doesn't support 3 yet, so I go into Edit -> Preferences -> General -> Config Editor and change security.tls.version.min from 3 to 1, and all is fine.

Until a new TB RPM arrives, and it is silently reset to 3.

Could prefs.js (or wherever this is stored) please be designated as a config file so that if the user has modified it it doesn't get replaced or modified ?  Because all of the other customized settings are left alone.  Clearly, prefs.js is not being replaced in toto, so if there is some specific patch that does this reset that can be eliminated, I would very much appreciate it.

Comment 1 Dave Hodgins 2021-01-27 03:48:28 CET

rpm package installation never modifies files in /home (which may or may not
be mounted when the packages are installed).

If new versions of thunderbird are modifying that value, it's being done by
thunderbird itself, not by the anything done in the packaging.

According to https://support.mozilla.org/da/questions/1295861 it intentionally
alters it, but allows it to be manually changed after that.

CC: (none) => davidwhodgins

Comment 2 Frank Griffin 2021-01-27 05:29:07 CET

Thanks, Dave.  I guess it's just going to be a PITA for a while then.

Resolution: (none) => INVALID
Status: NEW => RESOLVED

Comment 3 Dave Hodgins 2021-01-27 06:14:42 CET

Hopefully it's just the one release of tb that changed the prior setting,
not part of every new version.