HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
telegram-s
telegram-mt-old
Java2013–2013
telegram-s / telegram-mt-old

telegram-mt-old

Java MTProto implementation

4Distinct people
4Mentions
0Explicit recommenders
128GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Java MTProto implementation

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour4 dated mentions

Observed mentions: 2013-12-16 10:33:53 UTC to 2013-12-17 01:23:24 UTC.

0122013-12-16 10:00:00 UTC to 2013-12-16 11:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsDec 16, 10:002013-12-16 11:00:00 UTC to 2013-12-16 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 12:00:00 UTC to 2013-12-16 13:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2013-12-16 13:00:00 UTC to 2013-12-16 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 14:00:00 UTC to 2013-12-16 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 15:00:00 UTC to 2013-12-16 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 16:00:00 UTC to 2013-12-16 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 17:00:00 UTC to 2013-12-16 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 16, 17:002013-12-16 18:00:00 UTC to 2013-12-16 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 19:00:00 UTC to 2013-12-16 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 20:00:00 UTC to 2013-12-16 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 21:00:00 UTC to 2013-12-16 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 22:00:00 UTC to 2013-12-16 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-16 23:00:00 UTC to 2013-12-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-17 00:00:00 UTC to 2013-12-17 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-12-17 01:00:00 UTC to 2013-12-17 02:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 17, 01:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 16, 10:002013-12-16 10:00:00 UTC2013-12-16 11:00:00 UTC202
Dec 16, 11:002013-12-16 11:00:00 UTC2013-12-16 12:00:00 UTC000
Dec 16, 12:002013-12-16 12:00:00 UTC2013-12-16 13:00:00 UTC101
Dec 16, 13:002013-12-16 13:00:00 UTC2013-12-16 14:00:00 UTC000
Dec 16, 14:002013-12-16 14:00:00 UTC2013-12-16 15:00:00 UTC000
Dec 16, 15:002013-12-16 15:00:00 UTC2013-12-16 16:00:00 UTC000
Dec 16, 16:002013-12-16 16:00:00 UTC2013-12-16 17:00:00 UTC000
Dec 16, 17:002013-12-16 17:00:00 UTC2013-12-16 18:00:00 UTC000
Dec 16, 18:002013-12-16 18:00:00 UTC2013-12-16 19:00:00 UTC000
Dec 16, 19:002013-12-16 19:00:00 UTC2013-12-16 20:00:00 UTC000
Dec 16, 20:002013-12-16 20:00:00 UTC2013-12-16 21:00:00 UTC000
Dec 16, 21:002013-12-16 21:00:00 UTC2013-12-16 22:00:00 UTC000
Dec 16, 22:002013-12-16 22:00:00 UTC2013-12-16 23:00:00 UTC000
Dec 16, 23:002013-12-16 23:00:00 UTC2013-12-17 00:00:00 UTC000
Dec 17, 00:002013-12-17 00:00:00 UTC2013-12-17 01:00:00 UTC000
Dec 17, 01:002013-12-17 01:00:00 UTC2013-12-17 02:00:00 UTC101

What Hacker News says

4 sources
Disclaimer: I am not a cryptographer, and have only gotten to #40 in Matasano's challenges. They appear to be trying to use encrypt and mac, and not as far as I can tell relying on IGE mode to provide authentication. See the "Message Key" and "Important Tests" sections here: https://core.telegram.org/mtproto/description There is also not, as far as I can tell from reading the protocol description above and the source code here: https://github.com/ex3ndr/telegram-mt/blob/master/src/main/j... (in particular the EncryptedMessage method, lines 447 to 460) any sort of key in the MAC, it's just SHA-1 of the plaintext. It's also not encrypted as far as I can tell, it's listed in the unencrypted "external header" in the protocol description. I can't think of an attack from this, but the fact that an adversary can generate a valid MAC for _any
Read the rest
message_ by simply SHA-1'ing it seems really scary.
In Telegram - secure, free messaging
Great, let's take a quick look. TcpContext.java[1] says: MAX_PACKED_SIZE = 1024 * 1024 * 1024;//1 MB READ_DIE_TIMEOUT = 5 * 1000; // 15 sec So those are bugs, though I'm not sure if documentation or code. Most importantly to me, there are very few comments in the code, and the few there are are incorrect. One might infer that this code has been written either in haste, or by someone who believes that comments are not needed in this sort of systems code. There are also writeInt() and readInt() method which seems to be little-endian, which seems odd for a network program. No comments near them. Finally, there's a "Package" class which is just a byte array and a flag. And there's a method which writes it after a cute encoding for the length divided by 4. But there is no code which checks that the length is evenly divisible by 4
Read the rest
. This may lead to incomplete Packages being written, with what effect I am not sure. In summary, I wouldn't trust this program, having reviewed one of its source files mostly at random. Oh, and despite its README saying that it is designed for mobile, it uses TCP Keep-Alive, which seems like a bad idea for mobile specifically (due to keeping the radio alive and draining the battery). Again, no comments explaining why. [1] https://github.com/ex3ndr/telegram-mt/blob/master/src/main/j...
In Telegram - secure, free messaging

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.