From: rmccabe@sourceware.org <rmccabe@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga/luci/docs user_manual.html
Date: 15 Jan 2007 20:33:00 -0000 [thread overview]
Message-ID: <20070115203300.1248.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: conga
Changes by: rmccabe at sourceware.org 2007-01-15 20:33:00
Modified files:
luci/docs : user_manual.html
Log message:
wording tweaks
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/luci/docs/user_manual.html.diff?cvsroot=cluster&r1=1.14&r2=1.15
--- conga/luci/docs/user_manual.html 2007/01/15 20:26:02 1.14
+++ conga/luci/docs/user_manual.html 2007/01/15 20:33:00 1.15
@@ -140,9 +140,9 @@
the datacenter systems can pretty safely be assumed to be trustworthy.
If a luci server is used to connect to systems across the open Internet,
the user <i>could</i> be vulnerable to a form of security attack known
- as a 'Man in the Middle' attack; wherein a hostile party sits between
- the client and server and intercepts any data exchanged while masquerading
- to its peers as a legitimate party.
+ as a 'Man in the Middle' attack; wherein a hostile party that sits between
+ the client and server intercepts data exchanged, while masquerading
+ to its peers as a legitimate party, and issues potentially malicious commands.
<p/>
If the user would like to verify the certificate of a ricci agent before
authenticating to it (avoiding a 'Man in the Middle' attack), the
next reply other threads:[~2007-01-15 20:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 20:33 rmccabe [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-25 19:27 [Cluster-devel] conga/luci/docs user_manual.html jparsons
2007-01-15 21:43 jparsons
2007-01-15 21:41 jparsons
2007-01-15 21:23 jparsons
2007-01-15 20:26 rmccabe
2007-01-15 20:03 jparsons
2007-01-15 19:57 rmccabe
2007-01-15 19:46 jparsons
2007-01-15 16:00 jparsons
2006-10-10 18:31 rmccabe
2006-10-09 5:47 jparsons
2006-09-26 13:35 jparsons
2006-09-26 12:36 jparsons
2006-09-26 12:12 jparsons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070115203300.1248.qmail@sourceware.org \
--to=rmccabe@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).