From: jparsons@sourceware.org <jparsons@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga/luci/docs user_manual.html
Date: 15 Jan 2007 19:46:06 -0000 [thread overview]
Message-ID: <20070115194606.480.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: conga
Changes by: jparsons at sourceware.org 2007-01-15 19:46:05
Modified files:
luci/docs : user_manual.html
Log message:
user manual updates for cert ui, parte un
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/luci/docs/user_manual.html.diff?cvsroot=cluster&r1=1.10&r2=1.11
--- conga/luci/docs/user_manual.html 2007/01/15 16:00:48 1.10
+++ conga/luci/docs/user_manual.html 2007/01/15 19:46:05 1.11
@@ -109,7 +109,7 @@
module support to filter and retrieve log entries. <p/>
To add a system, click on the Add a System link in the left hand navigation
table. This will load the following page:
- <img src="./ss_homebase2.png"/><br/>
+ <img src="./addsys_11.png"/><br/>
<b>Figure #3: Add a System</b>
<p/>
<p/>
@@ -120,18 +120,44 @@
one additional entry row has been provided, a checkbox is also made available
that can be selected if all systems specified for addition to the luci server
share the same password.
- <img src="./ss_homebase3.png"/><br/>
+ <img src="./addsys_22.png"/><br/>
<b>Figure #4: Multiple System Entries</b>
<p/>
<p/>
If the System Hostname is left blank for any row, it is disregarded when the
- list of systems is submitted for addition. If systems in the list of rows do
+ list of systems is submitted for addition. If the user wishes to delete a
+ row for any reason, the icon at the far right of the row (that resembles
+ rows in a table with an 'x') can be clicked. If systems in the list of rows do
NOT share the same password (and the checkbox is, of course, left unchecked)
and one or more passwords are incorrect, an error message is generated for
each system that has an incorrect password. The systems listed with correct
passwords are added to the luci server. In addition to incorrect password
problems, an error message is also displayed if luci is unable to connect to
- the ricci agent on a system. Finally, if a system is entered on the form for
+ the ricci agent on a system.
+ <p/>
+ For most typical datacenter deployments of conga, the luci server will
+ reside on a system within the confines of the datacenter network, and
+ 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 assault known
+ as the 'Man in the Middle' attack; wherein a hostile party spoofs the
+ hostname or ip adress of a system to be added to a luci server.
+ <p/>
+ If the user would like to verify the certificate of a ricci agent before
+ authenticating to it (avoiding a 'Man in the Middle' form of attack), the
+ checkbox marked <b>Verify system certificates before sending any
+ passwords</b> should be checked. With this box checked, clicking submit
+ retrieves the certificate information for all systems listed, and provides
+ a 'Trust' checkbox for each system. The password for a system will not
+ be sent without the trust box checked. To add the system or systems,
+ click the 'Trust' checkboxes for each row desited and click submit again.
+ Mousing over the lock icon for
+ a row entry will display the certificate information for just that system.
+ <p/>
+ <img src="./addsys_33.png"/><br/>
+ <b>Figure #5: Certificate Verification Page</b>
+ <p/>
+ Finally, if a system is entered on the form for
addition and it is ALREADY being managed by the luci server, the system is not added
again (but, the administrator is informed via an error message).<p/>
next reply other threads:[~2007-01-15 19:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 19:46 jparsons [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:33 rmccabe
2007-01-15 20:26 rmccabe
2007-01-15 20:03 jparsons
2007-01-15 19:57 rmccabe
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=20070115194606.480.qmail@sourceware.org \
--to=jparsons@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).