2/3     Speaking of ssh, could soda admins generate  new 'n fixed ssh host
        keys so that we don't have to edit our known_hosts file every time
        soda is switched from openssh to commerical ssh1 and then back to
        openssh?
        \_ They could.  I hope they have better things to do or you'd just
           ignore the errors like everyone else.
           \_ It is pretty time consuming to copy a file. I give you that.
           \_ I ssh to soda from about seven different systems. It is
              kind of annoying to have to update known_hosts file on all of
              them whenever soda admins change their mind about which version
              of sshd to run. -original poster
        \_ we should just have the ssh1 ssh2 and openssh binaries each of
           which get called after a  case statement depending on /dev/rand
           then tom can bitch all he wants, and he will be a happy tom.
        \_ redhat 7.1 uses SSH Version OpenSSH_2.3.0p1
           \_ And your point is? I was not advocating using one implementation
              of ssh or another. What I say is that the soda admins should
              generate new ssh host keys so that people's clients don't
              compalain every time sshd is switched to openssh and then
              back to data fellows ssh1. The current keys are 1023bit and
              the sshd1 fails to acknowledge that.