<p>
Protocol specification of SILC protocol is available for
-anyone to look at. There exists three Internet Drafts that has been
+anyone to look at. There exists four Internet Drafts that has been
submitted to <a href="http://www.ietf.org">IETF</a>.
See <a href="docs.html">documentation page</a> for more information.
<font size=4>
<p>
After checkout from CVS the SILC source tree must be prepared for
-configuration and compilation. To compile the source three, give,
+configuration and compilation. To compile the source tree, give,
<p>
<pre>
<font size=3>
<h2>SILC Protocol Internet Drafts</h2>
<p>
<font size=4>
-SILC Protocol is documented and three Internet Drafts exists. These
+SILC Protocol is documented and four Internet Drafts exists. These
Internet Drafts are also available from
<a href="http://www.ietf.org">IETF</a>.
<p>
-<b>Note: These drafts are already pretty much outdated. If you really need
-to know what is happening in the protocol designing I suggest checking out
-the drafts from the CVS. They are updated constantly.</b>
-<p>
<li>Secure Internet Live Conferencing (SILC), Protocol Specification
<p>
Abstract
<p>
-This memo describes a Secure Internet Live Conferencing (SILC)
-protocol which provides secure conferencing services over insecure
-network channel. SILC is IRC [IRC] like protocol, however, it is
-not equivalent to IRC and does not support IRC. Strong cryptographic
-methods are used to protect SILC packets inside SILC network. Two
-other Internet Drafts relates very closely to this memo; SILC Packet
-Protocol [SILC2] and SILC Key Exchange and Authentication Protocols
-[SILC3].
-<p>
-<a href="docs/draft-riikonen-silc-spec-01.txt">
-draft-riikonen-silc-spec-01.txt</a>
+ This memo describes a Secure Internet Live Conferencing (SILC)
+ protocol which provides secure conferencing services over insecure
+ network channel. SILC is IRC [IRC] like protocol, however, it is
+ not equivalent to IRC and does not support IRC. Strong cryptographic
+ methods are used to protect SILC packets inside the SILC network.
+ Three other Internet Drafts relates very closely to this memo;
+ SILC Packet Protocol [SILC2], SILC Key Exchange and Authentication
+ Protocols [SILC3] and SILC Commands [SILC4].
+<p>
+<a href="docs/draft-riikonen-silc-spec-02.txt">
+draft-riikonen-silc-spec-02.txt</a>
<p><br>
<li>SILC Packet Protocol
<p>
Abstract
<p>
-This memo describes a Packet Protocol used in the Secure Internet Live
-Conferencing (SILC) protocol specified in the Secure Internet Live
-Conferencing, Protocol Specification Internet Draft [SILC1]. This
-protocol describes the packet types and packet payloads which defines
-the contents of the packets. The protocol provides secure binary packet
-protocol that assures that the contents of the packets are secured and
-authenticated.
+ This memo describes a Packet Protocol used in the Secure Internet Live
+ Conferencing (SILC) protocol, specified in the Secure Internet Live
+ Conferencing, Protocol Specification Internet Draft [SILC1]. This
+ protocol describes the packet types and packet payloads which defines
+ the contents of the packets. The protocol provides secure binary packet
+ protocol that assures that the contents of the packets are secured and
+ authenticated.
<p>
-<a href="docs/draft-riikonen-silc-pp-01.txt">
-draft-riikonen-silc-pp-01.txt</a>
+<a href="docs/draft-riikonen-silc-pp-02.txt">
+draft-riikonen-silc-pp-02.txt</a>
<p><br>
<li>SILC Key Exchange and Authentication Protocols
<p>
Abstract
<p>
-This memo describes two protocols used in the Secure Internet Live
-Conferencing (SILC) protocol specified in the Secure Internet Live
-Conferencing, Protocol Specification internet-draft [SILC1]. The
-SILC Key Exchange (SKE) protocol provides secure key exchange between
-two parties resulting into shared secret key material. The protocol
-is based on Diffie Hellman key exchange algorithm and its functionality
-is derived from several key exchange protocols. SKE uses best parts
-of the SSH2 Key Exchange protocol, Station-To-Station (STS) protocol
-and the OAKLEY Key Determination protocol [OAKLEY].
-<p>
-The SILC Connection Authentication protocol provides user level
-authentication used when creating connections in SILC network. The
-protocol is transparent to the authentication data which means that it
-can be used to authenticate the user with, for example, passphrase
-(pre-shared- secret) or public key (and certificate).
-<p>
-<a href="docs/draft-riikonen-silc-ke-auth-01.txt">
-draft-riikonen-silc-ke-auth-01.txt</a>
+ This memo describes two protocols used in the Secure Internet Live
+ Conferencing (SILC) protocol, specified in the Secure Internet Live
+ Conferencing, Protocol Specification internet-draft [SILC1]. The
+ SILC Key Exchange (SKE) protocol provides secure key exchange between
+ two parties resulting into shared secret key material. The protocol
+ is based on Diffie-Hellman key exchange algorithm and its functionality
+ is derived from several key exchange protocols. SKE uses best parts
+ of the SSH2 Key Exchange protocol, Station-To-Station (STS) protocol
+ and the OAKLEY Key Determination protocol [OAKLEY].
+<p>
+ The SILC Connection Authentication protocol provides user level
+ authentication used when creating connections in SILC network. The
+ protocol is transparent to the authentication data which means that it
+ can be used to authenticate the user with, for example, passphrase
+ (pre-shared-secret) or public key (and certificate).
+<p>
+<a href="docs/draft-riikonen-silc-ke-auth-02.txt">
+draft-riikonen-silc-ke-auth-02.txt</a>
+<p><br>
+
+<li>SILC Commands
+<p>
+Abstract
+<p>
+ This memo describes the commands used in the Secure Internet Live
+ Conferencing (SILC) protocol, specified in the Secure Internet Live
+ Conferencing, Protocol Specification Internet Draft [SILC1]. The
+ SILC Commands are very important part of the SILC protocol. Usually
+ the commands are used by SILC clients to manage the SILC session, but
+ also SILC servers may use the commands. This memo specifies detailed
+ command messages and command reply messages.
+<p>
+<a href="docs/draft-riikonen-silc-commands-00.txt">
+draft-riikonen-silc-commands-00.txt</a>
<p><br>
</td>
<h1>Download SILC</h1>
<p>
<font size=4>
-The latest SILC release is version 20010413. Please, read the README
+The latest SILC release is version 0.1. Please, read the README
and INSTALL files after downloading for instructions how to install and
use SILC.
<p>
<p>
<h3>Main Download</h3>
<p>
-Sources HTTP: <a href="http://silcnet.org/silc-20010413.tar.gz">
-tar.gz</a> (1820 KB), <a href="http://silcnet.org/silc-20010413.tar.bz2">
+Sources HTTP: <a href="http://silcnet.org/silc-0.1.tar.gz">
+tar.gz</a> (1820 KB), <a href="http://silcnet.org/silc-0.1.tar.bz2">
tar.bz2</a> (1448 KB)
<br>
-Sources FTP: <a href="ftp://silc.pspt.fi/pub/silc/snapshots/">tar.gz
+Sources FTP: <a href="ftp://silc.pspt.fi/pub/silc/">tar.gz
(1820 KB)</a>
<p>
<h3>Other packages</h3>
<li>Normal conferencing services such as private messages, channels,
channel messages, etc. All traffic is secured and authenticated.
<p>
-<li>No unique nicknames. There can same nicknames in SILC without
+<li>No unique nicknames. There can be same nicknames in SILC without
collisions. SILC has unique Client ID's, Server ID's and Channel ID's
- to assure that there are no collisions.
+ to assure that there are no collisions. The maximum length of the
+ nickname is 128 characters. The maximum length of the channel name
+ is 256 characters.
+<p>
+<li>Channels can have channel operators and a channel founder which is the
+ client who created the channel. Channel founder privileges supersedes
+ the channel operator privileges. Also, channel founder privileges
+ may be regained even if the founder leaves the channel. The
+ requirement for this is that the client is connected to the same
+ server it was originally connected. The channel founder cannot
+ be removed from the channel by force.
+<p>
+<li>Channel messages are protected by channel key, generated by the
+ server. The key is re-generated once in an hour. It is
+ possible to set a private key for the channel so that even the
+ servers does not know the key. Actually, it is possible to set
+ several private keys so that only specific users on the channel may
+ decrypt some specific messages. Adding the private key significantly
+ increases the security as nobody else but the users on the channel
+ knows the key.
+<p>
+<li>Private messages are protected using the session keys, generated
+ when connecting to the server. This means that the private messages
+ are decrypted and re-encrypted enroute to the true receiver of the
+ message. However, it is possible to set a private key between two
+ clients and protect the private messages with that key. In this case
+ no server enroute can decrypt the message since they don't have
+ the key. The SILC protocol provides an automatic key negotiation
+ between two clients using the SKE protocol. This makes it very
+ easy to negotiate a shared secret key with another client in the
+ network.
+<p>
+<li>All the other traffic, like commands between client and the server
+ are protected using the session keys. Session keys are re-generated
+ once in an hour. The re-key may be done with or without the PFS
+ (Perfect Forward Secrecy).
<p>
<li>Secure key exchange and authentication protocol. SILC Key Exchange
- protocol provides key material used in the SILC sessions in secure
- manner. The protocol is immune for example to man-in-the-middle
- attacks. The SILC Authentication protocol provides strong
+ (SKE) protocol provides key material used in the SILC sessions in
+ secure manner. The protocol is immune for example to man-in-the-middle
+ attacks and is based on the Diffie-Hellman key exchange algorithm. The
+ SILC Authentication protocol provides strong
authentication. Authentication may be based on passphrase or public
key (RSA) authentication. For clients there is an option not to
use authentication when connecting to servers.
<p>
<li>All traffic is encrypted and authenticated using the best cryptographic
- algorithms out there. Command messages, private messages and channel
- messages are all protected by encryption. User can set private keys
- for both private message and for channels so that even SILC servers do
- not know the keys. Cipher keys are, by default, 128 bits in length and
+ algorithms out there. Cipher keys are, by default, 256 bits in length and
public keys, by default, 1024 bits in length.
<p>
<li>Supports the following ciphers: AES, Twofish, Blowfish, Mars,
<tr><td>
<font face="Arial,Helvetica,Sans-serif">
<div style="margin-left: 20px">
-<center><h2>SILC 20010413 Beta Version Available</h2></center>
+<center><h2>SILC 0.1 Is Now Available!</h2></center>
<center>
<font size=4>
-The new Beta version 20010413 of SILC is available for testing.
+The new Beta version 0.1 of SILC is available for testing.
Read the README and INSTALL files after downloading for instructions how
to compile and use SILC. Report bugs to the
<a href="lists.html">SILC development mailing list.</a>
server linked to the new router on silc.pspt.fi contact
<a href="mailto:priikone.NOSPAM@poseidon.pspt.fi">me</a> now.</h3>
<p>
-Download: <a href="download.html">SILC 20010413 Beta Version</a>
+Download: <a href="download.html">SILC 0.1 Beta Version</a>
<br>
-Changes: <a href="changes.txt">SILC 20010413 Changes</a>
+Changes: <a href="changes.txt">SILC 0.1 Changes</a>
<p>
</center>
<p><br>
projects / silc.git / commitdiff