From 36be7f070eee9f87117e3f46e9a38f65b4517499 Mon Sep 17 00:00:00 2001 From: Sergey Matveev Date: Mon, 12 Jan 2026 16:10:17 +0300 Subject: [PATCH] =?utf8?q?=D0=95=D1=89=D1=91=20=D0=BE=D0=B4=D0=B8=D0=BD=20?= =?utf8?q?=D0=BA=D1=80=D0=B8=D0=BF=D1=82=D0=BE=D0=B0=D0=BD=D0=B0=D0=BB?= =?utf8?q?=D0=B8=D0=B7=20Telegram?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit --- faq.texi | 1 + 1 file changed, 1 insertion(+) diff --git a/faq.texi b/faq.texi index 4a6ff43..212b54d 100644 --- a/faq.texi +++ b/faq.texi @@ -303,6 +303,7 @@ XXX быстрее, лучше и безопаснее? У преобладаю Ни в коем случае, так как его @code{MTProto} протокол уязвим к CCA атакам и не аутентифицирует шифротекст. Подробнее можно прочитать: @url{https://eprint.iacr.org/2015/1177.pdf, "On the CCA insecurity of MTProto"}, +@url{https://eprint.iacr.org/2023/469.pdf, "Four Attacks and a Proof for Telegram"}, @url{https://mtpsym.github.io/, "Security Analysis of Telegram"}, @url{http://unhandledexpression.com/crypto/general/security/2013/12/17/telegram-stand-back-we-know-maths.html, "Telegram AKA Stand back we have Math PhDs!"}, @url{https://www.cryptofails.com/post/70546720222/telegrams-cryptanalysis-contest, "Telegram's Cryptanalysis Contest"}, -- 2.52.0