From 06adb2adef12d5e4a89eddf0b9e4fe2802d2fb00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lorenz=20H=C3=BCbschle-Schneider?= Date: Thu, 30 Apr 2020 14:38:52 +0200 Subject: [PATCH] Add note on WeeChat 2.9 release date --- index.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/index.html b/index.html index b790cb3..e247912 100644 --- a/index.html +++ b/index.html @@ -137,6 +137,7 @@
@@ -199,7 +200,7 @@ chown -R username:username ~usernameCompatibility with WeeChat 2.8 and older

Required for WeeChat <= 2.8

-

With WeeChat 2.9, relay client authentication was made more secure and resistant to brute forcing. Glowing Bear uses the most secure authentication method by default. However, to support older versions of WeeChat, this option allows Glowing Bear to still use the old authentication method, sending your password to WeeChat (in plain text if you are not using encryption!). Only enable this if you are using a WeeChat version before 2.9!

+

With WeeChat 2.9—scheduled for release in July 2020—relay client authentication was made more secure and resistant to brute forcing. Glowing Bear uses the most secure authentication method by default. However, to support older versions of WeeChat, this option allows Glowing Bear to still use the old authentication method, sending your password to WeeChat (in plain text if you are not using encryption!). Only enable this if you are using a WeeChat version before 2.9!

By default, WeeChat 2.9 support several authentication methods. Of these, Glowing Bear only uses the most secure one, pbkdf2+sha512. You can check the list of enabled methods to ensure it is in there: /set relay.network.password_hash_algo