.ds RF FORMFEED[Page %]
.ds CF
.ds LH Internet Draft
-.ds RH 22 July 2001
+.ds RH 21 August 2001
.ds CH
.na
.hy 0
.nf
Network Working Group P. Riikonen
Internet-Draft
-draft-riikonen-silc-spec-03.txt 22 July 2001
-Expires: 22 January 2002
+draft-riikonen-silc-spec-03.txt 21 August 2001
+Expires: 21 February 2002
.in 3
messages, private messages and channel messages. It is important to note
that SILC, like any other security protocol is not full proof system and
cannot secure from insecure environment; the SILC servers and routers could
-very well be hacked. However, to provide acceptable level of security and
-usability for end user the protocol uses many times session keys or other
-keys generated by the servers to secure the messages. If this is
+very well be compromised. However, to provide acceptable level of security
+and usability for end user the protocol uses many times session keys or
+other keys generated by the servers to secure the messages. If this is
unacceptable for the client or end user, the private keys negotiatied
outside the SILC Network should always be used. In the end it is always
implementor's choice whether to negotiate private keys by default or
Requirement Levels", BCP 14, RFC 2119, March 1997.
-
-
-
-
.ti 0
7 Author's Address
EMail: priikone@silcnet.org
-This Internet-Draft expires 22 January 2002
+This Internet-Draft expires 21 February 2002