SFTP not working on 5.1.0

[lukeroge]

I'm trying to use the sftp hack mentioned on the wiki to connect to my kindle touch, but its not working at all. An example of this below

me:~$ sshfs -o sftp_server=/mnt/us/sftp-server root@KINDLE_IP:/ /media/kindle
root@KINDLE_IPs password: 
remote host has disconnected

I tried running the sftp-server program itself on the kindle, and got this error:

[root@kindle root]# /mnt/us/sftp-server
/mnt/us/sftp-server: error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared object file: No such file or directory

I would really like to get this working again, as I can't really do much without it
Thanks in advance.

[NiLuJe]

Oh, yep, they updated to OpenSSL-1 in 5.1.0.

I'll probably do a proper KT OpenSSH (where sftp-server comes from) build at some point, so, err, unless you want to do it yourself, you'll have to wait, because the older Kindles relies on a binary built against OpenSSL-0.9.8 (and I guess that's where the binary came from, the K2/K3 usbnet hack).

(The very, very ugly hack of symlinking openssl 1 to openssl 0.9.8 might work, but it might also make sftp-server explode in a fiery abi mismatch ^^).

But that's good to know, it means that yet another thing will be 5.1.0 only .

[geekmaster]

Originally Posted by NiLuJe

Oh, yep, they updated to OpenSSL-1 in 5.1.0.
...
But that's good to know, it means that yet another thing will be 5.1.0 only .

It would be nice to declare 5.1.0 hopelessly broken and unsupported. I actually requested that amazon release an update to make eink updates compatible with 5.0.x, but it is looking like that is only the beginning. I suppose if they can just recompile everything to use their broken header files and they keep this a closed system, they do not have to care (and it may actually be in their advantage) in their war on software that does not come from their app store (from which they profit at least from exposure to ads)....

[lukeroge]

Originally Posted by geekmaster

It would be nice to declare 5.1.0 hopelessly broken and unsupported. I actually requested that amazon release an update to make eink updates compatible with 5.0.x, but it is looking like that is only the beginning. I suppose if they can just recompile everything to use their broken header files and they keep this a closed system, they do not have to care (and it may actually be in their advantage) in their war on software that does not come from their app store (from which they profit at least from exposure to ads)....

I don't think its really "broken" per say, but it is annoying that they changed a lot around (breaking our stuff) :/

Originally Posted by NiLuJe

Oh, yep, they updated to OpenSSL-1 in 5.1.0.

I'll probably do a proper KT OpenSSH (where sftp-server comes from) build at some point, so, err, unless you want to do it yourself, you'll have to wait, because the older Kindles relies on a binary built against OpenSSL-0.9.8 (and I guess that's where the binary came from, the K2/K3 usbnet hack).

(The very, very ugly hack of symlinking openssl 1 to openssl 0.9.8 might work, but it might also make sftp-server explode in a fiery abi mismatch ^^).

But that's good to know, it means that yet another thing will be 5.1.0 only .

Shockingly enough, symlinking it does actually work! I've only just tried it so I'm yet to see if there will be any crashing issues later on. I look forward to seeing progress on a proper version

[NiLuJe]

FWIW, after finally having built a proper K5 TC, the reason it doesn't implode is because of the fact that sftp-server doesn't really depends on OpenSSL, as building it with as-needed reveals .

 0x00000001 (NEEDED)                     Shared library: [libgcc_s.so.1]
 0x00000001 (NEEDED)                     Shared library: [libc.so.6]
 0x00000001 (NEEDED)                     Shared library: [ld-linux.so.3]

vs.

 0x00000001 (NEEDED)                     Shared library: [libcrypto.so.0.9.8]
 0x00000001 (NEEDED)                     Shared library: [libdl.so.2]
 0x00000001 (NEEDED)                     Shared library: [libutil.so.1]
 0x00000001 (NEEDED)                     Shared library: [libz.so.1]
 0x00000001 (NEEDED)                     Shared library: [libnsl.so.1]
 0x00000001 (NEEDED)                     Shared library: [libcrypt.so.1]
 0x00000001 (NEEDED)                     Shared library: [libresolv.so.2]
 0x00000001 (NEEDED)                     Shared library: [libc.so.6]
 0x00000001 (NEEDED)                     Shared library: [ld-linux.so.3]

Sidebar: Where the hell did that ARMv5 binary came from, anyway? o_O.

[orpheus2011]

Niluje - Could you kindly provide the ssh commands for the correct symlinking? I am having the same trouble in getting sftp-server to work on my Paperwhite. Many thanks!

[twobob]

1) find what you want to link against

[root@kindle awesome]# find / -iname '*'"libcrypto"'*'

/usr/lib/libcrypto.so.1.0.0
/usr/lib/libcrypto.so
/mnt/us/usr/lib/libcrypto.so.1.0.0
/mnt/us/usr/lib/libcrypto.so

2) read ln help

[root@kindle awesome]# ln -h

Usage: ln [OPTIONS] TARGET... LINK|DIR

Create a link LINK or DIR/TARGET to the specified TARGET(s)

Options:
-s Make symlinks instead of hardlinks
-f Remove existing destinations
-n Don't dereference symlinks - treat like normal file
-b Make a backup of the target (if exists) before link operation
-S suf Use suffix instead of ~ when making backup files

so we probably want a soft link

3) cd to the folder you want the link to live in
[root@kindle awesome]# cd /usr/lib
[root@kindle lib]#

4) make root writable
mntroot rw

5) make link
ln -s /usr/lib/libcrypto.so.1.0.0 libcrypto.so.0.9.8

4) make root read only
mntroot ro


That kind of thing?

[NiLuJe]

@orpheus2011: I did. It's in the K4 usbnet package.