Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://chaos.social/users/saxnot/statuses/114176683341931712">saxnot (saxnot@chaos.social)'s status on Tuesday, 18-Mar-2025 01:16:08 JST</a><a href="https://chaos.social/@saxnot" title="saxnot@chaos.social"><img src="https://gnusocial.jp/avatar/5550-48-20231020041728.webp" width="48" height="48" alt="saxnot" style="position: absolute; left: 0; top: 0;">saxnot</a><div><a href="https://chaos.social/@saxnot/114176669890304915" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/293302" title="kuketz@social.tchncs.de">Mike Kuketz :mastodon:</a></li></ul></div></section><article><p><a href="https://friedcheese.us/users/feld">@feld</a> According to german security expert <a href="https://social.tchncs.de/@kuketz">@kuketz</a> in his blog article from 2020 there is at the time no audit for the Telegram MTProto 2.0 protocol.<br><a href="https://www.kuketz-blog.de/telegram-sicherheit-gibt-es-nur-auf-anfrage-messenger-teil3/" rel="nofollow noreferrer">https://www.kuketz-blog.de/telegram-sicherheit-gibt-es-nur-auf-anfrage-messenger-teil3/</a></p><p>Correct me if that is wrong. The first MTProto was broken in a very amateurish way. The second not audited at all to my knowledge.</p><p>I like to believe Telegram being an unattractive target for audits anyways since it's closed source and publicly criticizing tools of the russian state might be bad for your health<br><a href="https://chaos.social/tags/telegram" rel="tag">#telegram</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4743121#notice-9298562">In conversation</a><time datetime="2025-03-18T01:16:08+09:00" title="Tuesday, 18-Mar-2025 01:16:08 JST">about 18 days ago</time> <span>from <span><a href="https://chaos.social/@saxnot/114176683341931712" rel="external" title="Sent from chaos.social via ActivityPub">chaos.social</a></span></span><a href="https://chaos.social/@saxnot/114176683341931712">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/4315894">Untitled attachment</a></label><br></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
saxnot (saxnot@chaos.social)'s status on Tuesday, 18-Mar-2025 01:16:08 JSTsaxnot
in reply to
- feld
- Mike Kuketz :mastodon:
@feld According to german security expert @kuketz in his blog article from 2020 there is at the time no audit for the Telegram MTProto 2.0 protocol.
https://www.kuketz-blog.de/telegram-sicherheit-gibt-es-nur-auf-anfrage-messenger-teil3/
Correct me if that is wrong. The first MTProto was broken in a very amateurish way. The second not audited at all to my knowledge.
I like to believe Telegram being an unattractive target for audits anyways since it's closed source and publicly criticizing tools of the russian state might be bad for your health
#telegram
In conversationabout 18 days ago from chaos.socialpermalink
Attachments
1. Untitled attachment

Public

Embed Notice

HTML Code

Corresponding Notice