From: Pekka Riikonen Date: Sun, 12 Nov 2000 20:27:27 +0000 (+0000) Subject: updates X-Git-Tag: SILC.0.1~323 X-Git-Url: http://git.silcnet.org/gitweb/?a=commitdiff_plain;h=d20084bc247dd2d512590cf720f9c0fda8f5c7e1;p=silc.git updates --- diff --git a/doc/draft-riikonen-silc-ke-auth-01.nroff b/doc/draft-riikonen-silc-ke-auth-01.nroff index 8f71edce..97241e8c 100644 --- a/doc/draft-riikonen-silc-ke-auth-01.nroff +++ b/doc/draft-riikonen-silc-ke-auth-01.nroff @@ -994,7 +994,10 @@ defined: 4 Security Considerations Security is central to the design of this protocol, and these security -considerations permeate the specification. +considerations permeate the specification. Common security considerations +such as keeping private keys truly private and using adequate lengths for +symmetric and asymmetric keys must be followed in order to maintain the +security of this protocol. .ti 0 diff --git a/doc/draft-riikonen-silc-pp-01.nroff b/doc/draft-riikonen-silc-pp-01.nroff index 2e3527f1..2ca38888 100644 --- a/doc/draft-riikonen-silc-pp-01.nroff +++ b/doc/draft-riikonen-silc-pp-01.nroff @@ -2491,7 +2491,10 @@ and additional documents on the issue may be written. 3 Security Considerations Security is central to the design of this protocol, and these security -considerations permeate the specification. +considerations permeate the specification. Common security considerations +such as keeping private keys truly private and using adequate lengths for +symmetric and asymmetric keys must be followed in order to maintain the +security of this protocol. .ti 0 diff --git a/doc/draft-riikonen-silc-spec-01.nroff b/doc/draft-riikonen-silc-spec-01.nroff index 33555f1a..5410afdb 100644 --- a/doc/draft-riikonen-silc-spec-01.nroff +++ b/doc/draft-riikonen-silc-spec-01.nroff @@ -3165,7 +3165,10 @@ List of all defined command status messages following. 6 Security Considerations Security is central to the design of this protocol, and these security -considerations permeate the specification. +considerations permeate the specification. Common security considerations +such as keeping private keys truly private and using adequate lengths for +symmetric and asymmetric keys must be followed in order to maintain the +security of this protocol. .ti 0