<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automated Symbolic Verification of Telegram's MTProto 2.0 · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2012.03141/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2012.03141/feed.xml" rel="self" type="application/rss+xml" /><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — mentioned by gloosx</title><link>https://news.ycombinator.com/item?id=41348519</link><guid isPermaLink="false">urn:hackerpapers:mention:2012.03141:41348519</guid><pubDate>Sun, 25 Aug 2024 16:22:19 GMT</pubDate><description>&lt;p&gt;That&amp;#x27;s a popular lie, Telegram uses the MTProto 2.0 Cloud algorithm for non-secret chats, which is audited and verified by multiple independent parties. For example WhatsApp claims it uses EE2E encrypted chats, how ever these claims are unverified and not audited. Also their chief executives are not in jail, coincidentally. You can consult these links if you want to read more about it: https://core.telegram.org/mtproto/AJiEAwIYFoAsBGJBjZwYoQIwFM... https://arxiv.org/pdf/2012.03141 https://github.com/miculan/telegram-mtproto2-verification&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — mentioned by NayamAmarshe</title><link>https://news.ycombinator.com/item?id=41348228</link><guid isPermaLink="false">urn:hackerpapers:mention:2012.03141:41348228</guid><pubDate>Sun, 25 Aug 2024 15:53:47 GMT</pubDate><description>&lt;p&gt;&amp;gt; They are stored in plaintext on telegram servers FYI, this is a totally misleading and false claim. Telegram uses the MTProto 2.0 Cloud algorithm for non-secret chats[1][2]. In fact, it uses a split-key encryption system and the servers are all stored in multiple jurisdictions. So even Telegram employees can&amp;#x27;t decrypt the chats, because you&amp;#x27;d need to compromise all the servers at the same time. Telegram&amp;#x27;s algorithm has been independently audited multiple times. Compared to other apps like WhatsApp with claims of E2EE and no body of verification and validation.[3] [1]…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — mentioned by robryk</title><link>https://news.ycombinator.com/item?id=35560081</link><guid isPermaLink="false">urn:hackerpapers:mention:2012.03141:35560081</guid><pubDate>Thu, 13 Apr 2023 18:39:55 GMT</pubDate><description>&lt;p&gt;&amp;gt; The algorithm is public. It is a straightforward application of well known primitives. It is hardly proprietary. Note that its predecessor, was very much not that (e.g. https://words.filippo.io/dispatches/telegram-ecdh/ was a vulnerability in it, and it stuck to some weird choices of crypto primitives/key sizes for a pretty long time). This colors my expectations about the current version slightly. I personally know nothing about the current protocol used (mtproto 2.0) and a few minutes of googling surfaced https://eprint.iacr.org/2022/595.pdf, https://eprint.iacr.org/2023/469 and…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — HN submission</title><link>https://news.ycombinator.com/item?id=34340574</link><guid isPermaLink="false">urn:hackerpapers:submission:2012.03141:34340574</guid><pubDate>Wed, 11 Jan 2023 16:46:19 GMT</pubDate><description>&lt;p&gt;Telegram&amp;#x27;s MTProto 2.0 proven formally correct (2021) [pdf]&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;3 points; 1 discussion reply on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — mentioned by lloeki</title><link>https://news.ycombinator.com/item?id=33124822</link><guid isPermaLink="false">urn:hackerpapers:mention:2012.03141:33124822</guid><pubDate>Fri, 07 Oct 2022 18:01:22 GMT</pubDate><description>&lt;p&gt;&amp;gt; Telegram holds the keys to decrypt the messages and that&amp;#x27;s all you need to know. That&amp;#x27;s an entirely different problem than TFA (an attacker accessing and being able to impersonate an account by subverting a third party 2FA middleman), which Telegram guards against as as soon as you have one device enrolled the code is sent over Telegram, not SMS. &amp;gt; It&amp;#x27;s why you are able to just login to your Telegram account on another device and magically get all of your message history. Being able to log in and get your history to sync is not a telltale sign that history is not encrypted and thus visible…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — HN submission</title><link>https://news.ycombinator.com/item?id=25722076</link><guid isPermaLink="false">urn:hackerpapers:submission:2012.03141:25722076</guid><pubDate>Mon, 11 Jan 2021 00:10:29 GMT</pubDate><description>&lt;p&gt;Automated Symbolic Verification of Telegram&amp;#x27;s MTProto 2.0&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;64 points; 53 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — mentioned by j-james</title><link>https://news.ycombinator.com/item?id=25671215</link><guid isPermaLink="false">urn:hackerpapers:mention:2012.03141:25671215</guid><pubDate>Thu, 07 Jan 2021 14:13:41 GMT</pubDate><description>&lt;p&gt;Each of these have fairly different use cases. WhatsApp is bad. They are owned by a data collection company notorious for gross privacy violations. Both the client apps and the server are completely closed source, which means either could be spying on you without any way to know. They do claim to implement the secure Signal Protocol, but how do you verify end to end encryption without seeing source code, anyway? Telegram is a perfectly adequate choice. The user experience is similar to WhatsApp. It does practice some dark patterns - end to end encryption is only available in &amp;quot;secret chats&amp;quot;…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — mentioned by j-james</title><link>https://news.ycombinator.com/item?id=25664081</link><guid isPermaLink="false">urn:hackerpapers:mention:2012.03141:25664081</guid><pubDate>Wed, 06 Jan 2021 23:16:35 GMT</pubDate><description>&lt;p&gt;Telegram&amp;#x27;s MTProto 2.0 encryption protocol was recently proved correct, but I haven&amp;#x27;t seen any peer review or discussion on the paper yet. https://arxiv.org/abs/2012.03141&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — HN submission</title><link>https://news.ycombinator.com/item?id=25642894</link><guid isPermaLink="false">urn:hackerpapers:submission:2012.03141:25642894</guid><pubDate>Tue, 05 Jan 2021 06:57:24 GMT</pubDate><description>&lt;p&gt;Automated Symbolic Verification of Telegram’s MTProto 2.0&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — mentioned by j-james</title><link>https://news.ycombinator.com/item?id=25642023</link><guid isPermaLink="false">urn:hackerpapers:mention:2012.03141:25642023</guid><pubDate>Tue, 05 Jan 2021 04:13:54 GMT</pubDate><description>&lt;p&gt;Telegram&amp;#x27;s protocol itself isn&amp;#x27;t necessarily a weakness - recently, a paper was published claiming to have proved the MTProto 2.0 protocol correct. Perhaps because of how recent this was, it doesn&amp;#x27;t seem to have garnered any discussion or review anywhere. https://arxiv.org/abs/2012.03141&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Automated Symbolic Verification of Telegram's MTProto 2.0 — HN submission</title><link>https://news.ycombinator.com/item?id=25524371</link><guid isPermaLink="false">urn:hackerpapers:submission:2012.03141:25524371</guid><pubDate>Thu, 24 Dec 2020 01:49:52 GMT</pubDate><description>&lt;p&gt;Automated Symbolic Verification of Telegram&amp;#x27;s Cryptographic Protocol&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;7 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2012.03141/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
