From b2a82a6ddb182473355f1444575ce793c07eb4a2 Mon Sep 17 00:00:00 2001 From: Pekka Riikonen Date: Sat, 7 Dec 2002 13:27:18 +0000 Subject: [PATCH] updates. --- TODO | 2 -- apps/irssi/docs/help/in/smsg.in | 2 +- doc/silc.yo | 7 ++++--- 3 files changed, 5 insertions(+), 6 deletions(-) diff --git a/TODO b/TODO index 15318131..1d5f3a69 100644 --- 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 6c6318d8..86d3fb19 100644 --- 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 3247e11d..726b0a70 100644 --- 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) -- 2.43.0