Can't use oscar gaim-encryption imported keys
Brought to you by:
obobo
Menu
▾
▴
#135 Can't use oscar gaim-encryption imported keys
When upgrading from gaim to pidgin the id.priv file contains the old gaim-encryption style syntax for aim and icq accounts. In this syntax the beginning of lines in the id.priv file contain "screenname,prpl-oscar NSS 1.0" when pidgin is expecting "screenname,prpl-aim NSS 1.0" or "icq" in place of "aim" above.
When starting pidgin for the first time after a gaim to pidgin upgrade, gaim-encryption will attempt to re-generate new encryption keys for these accounts, although the old keys are still there in the file. Rather than just regenerating keys could the old id.priv file be updated to the pidgin-encryption syntax? This would prevent the need for users to manually make the syntax changes.
The manual solution to this problem is to start pidgin the first time, exit pidgin, open the id.priv file, delete any new keys that were generated, and change all occurrences of "oscar" to either "aim" or "icq". Next time pidgin is started it will operate as expected with the old keys.
Logged In: YES
user_id=21203
Originator: NO
I believe that this change was actually from before the Gaim->Pidgin transition. At some point Gaim/Pidgin changed the names of the AIM protocols, and since the Encryption plugin uses the protocol name together with the username to try to distinguish them, there are problems.
At this point I think that most folks have migrated (and have keys with the new protocol names), so I don't think it is too pressing an issue. Thanks for pointing out how users can solve it by hand, though.
-Bill