2 <body bgcolor="#ffffff">
4 <a href="index.html"><img src="silc2.jpg" border=0></a>
5 <table width="70%" border="0" cellspacing="0" cellpadding="1"
14 Features to be included into the final release of SILC. [Note that the
15 current Developer's Version does not include all of these features, read
16 TODO file for more information.]
19 <li>Normal conferencing services such as private messages, channels,
20 channel messages, etc. All traffic is secured and authenticated.
22 <li>No unique nicknames. There can same nicknames in SILC without
23 collisions. SILC has unique Client ID's, Server ID's and Channel ID's
24 to assure that there are no collisions.
26 <li>Secure key exchange and authentication protocol. SILC Key Exchange
27 protocol provides key material used in the SILC sessions in secure
28 manner. The protocol is immune for example to man-in-the-middle
29 attacks. The SILC Authentication protocol provides strong
30 authentication. Authentication may be based on passphrase or public
31 key (RSA) authentication. For clients there is an option not to
32 use authentication when connecting to servers.
34 <li>All traffic is encrypted and authenticated using the best cryptographic
35 algorithms out there. Command messages, private messages and channel
36 messages are all protected by encryption. User can set private keys
37 for both private message and for channels so that even SILC servers do
38 not know the keys. Cipher keys are, by default, 128 bits in length and
39 public keys, by default, 1024 bits in length.
41 <li>Supports data compression with GZIP to improve performance.
43 <li>SIM (SILC Module) support. Support for loading of shared objects at
44 run-time that provides new and extended features to both SILC client
45 and server. These can provide extra ciphers and extra features to
48 <li>SILC client can be installed and used without root privileges.
50 <li>SILC client can be configured by system wide configuration files but
51 with user specific configuration files as well.