Bug 3807 - Decrypting AES encrypted passwords (for backups), configure password store
Summary: Decrypting AES encrypted passwords (for backups), configure password store
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Plugins/Privacy/PGP (show other bugs)
Version: 3.14.0
Hardware: PC Linux
: P3 minor
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2017-04-10 21:23 UTC by max_musterman256
Modified: 2017-04-10 22:11 UTC (History)
0 users

See Also:


Attachments

Description max_musterman256 2017-04-10 21:23:03 UTC
"The 3.14.0 release implements a completely new password storage backend."

Though I did not find a description in the manual for it (searching for password). Origin is a problem about a forgotten password and I have GPG installed/compiled according to the manual.
In ~/.claws-mail/passwordstorerc the password should be saved though mine seems to be recv {AES-256-CBC,50000}LONG_AES_KEY...

I guess this is GPG dependent, since a GPG key is used with this account.
How does the decription work? Can I do this manually as well?

I cannot configure the email accounts to not encrypt the passwords.
Is this behavior intendend? A notion/hint would be great.
Comment 1 Andrej Kacian 2017-04-10 22:11:44 UTC
Hi, the encryption scheme is described at http://git.claws-mail.org/?p=claws.git;a=blob;f=doc/src/password_encryption.txt

If you have not set a master passphrase, you should be able to decrypt the saved password using this information, since it is encrypted using a static key, selected at compile time (defaults to "passkey0", I don't think anyone ever changes this).

I am closing this, as this is a bug tracker, not a discussion or help forum. Please use a mailing list (http://claws-mail.org/MLs.php), or come visit us on IRC channel #claws at FreeNode instead.

Note You need to log in before you can comment on or make changes to this bug.