margin: 0px 0 0 0;\r
}\r
\r
+small a, small a:visited {\r
+ color: #555;\r
+}\r
+\r
+small a:hover {\r
+ color: #777;\r
+}\r
+\r
code {\r
font-size: 18px;\r
}\r
}\r
}\r
\r
-@media screen and (min-height: 900px) {\r
+@media screen and (min-height: 930px) {\r
footer {\r
height:300px;\r
}\r
\r
@media screen and (max-width: 700px), screen and (max-height: 700px) {\r
#container {\r
- font-size: 50px;\r
+ font-size: 56px;\r
padding: 4% 0 80px;\r
}\r
#container2 {\r
- font-size: 46px;\r
+ font-size: 38px;\r
padding: 1% 0 10px;\r
}\r
body {\r
- font-size: 24px;\r
+ font-size: 22px;\r
}\r
code {\r
font-size: 16px;\r
padding: 4% 0 70px;\r
}\r
#container2 {\r
- font-size: 38px;\r
+ font-size: 36px;\r
padding: 1% 0 5px;\r
}\r
body {\r
- font-size: 22px;\r
+ font-size: 20px;\r
}\r
code {\r
font-size: 14px;\r
-bar
+SILC Client 1.1.10
+==================
+
+This version introduces a new default private message key protection
+method by auto-negotiating private message key with SILC Key Exchange
+protocol over the SILC network, client-to-client. The SKE is executed
+by encapsulating it inside private messages. SKE results into secret
+shared key between the two clients and all private messages are protected
+with that key. This provides complete end-to-end protection for private
+messages even if the SILC servers cannot be trusted.
+
+SILC Client will auto-negotiate the key when private message is sent
+for the first time. Both users will be prompted to accept each others
+public keys and once accpeted they are cached and subsequent verification
+will be done automatically. It is important to verify the public key
+to avoid the possibility of man-in-the-middle attacks.
+
+SILC Client automatically detects, within seconds, if the remote client
+does not support the new method. User will receive a notification on
+screen telling that the private messages will be protected using normal
+session keys instead. This may happen also if an error occurs during
+the key exchange protocol.
+
+This version also fixes numerous bugs that have been found using static
+analysis tools.
<![endif]-->
<header>
- <center><a href="http://silcnet.org/"><img src="img/silc.svg" height=64 alt="SILC logo"></a></center>
+ <center><a href="/"><img src="img/silc.svg" height=64 alt="SILC logo"></a></center>
</header>
<br />
</a>
<small>
- <a href="docs/client/ChangeLog">ChangeLog 2014-05-06</a> |
+ <a href="docs/client/ReleaseNotes">Release Notes 2014-05-06</a> |
<a href="client.html">Other versions</a>
</small>
</center>
<!-- Download -->
<center>
- <a href="http://silcnet.org/docs/release/SILC%20Client%201.1.8">SILC Client 1.1.20 Release Notes</a><br />
- <a href="http://silcnet.org/docs/changelog/SILC%20Client%201.1.8">SILC Client 1.1.20 Changes</a>
-
- <br /></br />
-
- <table width="40%" cellspacing="1" cellpadding="2" border="0">
- <tr>
- <td width="170"><b>Package</b></td>
- <td align="center"><b>Version</b></td>
- <td align="center"><b>URL</b></td>
- <td align="center"><b>SUM</b></td>
- </tr>
-
- <tr>
- <td>Source tar.gz</td>
- <td align="center"><a href="http://silcnet.org/docs/release/SILC%20Client%201.1.8">1.1.20</a></td>
- <td class="download-td" align="center"><a href="https://pidgin.im/download/windows/">HTTP</a></td>
- <td align="center"><a href="http://silcnet.org/download/client/sources/silc-client-1.1.20.tar.gz.sum">SHA512</a></td>
- </tr>
-
- <tr>
- <td>Pidgin Windows</td>
- <td align="center"><a href="https://developer.pidgin.im/wiki/ChangeLog">ChangeLog</a></td>
- <td class="download-td" align="center"><a href="https://pidgin.im/download/windows/">HTTP</a></td>
- <td align="center">N/A</td>
- </tr>
- </table>
-
</center>
<footer>
<nav>
-<!--
<a href="info.html">INFO</a>
<a href="client.html">CLIENT</a>
<a href="server.html">SERVER</a>
<a href="dev.html">DEVELOPMENT</a>
<a href="https://github.com/silc/silc/issues">ISSUES</a>
--->
</nav>
</footer>