#9964 LOW Not Tri: 1st boot shallow copy needs feedback

[Zarro Boogs per Child]

#9964: 1st boot shallow copy needs feedback
-----------------------------------+----------------------------------------
           Reporter:  rsmith       |       Owner:  cjb          
               Type:  enhancement  |      Status:  new          
           Priority:  low          |   Milestone:  Not Triaged  
          Component:  distro       |     Version:  not specified
         Resolution:               |    Keywords:               
        Next_action:  never set    |    Verified:  0            
Deployment_affected:               |   Blockedby:               
           Blocking:               |  
-----------------------------------+----------------------------------------

Comment(by Quozl):

 Yes, no user keys or passwords exist, so there is no existing supported
 use case for inbound SSH in ''our'' builds, though a deployment may choose
 to use it.

 Sugar and activities do not appear to require inbound or outbound SSH.

 Outbound SSH from Gnome Terminal is unaffected by absence of SSH host
 keys; tested on os105.  With AUTOCREATE_SERVER_KEYS set to NO build os105
 does not start sshd, quite expected, but there is an untidy console error
 if anybody is looking.

 Daniel mentioned that for XO-1 we tweaked sshd init to only generate rsa2
 keys.  A Fedora bug was opened, no movement on it.  I'm testing an
 identical change now for a local build.

 modules/base/kspost.10.core.inc:
 {{{
 # suppress generation of certain SSH host keys in
 # the same way we did it on XO-1 builds, so as to
 # reduce first boot time by several seconds (#9964)
 sed -i -e 's%\t\tdo_dsa%#\t\tdo_dsa%g' \
        -e 's%\t\tdo_rsa1%#\t\tdo_rsa1%g' \
        /etc/init.d/sshd
 }}}

-- 
Ticket URL: <http://dev.laptop.org/ticket/9964#comment:4>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system