unauthorized Master Password feature activated on upgrade

RESOLVED INCOMPLETE

Status

Thunderbird
Security
--
critical
RESOLVED INCOMPLETE
7 years ago
6 years ago

People

(Reporter: medling, Unassigned)

Tracking

({dataloss})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [223 Migration][dupeme])

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 Firefox/3.5.11 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2M

I just upgraded from version 2.x to version  3.1.2.  It now asks for a Master Software Security Password.  I didn't have one in version 2.  Now it won't let me access my inbox because I don't know the new password I didn't have.
As a result, I have effectively lost my entire inbox.

Reproducible: Always

Steps to Reproduce:
1. reboot
2.  launch thunderbird
3.  still asks for password I never had.  I eventually have to "cancel" to proceed
Actual Results:  
can't access inbox


I only hope that it hasn't encrypted my inbox preventing me from rolling back to Thunderbird 2 so I can get my email back.
The inbox isn't protected, only the passwords are encrypted with a masterpasswords.
Please follow http://kb.mozillazine.org/Master_password#Resetting_the_master_password
(Reporter)

Comment 2

7 years ago
FOLLOWUP:  Investigation showed that it DELETED my inbox.  this was coincidental with the prompt for a non-existent master password that I assumed that it was just blocking access to the inbox.  An examination of the file structure showed that the file size of "inbox" and "inbox.msf" is 0.  (the inbox was 1.2 GB immediately before the upgrade)
Do you have a backup of your prefs.js file ?
Keywords: dataloss
Whiteboard: [223 Migration]

Updated

7 years ago
Whiteboard: [223 Migration] → [223 Migration][dupeme]
While I don't mean to diminish any pain that these bugs may have caused you in the past, it is impossible to triage, assess, or fix these bugs without more information. Since this necessary information is lacking, I am forced to close these reports; if you can provide the information, please comment in the bug so it may be reopened.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.