OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: mnmis on September 21, 2004, 08:39:33 am
-
I installed Openzaurus 3.5.1 and I cannot connect to the Zaurus using ssh.
It asks for a password and I tried rootme, root, password and none of them worked.
Does anyone know what it is?
-
Assuming you're trying to log in as root, it's your root password (which is blank to begin with). SSH may not like blank passwords (?) so you might have to set one before you use it - I don't know.
Si
-
I used to login with root on 3.3.6-pre1 with no problem.
-
I haven't installed 3.5.1 yet (just waiting for the final GPE image), so this is just a guess. Try checking your /etc/ssh/sshd_config to see if "PermitRootLogin No" is set.
-
OZ 3.5.1 has empty root password (no password is set)
-
No such directory /etc/ssh on the Zaurus.
-
ssh works with 'rootme' password. It also works with any password
Dan
-
rootme doesn't work.
I even created a new user and that didn't work either.
I can ping the zaurus from my pc so that isn't it.
Any more ideas anyone?
-
Make sure you are root from the Linux box performing the ssh.
Also make sure to clear /root/.ssh/*
That will cause the ssh mechanism to re-negotiate.
Dan
-
I am trying to connect to the zaurus from my XP pc. Sorry for the confusion.
The thing is that the older versions of openzaurus never asked for a password, 3.5.1 does.
-
I am trying to connect to the zaurus from my XP pc
What ssh software?
Can you ping?
Si
-
The software is ssh from www.ssh.com.
I can ping from the pc to the zaurus and also from the zaurus to the pc.
-
dont have any problem when login to ssh using securecrt software.
i confirm there is a problem connecting to zaurus 351 using ssh client from www.ssh.com.
when tring using securefx software. i got this error. maybe it is because of '! sh: /usr/libexec/sftp-server: not found '.
maybe this can help.
i Session 00004 established for quick connect
i SecureFX version 2.2.7.238 (Official Release - August 19, 2004)
i RECV : Remote Identifier = "SSH-2.0-dropbear_0.44test4"
i CAP : Remote can re-key
i CAP : Remote sends language in password change requests
i CAP : Remote sends algorithm name in PK_OK packets
i CAP : Remote sends algorithm name in public key packets
i CAP : Remote sends algorithm name in signatures
i CAP : Remote sends error text in open failure packets
i CAP : Remote sends name in service accept packets
i CAP : Remote includes port number in x11 open packets
i CAP : Remote uses 160 bit keys for SHA1 MAC
i CAP : Remote supports new diffie-hellman group exchange messages
i CAP : Remote correctly handles unknown SFTP extensions
i CAP : Remote correctly encodes OID for gssapi
i CAP : Remote correctly uses connected addresses in forwarded-tcpip requests
i SEND : KEXINIT
i RECV : Read kexinit
i Available Remote Kex Methods = diffie-hellman-group1-sha1
i Selected Kex Method = diffie-hellman-group1-sha1
i Available Remote Host Key Algos = ssh-rsa
i Selected Host Key Algo = ssh-rsa
i Available Remote Send Ciphers = aes128-cbc,blowfish-cbc,twofish-cbc,3des-cbc
i Selected Send Cipher = aes128-cbc
i Available Remote Recv Ciphers = aes128-cbc,blowfish-cbc,twofish-cbc,3des-cbc
i Selected Recv Cipher = aes128-cbc
i Available Remote Send Macs = hmac-sha1,hmac-md5
i Selected Send Mac = hmac-md5
i Available Remote Recv Macs = hmac-sha1,hmac-md5
i Selected Recv Mac = hmac-md5
i Available Remote Compressors = none,zlib
i Selected Compressor = none
i Available Remote Decompressors = none,zlib
i Selected Decompressor = none
i SEND : KEXDH_INIT
i RECV : KEXDH_REPLY
i SEND : NEWKEYS
i RECV : NEWKEYS
i SEND: SERVICE_REQUEST[ssh-userauth]
i RECV: SERVICE_ACCEPT[ssh-userauth] -- OK
i SENT : USERAUTH_REQUEST [none]
i RECV : USERAUTH_FAILURE, continuations [publickey,password]
i SENT : USERAUTH_REQUEST [password]
i RECV : AUTH_SUCCESS
! sh: /usr/libexec/sftp-server: not found
i Channel Closed: 00000000 (The operation completed successfully. )
i Connected for 7 seconds, 1021 bytes sent, 1292 bytes receive
-
Well I have the problem with SSHSecureShell from sss.com too and confirm. I get in by using ssh from linux.
Since I can connenct via SSHSecureShell to OZ 3.3.6-pre-1 I think that this depends on dropear on Zaurus.
This problem can be solved by using OpenSSH. I heard this will be soon in the feed. You could also try the ssh packages from the 3.3.6 feed (I dunno if they work with 3.5.1).
Note that SSH requires more place than dropbear.
Cheers,
Sam
-
thank you for explaination. for now, i'm using cygwin ssh and for transfering file, winscp.
regards
-
Well, I got it to work using Putty. I saw that they added openssh to the updates today, I'll try that and report back.
-
Installing openssh fixed my problem using ssh.com's ssh client.
I had to edit sshd_config to add the ability for root and empty password to login.
I also edited the sftp-server path to get that to work.
-
installed the openssh from the upgrade feed. erkk.. 'eats' about 900kb of my root space.
-
i have a problem when try to install openssh in root/ram. after rebooting, opie wont start, indicating that libopie is missing. i don't know why it's happen.
the only modification is transfering my /root folder to sd /mnt/card/root and make a softlink /mnt/card/root to /root.
using 48-6 rom if not mistaken. oz351
-
just ignore my previous post. my fault when overwrite task-opie-minimal in /mnt/card. sorry for confusion.
-
FYI: Release -r1 of openssh in the upgrade feed fixes the sftp-server and "empty password login" problems
Thanks for your reports.
-
keep up the good work guys!
-
If you Google 'OpenSSH Windows' you'll find a port of openssh for Windows that will solve some of these problems and provide ssh and scp commands that function identically to their Unix counterparts.
-
I think thers some comfusion here.
ssh = secure shell (not file transfer)
scp = secure copy mechanism (file transfer)
sftp = secure file transfer
It sounds like we are mixing up what your trying to do
dropbear as installed by default supports ssh and scp
if the app your using tries to use sftp for transfer it will fail with the unable to find sftp-server this is correct as it doesnt exist. (multisync etc)
Apps that use scp for transfer are not affected
if you remove dropbear and install openssh from the upgrades feed you will now be supporting ssh scp and sftp
behaviour should now be the same as 3.3.6
-
I have installed the seven packages related to openssh from
http://openzaurus.org/official/unstable/3.5.1/upgrades/ (http://openzaurus.org/official/unstable/3.5.1/upgrades/)
I have generated a keypair with a pasphrase. I did the same on my cube
and put the public keys on my server. The cube gets in fine after being challanged for the
passphrase.
The Zaurus fails. When I do ssh -v, I see keys being exchanged but when I get to the
stage where the passphrase is required, instead of this :
debug1: read PEM private key done: type
Enter passphrase for key '/Users/poti/.ssh/id_dsa':
I get:
debug1: read PEM private key done: type
ssh_akspass: exec(/usr/libexec/ssh-askpass): No such file or directory
Where can I find ssh-askpass for OZ3.5.1, GPE?
Or, how can I get openssh not to use ssh-askpass, as in the case of my cube?
-
Coulds someone give me the install order of the OpenSSH packages on that feed? I just need to get SFTP to work, but I'm not sure what package puts the init.d file in place.
-
Coulds someone give me the install order of the OpenSSH packages on that feed? I just need to get SFTP to work, but I'm not sure what package puts the init.d file in place.
There is no sftp init.d file as the sftp-server is invoked by the ssh deamon.
Just install the openssh-sftp and dropbear should handle the rest.
-
Ok, installed sshd and sftp, did an ipkg-ling on both and it seems to work, thanks guys.