summaryrefslogtreecommitdiffstats
path: root/.weechat/sec.conf
Commit message (Collapse)AuthorAgeFilesLines
* weechat: use new passphrase_command instead of envTharre2021-12-191-1/+1
|
* weechat: update default config (version 3.3)Tharre2021-12-191-2/+2
|
* weechat: disable password saltingTharre2018-07-161-2/+2
| | | | | | | | | | | | | | | weechat unfortunately changes the salt each time it writes to sec.conf, even if the password itself hasn't changed. From the documentation of sec.crypt.salt: description: use salt when generating key used in encryption (recommended for maximum security); when enabled, the content of crypted data in file sec.conf will be different on each write of the file; if you put the file sec.conf in a version control system, then you can turn off this option to have always same content in file Since we're using a long and random password anyway, that isn't being reused, this is safe to disable.
* weechat: use password from passTharre2018-06-281-1/+1
|
* Add initial weechat configurationTharre2018-06-141-0/+20