updates.

diff --git a/TODO b/TODO
index 15318131b9dfeee451ccfe512e9ee63ba33b03da..1d5f3a69a4ed8b2250c102941de176f167e1489e 100644 (file)
--- a/TODO
+++ b/TODO
@@ -19,8 +19,6 @@ TODO for SILC Server 1.0
 TODO/bugs In SILC Libraries
 ===========================
 
- o Remove the old private key file format support in silcpkcs.c.
-
  o Test cases for all cryptographic primitive in lib/silccrypt/
 
  o Test cases for all payload encoding and decoding routins in lib/silccore/

diff --git a/apps/irssi/docs/help/in/smsg.in b/apps/irssi/docs/help/in/smsg.in
index 6c6318d8050e3948c2c9519eae215308d2ce60e6..86d3fb19e92a7b609d36cbf44072ee7e6cd3fc95 100644 (file)
--- a/apps/irssi/docs/help/in/smsg.in
+++ b/apps/irssi/docs/help/in/smsg.in
@@ -19,7 +19,7 @@ or [F] if the signature verificationn failed.  If you do not have
 the sender's public key you can fetch it with GETKEY command.
 
 If you don't want to verify the signatures from received messages
-you may do /SET ignore_messages_signatures on.  In this case
+you may do /SET ignore_message_signatures on.  In this case
 signatures in messages are ignored and they appear as normal
 non-signed messages.  By default, all message signatures are
 verified.

diff --git a/doc/silc.yo b/doc/silc.yo
index 3247e11d0db5dba8c7835dcf43a58c033a68d125..726b0a70eafeb8d5ee8cce7bda70a8164b92e039 100644 (file)
--- a/doc/silc.yo
+++ b/doc/silc.yo
@@ -1,4 +1,4 @@
-manpage(SILC) (1) (October 31 2002) (silc-client) (silc-client)
+manpage(SILC) (1) (December 7 2002) (silc-client) (silc-client)
 
 
 manpagename(silc) (client for SILC, a secure and flexible conferencing network)
@@ -16,11 +16,12 @@ the SILC network.  The silc client resembles IRC clients to make the
 using easier for new users.
 
 bf(Silc) supports sending of practically any kind of messages in addition
-of normal text messages in the SILC network.  The session to SILC server
+of normal text messages in the SILC network.  This includes multimedia
+messages like images, video and audio stream.  The session to SILC server
 is secured with session key, channel messages are protected with channel
 key and private messages with session keys.  It is also possible to use
 private channel keys and private message keys in addition to server
-generated keys.
+generated keys.  It is also possible to digitally sign all messages.
 
 bf(Silc) supports em(passphrase) authentication and public key authentication
 based on em(digital signatures), when connecting to SILC server.  bf(Silc)