Changes between Version 7 and Version 8 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-2
- Timestamp:
- 05/27/12 16:32:09 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-2
v7 v8 20 20 21 21 || '''Step''' || '''State''' || '''Date completed''' || '''Open Tickets''' || '''Closed Tickets/Comments''' || 22 || 1A || || || || ready to test||22 || 1A || [[Color(orange,Blocked)]] || || [exoticket:34] || blocked on information about bbn-hn configuration || 23 23 || 1B || || || || ready to test || 24 24 || 1C || || || || ready to test || … … 76 76 * Password-based SSH does not succeed 77 77 78 ==== Results of testing step 1A: 2012-05-27 ==== 79 80 * From the BBN internal network (128.89.68.0/23), with pubkey: 81 {{{ 82 $ ssh -o PubkeyAuthentication=yes chaos@bbn-hn.exogeni.gpolab.bbn.com 83 Last login: Sat May 26 14:41:55 2012 from capybara.bbn.com 84 ... 85 bbn-hn,[~],20:25(0)$ 86 }}} 87 * With password: 88 {{{ 89 $ ssh -o PubkeyAuthentication=no chaos@bbn-hn.exogeni.gpolab.bbn.com 90 chaos@bbn-hn.exogeni.gpolab.bbn.com's password: 91 Last login: Sun May 27 20:25:48 2012 from capybara.bbn.com 92 ... 93 bbn-hn,[~],20:27(0)$ 94 }}} 95 96 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. 97 78 98 === Step 1B: verify the absence of common unencrypted login protocols === 79 99