diff options
| author | Tharre <tharre3@gmail.com> | 2018-07-16 22:43:20 +0200 |
|---|---|---|
| committer | Tharre <tharre3@gmail.com> | 2018-07-16 22:54:05 +0200 |
| commit | 74c2fc774532e2860f1fbf655af37c8a63ae76da (patch) | |
| tree | 410d800ff45e22de15d8fbe8968a7be7e65e5ccf | |
| parent | 4984b1a04ad04cc81822bf46de28f0bccb31a639 (diff) | |
| download | dotfiles-74c2fc774532e2860f1fbf655af37c8a63ae76da.tar.gz dotfiles-74c2fc774532e2860f1fbf655af37c8a63ae76da.tar.xz dotfiles-74c2fc774532e2860f1fbf655af37c8a63ae76da.zip | |
weechat: disable password salting
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.
| -rw-r--r-- | .weechat/sec.conf | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/.weechat/sec.conf b/.weechat/sec.conf index 3baea26..3eb61f8 100644 --- a/.weechat/sec.conf +++ b/.weechat/sec.conf @@ -13,8 +13,8 @@ cipher = aes256 hash_algo = sha256 passphrase_file = "" -salt = on +salt = off [data] __passphrase__ = on -zncpass = "92275CD849245EA649820FD6AAE50B692F52A9249F5990094AAFFBA1D2EDB304EB99518567F6F0E5C26E3A1666428C54AD1D8F3167EC71AEAFBF4423A2333A7078518915BD3CA5B40DADF3720B25E0B62B72541104D02316214A95" +zncpass = "5765654368617421C32BB9FDEB9EAFB458E8A4D920E23D0B5006A874596682AFD53D4D33BE60FF46AAB7686DDA79C5DFCB33C8E506E0EB6D80709910B55CE9125FE7757EE880779E0E4C9A5C249DE00DB10B95929761E2968A2255" |