Results 1 to 5 of 5
  1.    #1  
    Lets start at the beginning.

    When I first installed SSH, that was some time ago. That was when password based logins were enabled.
    Then when the updated version came out thru Preware, I jumped on it and instaslled them.
    I finally managed to get the ssh keys version working after a lot of work (issues with PuTTY).
    Then after a few days, my SSH keys stopped working. I figured there were traces of the original optware ssh on my phone, so I doctored it using the 1.3.1 WebOS Doctor (11/21).

    Then, I installed all of the software in the required order through Preware and everything worked fine. Then less than a week later, I cannot get in through SSH. I know that it happened after 11/25 because I installed Precorder on that date.

    The public key (I generated and put in /var/home/root/.ssh/authorized_keys) is the same as the one on my computer and it matched my private key. I have verified this through the Terminal app on my Pre.

    PuTTY gives me the error "Server refused our key" and "Disconnected: No supported authentication methods available."

    I really need SSH working for several reasons and do not feel like doctoring my pre every 5 days to get it working. Does anyone here know why this happens?
    Arthur Thornton

    Former webOS DevRel Engineer at Palm, HP, and LG
    Former webOS app developer (built Voice Memos, Sparrow, and several homebrew apps and patches)
    Former blogger for webOS Nation and webOS Roundup
  2. nullr's Avatar
    Posts
    136 Posts
    Global Posts
    152 Global Posts
    #2  
    This is driving me nuts too. It worked fine but my STFP started giving me the same no authentication error. So I uninstalled optware and reinstalled the whole thing now I get the error again. Also I noticed that now on preware it says (in the description) that dropbear and openssh work on port 22 the standard ssh port rather than 222 the non standard one that was previously used. I also reinstalled everything and I keep getting the same error.
  3.    #3  
    Quote Originally Posted by nullr View Post
    This is driving me nuts too. It worked fine but my STFP started giving me the same no authentication error. So I uninstalled optware and reinstalled the whole thing now I get the error again. Also I noticed that now on preware it says (in the description) that dropbear and openssh work on port 22 the standard ssh port rather than 222 the non standard one that was previously used. I also reinstalled everything and I keep getting the same error.
    I finally got this working. I have no experience with dropbear, save for this experience, so I just used openssh instead.

    you might have to do keygen on your device
    Arthur Thornton

    Former webOS DevRel Engineer at Palm, HP, and LG
    Former webOS app developer (built Voice Memos, Sparrow, and several homebrew apps and patches)
    Former blogger for webOS Nation and webOS Roundup
  4. nullr's Avatar
    Posts
    136 Posts
    Global Posts
    152 Global Posts
    #4  
    Ok I fixed mine. I suspected there was something to do with the port being changed to "22" from "222" or the "PasswordAuthentication" in the sshd_config file was set to no. The the vi editor in Win xp is a joke and I still havent tried novacom on Ubuntu.The pre puts config files in /opt/etc/openssh/sshd_config rather than the standard /opt/etc/sshd_config Follow these steps and let me know how it goes. If any command does not work throw sudo infront of it.

    1.Get into pre command line either the novacom on cmd or the terminal app. (theres a tutorial but I dont have enough posts to post links)
    2.copy "cp /opt/etc/openssh/sshd_config /media/internal/sshd_config" this will copy your config file to the root of you Pre's usb drive (note: sshd_config no ssh_config)
    3.Connect your Pre on the "USB DRIVE"
    4.Open sshd_config file just double click and when it asks what program to use pick wordpad.
    5. Find "PasswordAuthentication" and if it has a no change it to yes otherwise just delete the "#" in front of "PasswordAuthentication" (not sure if this step matters)
    6.Find "Port" and change it back to "222"
    7. Save file. Unplug the Pre and plug it back in (to take it out of usb drive mode)
    8.copy "cp /media/internal/sshd_config /opt/etc/openssh/sshd_config" (this copys the edited config file)
    9. Restart ssh with "sudo /opt/etc/init.d/S40sshd restart"

    Now you loaded the new config file. Open putty put in your ip or dns and put port "222". That fixed it for me. Note to developers change the port back to 222 please.
  5. nullr's Avatar
    Posts
    136 Posts
    Global Posts
    152 Global Posts
    #5  
    This also fixed my SFTP problem.

Posting Permissions