Bug #1474
Quassel does not take /setkey in the network Commands
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/06/2018
Due date:
% Done:
0%
Estimated time:
Version:
0.12.4
OS:
Any
Description
Steps:
1. Add "/setkey #channel foo" to network Commands to execute onconnect
2. Close Quassel and reopen it, then re-connect to the network
Results:
1. Plain text messages are sent in the channel
Expected results:
The encryption key is set correctly, and messages are encrypted
History
#1 Updated by Alturiak about 6 years ago
I can't seem to reproduce this issue, at least not in a distributed setup. Are you running a monolithic (client+core) installation, by any chance?
Does closing quassel include shutting down the core?
#2 Updated by Alturiak about 6 years ago
So, this probably is a duplicate of #1473.