PDA

View Full Version : Is it possible to access the 770 over the WLAN?


Smiley Dan
11-10-2005, 08:06 AM
I mean, in a similar way to using the USB?

Is samba out for this device? If so we could make the folders samba mounts and mount them in our Linux/Windows laptops.

I really don't want to have to connect the USB *every* time I want to upload something.

Maybe I can use scp with the sshd being written?

Smiley Dan
11-10-2005, 08:49 AM
I've installed xterm and ssh (dropbear) - anyone know the user accounts and passwords? :D

Tried root/rootme but that didn't work, putty bombed out.

aflegg
11-10-2005, 12:40 PM
http://maemo.org/maemowiki/InstallSsh

Smiley Dan
11-10-2005, 03:05 PM
http://maemo.org/maemowiki/InstallSsh
yeah that's what l've been following. l don't want root access , just want to know the user password. useradd also doesn't work.

aflegg
11-10-2005, 05:42 PM
That page points out (albeit perhaps not clearly) that you can't log into the user account without using a public/private key pair.

Create the key pair on your PC and copy the public key to ~/.ssh/authorized_keys on the 770.

Lord Bodak
12-23-2005, 10:14 PM
I created a key on my machine, copied the id_rsa.pub file to the ~/.ssh/authorized_keys directory on the 770...

Ran the server as user.

Then tried connecting with:
ssh ip -p 2222

Got a prompt for a password and no luck figuring out what the password should be. Any ideas?

putkowski
12-23-2005, 10:59 PM
I'm getting to the file system using winscp and scp (see the troubleshooting section.) I may soon figure what tiny spot allows me to logon to the wiki.

It seems that when you copy to the fat MMC, edit, and copy back, the permissions are trashed. What a surprise !

In short, the answer is yes. (If you want a direct edit using winscp.) This works in both "rd-modes"

I will also be checking various distros (su9.2dt, deb and ian (sarge,) and the latest hat thing) to see how we can similarly ssh (fish,etc) to the box (That is cruel-- it's such a pretty box.)

Of course, if I get work things could slow dramatically. (iSeries, anyone?)

P'ski

putkowski
12-23-2005, 11:03 PM
I created a key on my machine, copied the id_rsa.pub file to the ~/.ssh/authorized_keys directory on the 770...

Ran the server as user.

Then tried connecting with:
ssh ip -p 2222

Got a prompt for a password and no luck figuring out what the password should be. Any ideas?

See the ssh install directions and make the link to rc2.d.

This will make the server run as (whoever) at startup and port 22 will be like barn doors.

P'ski

Lord Bodak
12-23-2005, 11:12 PM
See the ssh install directions and make the link to rc2.d.

This will make the server run as (whoever) at startup and port 22 will be like barn doors.

P'ski

Ok, I went ahead and tried that. Same problem, it still wants a password.

Edit: Never mind, I was being stupid. Long time since I set up ssh! I put the public key in an authorized_keys directory, not an authorized_keys file. Working fine now.

putkowski
12-23-2005, 11:33 PM
Ok, I went ahead and tried that. Same problem, it still wants a password.

After a boot-in-the-keister? You will need to see the wiki on how to gainroot. This box is stupidly defended.

did you do Xterm

sudo gainroot

and get a message saying "root enabled"

if not, you probably got a message saying "enable r&d mode if you want to break your device."

If you don't have a linux box handy, you are sunk. You can check the "troubleshooting" dept messages on "trouble with dropbear"

things will get better in the next few days.

if you know about X, please brush-up.

P'ski

Lord Bodak
12-23-2005, 11:35 PM
I got it-- see my edit above. Stupid me :)

putkowski
12-23-2005, 11:56 PM
Ok, I went ahead and tried that. Same problem, it still wants a password.

Edit: Never mind, I was being stupid. Long time since I set up ssh! I put the public key in an authorized_keys directory, not an authorized_keys file. Working fine now.


I haven't dealt with the key issues. I do Enter when I first connnect with ssh. I think this sets the key for the target. Am I right?

After a reflash, ssh from a debian client (correctly) says the key is afu. Since the error indicates the file containing the offending entry, it's easy to edit. All Hail The Lack of a Registry !!