<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Iran Hackers Just Cracked Telegram&#8217;s Encrypted Messaging Code &#8211; Fortune</title>
	<atom:link href="http://www.epanorama.net/blog/2016/08/03/iran-hackers-just-cracked-telegrams-encrypted-messaging-code-fortune/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2016/08/03/iran-hackers-just-cracked-telegrams-encrypted-messaging-code-fortune/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Mon, 27 Apr 2026 21:44:28 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2016/08/03/iran-hackers-just-cracked-telegrams-encrypted-messaging-code-fortune/comment-page-1/#comment-1503070</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 03 Aug 2016 05:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=44764#comment-1503070</guid>
		<description><![CDATA[Telegram:
Telegram says only publicly available data collected in attack on Telegram in Iran, accounts not accessed

Keep Calm and Send Telegrams!
https://telegram.org/blog/15million-reuters

Certain people checked whether some Iranian numbers were registered on Telegram and were able to confirm this for 15 million accounts. As a result, only publicly available data was collected and the accounts themselves were not accessed. 

However, since Telegram is based on phone contacts, any party can potentially check whether a phone number is registered in the system. This is also true for any other contact-based messaging app (WhatsApp, Messenger, etc.).

SMS codes

As for the reports that several accounts were accessed earlier this year by intercepting SMS-verification codes, this is hardly a new threat as we&#039;ve been increasingly warning our users in certain countries about it. Last year we introduced 2-Step Verification specifically to defend users in such situations.

If you have reasons to think that your mobile carrier is intercepting your SMS codes, use 2-Step Verification to protect your account with a password. If you do that, there&#039;s nothing an attacker can do.]]></description>
		<content:encoded><![CDATA[<p>Telegram:<br />
Telegram says only publicly available data collected in attack on Telegram in Iran, accounts not accessed</p>
<p>Keep Calm and Send Telegrams!<br />
<a href="https://telegram.org/blog/15million-reuters" rel="nofollow">https://telegram.org/blog/15million-reuters</a></p>
<p>Certain people checked whether some Iranian numbers were registered on Telegram and were able to confirm this for 15 million accounts. As a result, only publicly available data was collected and the accounts themselves were not accessed. </p>
<p>However, since Telegram is based on phone contacts, any party can potentially check whether a phone number is registered in the system. This is also true for any other contact-based messaging app (WhatsApp, Messenger, etc.).</p>
<p>SMS codes</p>
<p>As for the reports that several accounts were accessed earlier this year by intercepting SMS-verification codes, this is hardly a new threat as we&#8217;ve been increasingly warning our users in certain countries about it. Last year we introduced 2-Step Verification specifically to defend users in such situations.</p>
<p>If you have reasons to think that your mobile carrier is intercepting your SMS codes, use 2-Step Verification to protect your account with a password. If you do that, there&#8217;s nothing an attacker can do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2016/08/03/iran-hackers-just-cracked-telegrams-encrypted-messaging-code-fortune/comment-page-1/#comment-1503066</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 03 Aug 2016 05:26:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=44764#comment-1503066</guid>
		<description><![CDATA[NIST declares the age of SMS-based 2-factor authentication over
http://www.epanorama.net/newepa/2016/07/27/nist-declares-the-age-of-sms-based-2-factor-authentication-over-techcrunch/

NIST blog clarifies SMS deprecation in wake of media tailspin
http://www.epanorama.net/newepa/2016/07/31/nist-blog-clarifies-sms-deprecation-in-wake-of-media-tailspin-zdnet/]]></description>
		<content:encoded><![CDATA[<p>NIST declares the age of SMS-based 2-factor authentication over<br />
<a href="http://www.epanorama.net/newepa/2016/07/27/nist-declares-the-age-of-sms-based-2-factor-authentication-over-techcrunch/" rel="nofollow">http://www.epanorama.net/newepa/2016/07/27/nist-declares-the-age-of-sms-based-2-factor-authentication-over-techcrunch/</a></p>
<p>NIST blog clarifies SMS deprecation in wake of media tailspin<br />
<a href="http://www.epanorama.net/newepa/2016/07/31/nist-blog-clarifies-sms-deprecation-in-wake-of-media-tailspin-zdnet/" rel="nofollow">http://www.epanorama.net/newepa/2016/07/31/nist-blog-clarifies-sms-deprecation-in-wake-of-media-tailspin-zdnet/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
