MobileRead Forums - View Single Post - pbsshd doesn't start, openssh lib mismatch

rkomar · 07-07-2018, 02:42 PM

It looks like openssl was upgraded on the device, which is good for security. However, it does mean old binaries won't work, and also it is likely that the pocketbook SDK is out of date. To get this to work properly will take a fair amount of work. You will need to download the most recent version of the SDK (I recommend getting @BruceLee's version at https://www.mobileread.com/forums/sh...34&postcount=1). If the version of libcrypto.so on the device doesn't match the version in the SDK, you will have to download the openssl source code that matches the version on the device, and then cross-compile it with the SDK. You will then need to update the SDK by hand with the cross-compiled libraries and include files. After that, you can get a recent version of the openssh source code, and then cross-compile that based on the instructions in the README.txt file in the pbsshd package. Looking inside the pbsshd package, you will be able to see which of the cross-compiled openssh files you will need to copy onto the device.

An easier, but less secure, option would be to copy the version of libcrypto.so.1.0.0 from the pocketboot SDK to a new directory on the device, and add it to the LD_LIBRARY_PATH environmental variable within the sshd_start.app script before sshd is started. For example, if you copy it to the /mnt/ext1/applications/pb_sshd directory, then you would add the line:

export LD_LIBRARY_PATH=/mnt/ext1/applications/pb_sshd:$LD_LIBRARY_PATH

I'm not 100% sure that the LD_LIBRARY_PATH variable will be passed to the programs started by sshd (e.g. sftp-server). It is easiest to just try and see.

07-07-2018, 02:42 PM	#2
rkomar Wizard Posts: 3,057 Karma: 18821071 Join Date: Oct 2010 Location: Sudbury, ON, Canada Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633	It looks like openssl was upgraded on the device, which is good for security. However, it does mean old binaries won't work, and also it is likely that the pocketbook SDK is out of date. To get this to work properly will take a fair amount of work. You will need to download the most recent version of the SDK (I recommend getting @BruceLee's version at https://www.mobileread.com/forums/sh...34&postcount=1). If the version of libcrypto.so on the device doesn't match the version in the SDK, you will have to download the openssl source code that matches the version on the device, and then cross-compile it with the SDK. You will then need to update the SDK by hand with the cross-compiled libraries and include files. After that, you can get a recent version of the openssh source code, and then cross-compile that based on the instructions in the README.txt file in the pbsshd package. Looking inside the pbsshd package, you will be able to see which of the cross-compiled openssh files you will need to copy onto the device. An easier, but less secure, option would be to copy the version of libcrypto.so.1.0.0 from the pocketboot SDK to a new directory on the device, and add it to the LD_LIBRARY_PATH environmental variable within the sshd_start.app script before sshd is started. For example, if you copy it to the /mnt/ext1/applications/pb_sshd directory, then you would add the line: export LD_LIBRARY_PATH=/mnt/ext1/applications/pb_sshd:$LD_LIBRARY_PATH I'm not 100% sure that the LD_LIBRARY_PATH variable will be passed to the programs started by sshd (e.g. sftp-server). It is easiest to just try and see.