From 8b24cd01f204c4f9a3cb28c2856b3078901e3df1 Mon Sep 17 00:00:00 2001 From: Aizistral Date: Thu, 22 Sep 2022 00:10:40 +0200 Subject: Add command encryption support --- src/main/resources/assets/nochatreports/lang/en_us.json | 1 + 1 file changed, 1 insertion(+) (limited to 'src/main/resources') diff --git a/src/main/resources/assets/nochatreports/lang/en_us.json b/src/main/resources/assets/nochatreports/lang/en_us.json index a5d3969..b3b7b77 100644 --- a/src/main/resources/assets/nochatreports/lang/en_us.json +++ b/src/main/resources/assets/nochatreports/lang/en_us.json @@ -34,6 +34,7 @@ "gui.nochatreports.encryption_config.pass_not_allowed": "", "gui.nochatreports.encryption_config.algorithm": "Algorithm: %1$s", "gui.nochatreports.encryption_config.default_key": "", + "gui.nochatreports.encryption_config.encrypt_public": "Encrypt normal messages (not sent via commands)", "algorithm.nochatreports.aes_cfb8_base64": "§lAES/CFB8+Base64§r\nStandard symmetric encryption algorithm. Uses 128 bit keys, output is Base64-encoded to permit transfer via Minecraft's chat. As a downside - messages will gain roughly 30% increase in length, and server might truncate them if they exceed size limit.", "algorithm.nochatreports.aes_gcm_base64": "§lAES/GCM+Base64§r\nMore security in exchange for severe increase in message size (12 bytes for initialization vector and 12 for authentication tag, Base64 encoding on top). Choose if you value security over anything else.", "algorithm.nochatreports.aes_ecb_base64": "§lAES/ECB+Base64§r\nConsiderably less secure than CFB mode, but saves you some bytes by not requiring initialization vector. Still beats Caesar.", -- cgit v1.2.3