Hello Bastian, Am 20.11.18 um 17:44 schrieb Bastian Neuburger: > Hi, > >> I have however not yet tested what happens if you start thunderbird >> aftter the upgrade and close it right away (i.e. not trying to sign >> anything but also not entering the master password). I will try to test >> this later but now I need a working mail client. >> > > I also tested this variant now: > > 1. Have berkeley DB based profile that works fine with thunderbird 52 in > Jessie > 2. Upgrade thunderbird > 3. Start thunderbird > 4. Close it without doing anything (I am not prompted for the master > password) > 5. Start thunderbird again > > Expected results: > Either key3.db is still there or I am getting prompted for a master > password during step 4. > > Actual results: > Everything under "Your certificates" and "People" in the Certificate > Manager gone, all saved passwords gone. > > So the problem we encountered did not only wipe private keys, but also > certificates of other people I already corresponded with AND stored > passwords.
thanks for testing this, I'm unable to this as I don't use any of these features. > How should reporting with upstream be handled? Should I take care of it > myself or would you like to forward it? I'd prefer if you could do the interaction with upstream as I only would act as a man in the middle. And I haven't much time to work on Thunderbird now. Please give a note back about the upstream bug number so we can add a forwarding to this issue. Thanks! -- Regards Carsten Schoenert
