mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2024-11-28 19:23:11 +01:00
Update content of files
This commit is contained in:
parent
80ae5384cb
commit
f378a64f05
1 changed files with 5 additions and 1 deletions
|
@ -86,7 +86,7 @@
|
|||
<p><strong>Security researchers</strong> are welcome to submit any issues they find in the Telegram <strong>apps</strong> or <strong>protocol</strong> to us at <strong>security@telegram.org</strong>. All submissions which result in a change of code or configuration are eligible for bounties, ranging from <strong>$500</strong> to <a href="https://telegram.org/blog/crowdsourcing-a-more-secure-future"><strong>$100,000</strong></a> or more, depending on the severity of the issue.</p>
|
||||
</blockquote>
|
||||
<p>The current round of our <a href="/blog/cryptocontest">contest to crack Telegram’s encryption</a> ends with no winners. Despite the <strong>$300,000</strong> bounty and the fact that contestants could act as the Telegram server passing info between the users (i.e. use any kinds of active attacks, manipulate traffic etc.) no one could decipher their Secret Chats by the beginning of February. </p>
|
||||
<p>To demonstrate that the contest was fair, we‘ve added a decryption method to the contest bot’s list of commands – <strong>KEY</strong>. <strong>KEY</strong> returns the 256-byte encryption key used in the secret chat, so the task of the contest is now easily achieved. </p>
|
||||
<p>To demonstrate that the contest was fair, we've added a decryption method to the contest bot's list of commands – <strong>KEY</strong>. <strong>KEY</strong> returns the 256-byte encryption key used in the secret chat, so the task of the contest is now easily achieved. </p>
|
||||
<h4><a class="anchor" name="why-are-contests-important" href="#why-are-contests-important"><i class="anchor-icon"></i></a>Why are contests important?</h4>
|
||||
<p>One of the reasons we trust Telegram’s Secret Chats more than many of their alternatives, is that they're open to scrutiny from the world’s security experts. And while having <a href="/apps">open source apps</a> and a <a href="/api">well documented API</a> makes this kind of scrutiny possible, it is our contests that create incentive for it.</p>
|
||||
<p>That’s why we will definitely launch the next round of our contest later this year. It’ll take us some time to determine whether we can further simplify the task for the contestants. Once ready, we’ll announce the new round on <a href="https://twitter.com/telegram">Twitter</a>. </p>
|
||||
|
@ -94,6 +94,10 @@
|
|||
<div><br></div>
|
||||
|
||||
<p><em>February 11, 2015<br>The Telegram Team</em></p>
|
||||
<blockquote>
|
||||
<p>This contest is over, but Telegram's <strong>bug bounty program</strong> is always open.</p>
|
||||
<p><strong>Security researchers</strong> are welcome to submit any issues they find in the Telegram <strong>apps</strong> or <strong>protocol</strong> to us at <strong>security@telegram.org</strong>. All submissions which result in a change of code or configuration are eligible for bounties, ranging from <strong>$500</strong> to <a href="https://telegram.org/blog/crowdsourcing-a-more-secure-future"><strong>$100,000</strong></a> or more, depending on the severity of the issue.</p>
|
||||
</blockquote>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
|
Loading…
Reference in a new issue