Changeset 9829ae0 for doc


Ignore:
Timestamp:
2006-08-14T20:17:54Z (18 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
0383943
Parents:
d1f8759
Message:

Added information about the new file format to CHANGES.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/CHANGES

    rd1f8759 r9829ae0  
     1Version x.x:
     2- Most important change: New file format for user data (accounts, nicks and
     3  settings). Migration to the new format should happen transparently,
     4  BitlBee will read the old files and once you quit/save it will save in the
     5  new format. It is recommended to delete the old files (BitlBee doesn't do
     6  this automatically, it will just ignore them) since they won't be used
     7  anymore (and since the old file format is a security risk). Some advantages
     8  of this file format switch:
     9  * Safer format, since the identify-password is now salted before generating
     10    a checksum. This way one can't use MD5 reverse lookup databases to crack
     11    passwords. Also, the IM-account passwords are encrypted using RC4 instead
     12    of the simple obfuscation scheme which BitlBee used so far.
     13  * Easier to extend than the previous format (at least the .nicks format was
     14    horribly limited).
     15  * Nicknames for buddies are now saved per-account instead of per-protocol.
     16    So far having one buddy on multiple accounts of the same protocol was a
     17    problem because the nicks generated for the two "instances" of this buddy
     18    were very unpredictable.
     19    NOTE: This also means that "account del" removes not just the account,
     20    BUT ALSO ALL NICKNAMES! If you're changing IM accounts and don't want to
     21    lose the nicknames, you can now use "account set" to change the username
     22    and password for the existing connection.
     23  * Per-account settings (see the new "account set" command).
     24
    125Version 1.0:
    226- Removed some crashy debugging code.
Note: See TracChangeset for help on using the changeset viewer.