Changes between Version 7 and Version 8 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-2

Timestamp:

05/27/12 16:32:09 (12 years ago)

Author:

chaos@bbn.com

Comment:

--

GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-2

@@ -20 +20 @@
 
 || '''Step''' || '''State'''               || '''Date completed''' || '''Open Tickets''' || '''Closed Tickets/Comments'''                              ||
-|| 1A         ||                           ||                      ||                    || ready to test                                              ||
+|| 1A         || [[Color(orange,Blocked)]] ||                      || [exoticket:34]     || blocked on information about bbn-hn configuration ||
 || 1B         ||                           ||                      ||                    || ready to test                                              ||
 || 1C         ||                           ||                      ||                    || ready to test                                              ||
@@ -76 +76 @@
  * Password-based SSH does not succeed
 
+==== Results of testing step 1A: 2012-05-27 ====
+
+ * From the BBN internal network (128.89.68.0/23), with pubkey:
+{{{
+$ ssh -o PubkeyAuthentication=yes chaos@bbn-hn.exogeni.gpolab.bbn.com
+Last login: Sat May 26 14:41:55 2012 from capybara.bbn.com
+...
+bbn-hn,[~],20:25(0)$ 
+}}}
+ * With password:
+{{{
+$ ssh -o PubkeyAuthentication=no chaos@bbn-hn.exogeni.gpolab.bbn.com
+chaos@bbn-hn.exogeni.gpolab.bbn.com's password: 
+Last login: Sun May 27 20:25:48 2012 from capybara.bbn.com
+...
+bbn-hn,[~],20:27(0)$ 
+}}}
+
+I opened exoticket:34 to request explanation of the protection mechanisms on bbn-hn, so i can redo this test and verify that they work and seem likely to be sufficient.
+
 === Step 1B: verify the absence of common unencrypted login protocols ===