-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to open any /dev/pty?? devices #4
Comments
I think that's fixed in my fork... https://github.com/geofferey/dropbear-android |
I've checked you fork - it does'nt work too but with different error: char* ttyname(int)(3) is not implemented on Android |
BTW: version 2015.67 works but does not have required options either for password authentication or authorized keys(it requires keys in home dir which is wiped very time when android boots) |
Ok - i fix 2015.67 version :) - to be more exact i've fixed only one line in patch. You can find docker image to build it on docker hub: s3b0/android-dropbear |
[email protected]'s password: dropber output |
Hi
I have problem from subject. I'm trying to run it (on android box with 4.2.2 android version, rooted of course ;) ) as follows:
dropbear -d path_to_dss_key -r p path_to_rsa_key -r path_to_ecdsa_key -p 22 -P path_to_pid -R -N user -C password -U root -G root -A -F
Error log:
...
Failed to open any /dev/pty?? devices
No pty was allocated, couldn't execute
....
The text was updated successfully, but these errors were encountered: