1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Quirks with ssh and wep keys

Discussion in 'Tomato Firmware' started by geoffc, Nov 8, 2008.

  1. geoffc

    geoffc Addicted to LI Member

    Hi all,

    I'm having trouble logging in via ssh; can't use a password or RSA/DSA public keys. Just to make sure I'm doing it right, what user name should I use? Any other tips? (I think I have the ports set correctly.

    Second question, I generate my WEP keys (I know, I know, but I have some older devices that don't have WPA). The hex keys it generates are totally different from the keys generated from Windows, OS X, or anything else. I have to type the hex keys manually in the clients for them to connect. Any idea why Tomato isn't generating keys in a standard way?

    Thanks!
     
  2. geoffc

    geoffc Addicted to LI Member

    Hmm, something from the log files (don't know if it's related):

    Code:
    tomato authpriv.warn dropbear[5446]: Failed reading '/etc/dropbear/dropbear_dss_host_key', disabling DSS
    Also, for both my regular user (for which I submitted the public key), and the user admin (ssh "admin@myrouter.mydomain.net[/email]) get an error of
    Code:
    login attempt for nonexistent user" in the log.
     
  3. fyellin

    fyellin LI Guru Member

    For ssh, you must log in as "root", not "admin".
     
  4. fyellin

    fyellin LI Guru Member

    I don't think there is such a thing as "the standard way." In my experience, Linksys has done it different from Windows has done it differently from Apple. Stick to hex.
     
  5. geoffc

    geoffc Addicted to LI Member

    Bingo, root did it. Thanks! I'm not used to using root as an ssh user.

    Thanks!
     

Share This Page