Results 1 to 18 of 18
  1.    #1  
    I've been using the same password and checked the caplocks.

    but after updating 1.4 i can't ssh into my pre. access denied is the error code.

    anyone have any ideas?
  2. #2  
    probably some of your ssh configuration somewhere is acting up, i couldnt tell you exactly as there are many picky points in setting up an ssh, i would reinstall the app and reconfigure the ssh.
  3.    #3  
    gahhh that is what i was trying to avoid. any other method? can i terminal on my phone and change the pwd that way?

    i'm not too linux savy but can understand if someone points me in the right direction.
  4. #4  
    the answers are in this thread

    edit: this post
  5. #5  
    Quote Originally Posted by gu12u7 View Post
    I've been using the same password and checked the caplocks.

    but after updating 1.4 i can't ssh into my pre. access denied is the error code.

    anyone have any ideas?
    Rod suggested via IRC that this method is now obsolete (becuase I think he said:...) WebOS Updates are rewriting the portion which stores the username/password.

    He stated the new preferred method is to install "OpenSSH SFTP Server" from Preware and follow these instructions from the wiki to set it up.

    Edit: While the webos-internals team works on the Terminal app... you can use the Termunis app instead (which will need to be done to complete the setup)
    Last edited by MLJones8; 03/05/2010 at 01:06 AM.
    Pre|central Peacekeepers
    Share your Mizzou pride:
    - wallpapers/boot themes - here
    - Black n' Gold theme - here
  6.    #6  
    Quote Originally Posted by rawdeadfish View Post
    the answers are in this thread

    edit: this post
    thank you sir
  7. #7  
    Quote Originally Posted by MLJones8 View Post
    Rod suggested via IRC that this method is now obsolete (becuase I think he said:...) WebOS Updates are rewriting the portion which stores the username/password.

    He stated the new preferred method is to install "OpenSSH SFTP Server" from Preware and follow these instructions from the wiki to set it up.
    That is correct. The new method is more secure, and impervious to Palm webOS updates.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  8. #8  
    Quote Originally Posted by everette13 View Post
    hi, i installed all the packages also and can occasionally get it to connect, but it only lasts for a few moments; it only connects 1/10 times, of the rest, 6/10 give a "connection timed out" error and 3/10 ask for password then give "host not communicating for more than 15 seconds..." error.
    -is this not working well w 1.4?
    -what else should i do? i followed your links but most are old/deprecated.
    -as far as setting up a user, do we still do that or is that outdated also?

    it is unuseable as it is.
    thanks much.
    Ev
    Quote Originally Posted by MLJones8 View Post
    All the above is out of date (to my knowledge)...

    see post 5: h**p://forums.precentral.net/general-webos-chat/234107-cant-root-logon-after-1-4-a.ht
    hi,
    i was directed over here. i used the wiki to install and followed every direction, but what i initially posted still applies. i am installing this tonight for the first time, so should have most up to date packages, i hope.
    is there something else i need to do or change? both the putty and winscp programs have the "...to check it's working..." instructions, but no info on what to do if it isn't.
    thanks
    Ev

    sooo, no one can help with this?
    Last edited by everette13; 03/18/2010 at 09:06 PM.
  9. #9  
    I used this new method to get ssh working, but it only works with WIFI

    How do I get winscp working with EVDO?
  10. #10  
    I am having a heck of a time trying to get ssh to work and not having any luck. I followed all of the instructions, in several versions, re-installing the packages (both openSSH and dropbear) each time and wiping out the .ssh dirs, too, just to make sure.

    There seems to be a mix of pre (as in prior) 1.4 instructions and current 1.4 instructions, neither of which are working for me.

    I also tried creating the non-root users according to directions and that didn't work either.

    First, I don't understand why SSH is not built-in to webOS, or a terminal app, (or several other things that are available as patches, etc, but I digress). (oh alright, no root pw so big security hole for non-tech users)

    Is there a DEFINITIVE GUIDE to installing and getting SSH running on a Pre+ with 1.4? This is driving me crazy. I'm a rather experienced linux user (over 10 years) and have successfully used private keys in puTTY (or from linux bash prompt) before. I cannot figure out why this isn't working and why it has to be such a wonky procedure.

    Basically, the errors I'm getting are either "permission denied (publickey)" or "ssh_exchange_identification: Connection closed by remote host" if I'm even able to hit the server at all.

    Sometimes I can't even get the keys to generate properly with ssh-keygen and the public key NEVER gets written as id_rsa.pub. Last time it was ").pub"

    While it would be nice to SSH out, Terminus is too unreliable and of course Terminal isn't working. But SCP or SFTP for file transfers (even just WiFi only) would be a huge help.

    thanks in advance...
  11. #11  
    1) Remove all dropbear and openssh packages that you may have installed by previous obsolete methods. "ipkg-opt remove <package>" is probably what you want.

    2) Reboot

    3) Install Preware (http://install.preware.org).

    4) Install OpenSSH SFTP Server

    5) Use the OpenSSH package Homepage link to set up ssh keys.

    6) Use the keys to ssh in to the device over wifi, with the root user, on port 22.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  12. #12  
    Rod: anyway to ssh over EVDO?
  13. #13  
    Quote Originally Posted by trim81 View Post
    Rod: anyway to ssh over EVDO?
    Edit /etc/event.d/mobi.optware.openssh

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  14. #14  
    Rod,

    Thanks for the prompt reply. I followed the instructions to a "T", orr at least as closely as possible.

    I already had preware installed so used it to remove openssh and sftp packages. I also did not have an ipkg-opt command.

    Removed, rebooted, re-installed, rebooted.

    ran ssh-keygen
    public key was output to }.pub (yes, a curly brace)
    couldn't do anything with that symbol in terminus so rm *.pub and try again starting with a reboot.

    public key generation got stuck outputting a nameless file that still sits in /home/root since it has no name, I can't delete it or anything.

    reboot, try again
    this time identification output to o.
    public key stored in o.pub
    whatever, continuing
    btw, private key in default location /home/root/.ssh/id_rsa

    mv o.pub /home/root/.ssh/authorized_keys

    tar -cvf /media/internal/id_rsa.tar /home/root/.ssh/id_rsa
    so it won't get borked in transmission and in a location I can access from email so I can send it to myself to then untar and run through puTTYgen

    did all the puTTYgen and puTTY stuff as outlined on the openSSH package homepage.

    same errors and inability to login.

    any other ideas?
    is anyone else seeing this same weirrdness? Or does it go by the book for you?

    thanks
  15. #15  
    Quote Originally Posted by surfingjerry View Post
    Rod,

    Thanks for the prompt reply. I followed the instructions to a "T", orr at least as closely as possible.

    I already had preware installed so used it to remove openssh and sftp packages. I also did not have an ipkg-opt command.

    Removed, rebooted, re-installed, rebooted.

    ran ssh-keygen
    public key was output to }.pub (yes, a curly brace)
    couldn't do anything with that symbol in terminus so rm *.pub and try again starting with a reboot.

    public key generation got stuck outputting a nameless file that still sits in /home/root since it has no name, I can't delete it or anything.

    reboot, try again
    this time identification output to o.
    public key stored in o.pub
    whatever, continuing
    btw, private key in default location /home/root/.ssh/id_rsa

    mv o.pub /home/root/.ssh/authorized_keys

    tar -cvf /media/internal/id_rsa.tar /home/root/.ssh/id_rsa
    so it won't get borked in transmission and in a location I can access from email so I can send it to myself to then untar and run through puTTYgen

    did all the puTTYgen and puTTY stuff as outlined on the openSSH package homepage.

    same errors and inability to login.

    any other ideas?
    is anyone else seeing this same weirrdness? Or does it go by the book for you?

    thanks
    There is something very wrong if it is writing to filenames like that.

    -- Rod
  16. #16  
    yeah, I suppose so.

    what if I generate keys on a ddifferent machine and transfer them over... Might that work?
  17. #17  
    Quote Originally Posted by rwhitby View Post
    Edit /etc/event.d/mobi.optware.openssh

    -- Rod
    Rod: what do I edit in that file?

    thanks
  18. #18  
    Quote Originally Posted by trim81 View Post
    Rod: what do I edit in that file?

    thanks
    just enter: vi /etc/event.d/mobi.optware.openssh

    there are some lines in it explaining what to do to enable EVDO. I'd tell you, but my pre is giving me ssh issues

    or here:
    Remove the "-i eth0" on both of the following lines to enable SSH access over the cellular data network (EVDO, etc).

Posting Permissions