Problem with dropbear/WinSCP

[avdigital]

Hi,

I installed dropbear-key and dropbear-server on my 'rooted' Nokia 770 and I can connect to it with PuTTY and WinSCP on my Windows XP computer.

With WinSCP I can brows the directories of my Nokia and create/delete files on it, the only thing I can't do is transfer files from and to it with drag&drop. Is gives an error and WinSCP says that no SCP server is available and error = 127.

Anybody got some clue :confused: ?

[bradb]

Wow thanks... I didn't know there was a nice scp client for Windows.

As far as your problem goes, does this help?

http://winscp.net/eng/docs/faq_scp_not_found

Brad.

[avdigital]

Thanks, I know now where the problem lies.

scp is indeed on the Nokia (in /var/lib/install/usr/bin) but the path to it is not available.

I'm not a 'Linux wizard' at all, so could somebody help me to solve this, probably very simple, problem?

[avdigital]

I found the solution to my 'problem':


Make a link to the scp program:

ln -sf /var/lib/install/usr/bin/scp /usr/bin/scp

And it works; I can transfer file now from/to my Nokia :D .

(Not bad for a Linux newbie... :cool: )

[putkowski]

Can you browse "all" of the files? (Are you signing-in as root?)

[avdigital]

Can you browse "all" of the files? (Are you signing-in as root?)

Yes, with user 'root' and password 'rootme' I can browse all the files. (I don't use key files in dropbear)

[bradb]

I found the solution to my 'problem':

Great work. You'll be a true geek before you know it ;-)

I think that in this case the easiest solution is to simply make sure that the .profile for "user" (the complete path is /home/user/.profile) needs to make sure that /var/lib/install/usr/bin is in the path.

This time, no need for root :-)

[avdigital]

I have read somewhere else that the only way to login as 'user' you have to use the key files. I will look into that...

PS: I really like this Nokia, I think it will be only get better in time with new software and improvements. It also lets me discover and understand Linux as a hardcore Windows user :p .

[putkowski]

AVDigital,

Looks like the WINScp is working... do you get a couple of dialog boxes about "pwd" and "groups" ?

Maybe it's time for me to turn-off r & d mode for a while.

"It's good to be the root !!"

PS: WINScp has a built-in editor? What about those "custom commands?" (select a file and right click..) (you have to be in the "norton" interface.)

[Remote User]

I'm not actually a 770 maemo developer and am only just about to order a 770 now but I've seen the fakeroot logon name used all over the place and I wonder if that isn't the correct logon name, instead of root, in this context as it is in many contexts.

I'd also like to remind everyone that if you use the Wiki and you learn something to make it better, go ahead and enhance the entry for all who follow. It's very simple to do this and the knowledge base grows in its usefulness & value every time anyone contributes to it.

[aflegg]

`fakeroot' is a command within the Scratchbox SDK environment - and used in Debian generally - to fake root-privileges, without actually giving them to processes. Usually build-processes for packing debs.

[putkowski]

I'd love to do WIKI. Anyone planning on enabling the LOGON dialog?

[avdigital]

AVDigital,

Looks like the WINScp is working... do you get a couple of dialog boxes about "pwd" and "groups" ?

...

PS: WINScp has a built-in editor? What about those "custom commands?" (select a file and right click..) (you have to be in the "norton" interface.)


I did get a couple of dialog boxes, but if you clear 'Lookup user groups' in WinSCP settings under Environment-->Scp then it's gone.

And in WinSCP you can edit the selected files on you Nokia.

[putkowski]

And it gets better. If you copy modified 770 files to the PC, the permissions get trashed, but when you copy the file back to the 770, the permissions on the 770 file are retained.

Proof: (using WinSCP File/Properties... didn't check with ls)

copy /usr/sbin/gainroot to the PC. Rename the file (on the PC) and copy it back... the execute permissions will be gone.

change the 770 (renamed file's) permissions to include the execute bits.

re-copy the (renamed) PC file to the 770. The execute permissions are retained.

How this is Good:

we can create a directory tree (under a directory on the windows machine) that duplicates the accounts we have changed files in and copy those modified files to the PC folders. after a reflash, we can create/run a synchronize (selecting all files on the PC and using "selected" and "existing" files only options.)

poor man's restore for scripts and configuration files (at least!)