From a7374334f9e1db1bae761aa426acfcc5d913554e Mon Sep 17 00:00:00 2001 From: Pekka Riikonen Date: Thu, 8 May 2014 18:38:50 +0200 Subject: [PATCH] updates. --- css/main.css | 2 +- docs/toolkit/ReleaseNotes | 37 +++++++++++++++++++++++++++++++++++++ 2 files changed, 38 insertions(+), 1 deletion(-) create mode 100644 docs/toolkit/ReleaseNotes diff --git a/css/main.css b/css/main.css index 7cb1c50..c3ef321 100644 --- a/css/main.css +++ b/css/main.css @@ -145,7 +145,7 @@ code { } .list { - width: 70%; + width: 65%; text-align: left; font-size: 80%; } diff --git a/docs/toolkit/ReleaseNotes b/docs/toolkit/ReleaseNotes new file mode 100644 index 0000000..03d42cb --- /dev/null +++ b/docs/toolkit/ReleaseNotes @@ -0,0 +1,37 @@ +SILC Toolkit 1.1.11 +=================== + +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 Library 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. + +SILC Client Library 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 feature is totally transparent and applications usually will not +require any changes to get it working. For most cases it should work +out of the box without modifications to the application. + +This version also adds a new say() client operation associated context +which can be fetched from the SilcClientConnection entry. The associated +context can be SilcClientEntry, SilcChannelEntry or SilcServerEntry and +is meant to allow application to better target the say() operation. + +This version also enables higher security message payloads by including +the Client Ids in the MAC computation. Support for this has existed for +long time but it is now finally enabled. + +This version also adds various improvement to the SILC Key Exchange +Library and the SILC Core Library. -- 2.24.0