From: Michael Marley <michael@michaelmarley.com>
Date: Tue, 8 May 2018 18:49:33 +0000 (-0500)
Subject: Persist Blowfish keys in the database
X-Git-Tag: travis-deploy-test~120
X-Git-Url: https://git.quassel-irc.org/?a=commitdiff_plain;ds=sidebyside;h=c382e0c11f80fb37307ecc42c487aa433c97ad8c;hp=c382e0c11f80fb37307ecc42c487aa433c97ad8c;p=quassel.git

Persist Blowfish keys in the database

Add a new text field called "cipher" and store the hex-encoded
cipher key there whenever a new key is set or exchanged.  Also,
when each network is initialized, load the ciphers out of the
database and initialize the in-memory hashmap.  Then, the existing
behavior of each CoreIrcNetwork automatically using these keys
upon construction occurs.

Additionally, this makes PM buffer ciphers persistent both across
destruction/construction and across core restarts.

Note that the existing "key" field in the database is confusingly
named.  It does not contain any sort of cryptographic key but
instead holds channel passwords.

Closes #1473

Closes GH-332.
---