updates.

[silc.git] / doc / draft-riikonen-silc-spec-03.nroff

diff --git a/doc/draft-riikonen-silc-spec-03.nroff b/doc/draft-riikonen-silc-spec-03.nroff
index d372e2cabd8d818f478e451356d42fa79d5466b0..d641b8bf1d1fb159180bb86a67c4b55833884f11 100644 (file)
--- a/doc/draft-riikonen-silc-spec-03.nroff
+++ b/doc/draft-riikonen-silc-spec-03.nroff
@@ -1953,9 +1953,9 @@ other external means for distributing the keys.  This applies for all
 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