[X]Assistant

[kaztost]

SSH-пїЅпїЅпїЅпїЅпїЅпїЅ Dropbear пїЅ пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ Linux-пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅ Android-пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ download

Version: 2016.74



For the operation of the program requires root user rights.

The installers laid out here are designed for ARM devices.

Description:
Of the many options for installing SSH / SFTP server on phones and tablets, I stopped at the method proposed below, based on thisarticle.

First, a minimum of various bugs with proper configuration. Secondly, the installation takes a relatively small amount of memory on the device (10-11 MB). Thirdly, an integrated opkg environment appears along with the ssh server, with the ability to install a huge number of Linux packages fromrepositoryEntware-ng, originally intended for installing additional software on routers and other network hardware. This repository is updated frequently enough - the last update was April 19, 2017.

I consider that this topic corresponds to the section - we are emulating a router :)

Installation (Android 4 or newer): (apk-programs are created usingTasker)
1. Entware_Dropbear_Installer_v1.1_19Apr17.apk(6.46 MB)

Requirements: if SuperSU is installed, then in its settings the creation of a namespace split must be disabled; installation in the internal memory of the device; the paths / bin, / opt, / tmp, / data / local / entware-ng and / sdcard / entware-dropbear should not exist. It is desirable that the file /system/etc/resolv.conf does not exist either (otherwise, deal with the DNS settings yourself). Instructions: install, click on the Install button, give root-rights, wait until the button receives the inscription Installed. If it is installed normally, then the binary file / opt / sbin / dropbear should appear. If there is one, go to step 2. If you have done something wrong, reboot, delete the above paths and try to start again (after pressing Reset in the program menu).
2. Universal_Autocontrol_v1.1.apk(2.44 MB)

Instructions: install, click on the Start button, give root rights, check ssh connection (port - 22, login - root, password - 12345) via the external network or via В® ConnectBot (connection root @ localhost). In an ssh session, change the password using the passwd command. With default settings, when you click on Start, the ssh server starts with the /data/local/entware-ng/start.sh script, when you click on Stop, the server is stopped with the /data/local/entware-ng/stop.sh script, and when the android is loaded runs the mount script /data/local/entware-ng/mount.sh and, if the Start button was last pressed (i.e. Stop is active), the /data/local/entware-ng/start.sh script was pressed. Thus, the interface will always be mounted, and ssh depending on the button state.

I also post an alternative installer.Entware_Dropbear_Installer_NO_LIBPATH_v1.1_19Apr17.apk(6.46 MB)

for those with the main one who could not install anything (found on stock firmware from Android 4.4). Difference: in all scripts there is an unset LD_LIBRARY_PATH. For many, the installation fails precisely because of the fact that entvarny binaries do not work because of the android LD_LIBRARY_PATH in the environment.

What's new:

Entware Dropbear Installer v1.1_19Apr17 installer version: fixed minor bugs in scripts, updated installation packages from the repository on 04.19.17.
Version Universal Autocontrol v1.1: added autoload control (disable, enable, manual start).

Comment

The installer creates the / data / local / entware-ng directory and binds it to / opt, but it can also be used when installing the entwary into a self-mounted / opt (via a separate section of the memory card or loop device). To do this, you can pre-mount / opt as you need and create a FILE / data / local / entware-ng. Then the installation script will not be able to create a directory with that name and, accordingly, bin it in / opt. Then all subsequent installation will go to your / opt. It remains to create the mount script as you need and place it in init.d / su.d. Or through Universal Autocontrol, in its settings, the paths of the executed scripts can be changed. The file / data / local / entware-ng can be installed and deleted after installation. Just like the installer himself.

You can also do it differently: before installing, create the / data / local / entware-ng directory and mount your partition there. After installation and reboot, mount the partition in / opt directly.

Manual installation, in particular, for Android<4

1. Change the apk-installer's extension to zip and unpack it into the / sdcard / entware-dropbear directory. The file entware.zip from this directory should also be unpacked there.
2. In the terminal (emulator or adb) execute

su
sh /sdcard/entware-dropbear/install.sh

3. To start the ssh server run

sh /sdcard/entware-dropbear/start.sh

4. Ensure the execution of the mount.sh and start.sh scripts when the device is turned on via init.d / su.d or via Universal Autocontrol.

Busybox is not needed for installation. After installation in ssh-sessions, busybox from entware will work, but it will not replace the system busybox. Before installing new packages, you must perform an "opkg update".It is strongly recommended not to update the package busybox!Otherwise you will not be able to log in and change passwords properly.

The installation script over the network (you need a busybox) can be taken from the message#52356898
If the Linux kernel in the device is quite new (at least 3.2.40), you can try installing the next generation of Entware-3x. Cm.#51746068.
You can read about compiling with gcc on the device itself.here.

Cancel installation.To remove everything completely, you need to remove the Universal Autocontrol program, restart the device, delete the / data / local / entware-ng directory and the (already dead) symlink /system/etc/resolv.conf.

The old hat is here:В® SSH server Dropbear and other console Linux utilities for Android devices (Post kaztost # 60851394)

Developer:Entware team
Homepage: https://github.com/Entware-ng/Entware-ng/wiki

Past versions

Entware_Dropbear_Installer.apk(6.45 MB)

Universal_Autocontrol.apk(2.44 MB)

Entware_Dropbear_Installer_NO_LIBPATH.apk(6.45 MB)

M

The cap is restored after removal by the top-starter.

Post has been editedKenas - 17.05.17, 17:55

[okomand]

And why do the files from the repository have the ipk extension?
Where are the bin7 directly under arm7?
Or do you have to do everything through opkg?

Post has been editedokouser - 16.05.16, 01:31

[kaztost]

[email protected], 01:25

And why do the files from the repository have the ipk extension?

Unzip them as a zip / gzip / tarball - you will see the binaries. It is just that they are not desirable in this form - you may need dependent dynamic libraries (* .so), which are in other ipk files, for execution. This is exactly what the opkg utility does - it downloads and installs all the missing.

Post has been editedkaztost - 16.05.16, 01:39

[okomand]

[email protected], 00:29

Unzip them as a zip / gzip / tarball - see the binaries

Can you tell us a clear sequence of actions to get to the binaries,on androidandwithout using opkg.
Here I have on the android does not work, as the old meme says, here and so just take ipk and unpack it to the binaries.

Post has been editedokouser - 16.05.16, 01:59

[kaztost]

If you put mc in android, then it will unzip ipk without any problems. On Windows, Total Commander also seems to be able, only sometimes it is necessary to rename it to zip. And on android you can tryZarchchiver. Only sense that you unzip, I think not - almost all binaries use libraries from the / opt directory. On the one hand, this is a huge plus, otherwise everything would be confused with android binaries that use completely different dynamic libraries.

Post has been editedkaztost - 20.11.16, 12:11

[okomand]

kaztost
But have you encountered dropbear binaries that could be run from / system / bin?

[Zyxmon]

Please correct the first post. Developer Entware is not me alone. Earns team - "Entware team".
Entware repository is designed to expand the functionality of devices (routers, nasov, ...) with different architectures - armv5, armv7, intel, mipsel. Every week Entware is installed on 1500+ pieces of hardware. On Android, similar packages are not popular, because no GUI. Setup hands in the console. This is linux, not android.

[kaztost]

okouser,In Cyanogen and similar firmware there is a file / system / bin / sshd. This is openSSH-server (not dropbear). there isinstructionby setting it up. Authorization by passwords does not work there, only by keys. On the stock firmware is unlikely to work.

Zyxmoncorrected. I meant that you are the author of the patches and experimental branches.

[okomand]

[email protected], 08:24

and similar firmware there is a file / system / bin / sshd

If it is easy, can you post a binary or throw a link to the repository?

[kaztost]

okouser,
In the same place, * .so files are dependent. It is easier for you to unzip some Cyanaogen firmware from a device with the same architecture and the same version of Android, take a binary, give rights to execute, run if you swear because there is no so-file - pull out the so-file and put in / system / lib, try to start again, etc.

[gorilloid]

If someone needs a specific binary without installing entware itself, then:

1. Remount root on the record, create a folder / opt in the root, remuntium back to ro.
2. Create a folder in the internal memory (for example, in / data) or on a flash drive with ext-fs (better ext2)
3. Bind a folder from internal memory to / opt
4. We take an ipk-package, we add the contents of data.tar.gz to the root, we look at the list of dependencies in the control file, from the archive control.tar.gz, the line "Depends".
5. Download dependency packages and unpack the contents of their data.tar.gz to the root.
6. ???
7. PROFIT!

I know that there are more body movements than when installing the entware itself, but if someone suddenly wants to ...

[email protected], 14:45

On Android, similar packages are not popular, because no GUI. Setup hands in the console. This is linux, not android.

In vain you are so. They are unpopular with housewives, and users, even a little familiar with Linux, are needed like air.

Until I came across entware, I collected standalone binaries all over the internet under armv7.

Post has been editedgorilloid - 10.06.16, 11:34

[kaztost]

If anyone is interested, then you can install almost the same optwarelink. Only the installation is not quite as smooth as in entware. For example, for the postinstall scripts in ipkg to work, you must put / system / xbin in the PATH in the first place to block toolbox utilities. Well, for some reason this ipkg does not always install dependencies, you have to manually install it. And so everything seems to work. Even gedit was launched on an external X-server :)

[BSDevil]

That damn, did

mv / system / sh / system / sh_old
ln -s / opt / bin / bash / system / sh

init.d in my firmware did not work - and that's it! After the reboot, I was left without root; (

$ adb shell
- exec '/ system / bin / sh' failed: No such file or directory (2) -
$ adb remount / system
remount of system failed: Permission denied
remount failed

From the terminal on the mobile phone su stupidly hangs. sudo says i don't have root (((

Post has been editedBSDevil - 07.07.16, 17:05

[kaztost]

[email protected], 17:05

su stupidly freezes

Because the standard shell can not find. Try

su -c / system / bin / sh_old

(or did you really have / system / sh and / system / sh_old?).
Or, if busybox is installed,

su -c busybox ash

If you successfully enter the sous shell, return everything as it was.

[psihodelikzp]

I hope the author of this topic will not mind.
since at work pretty often I come across devices on android and many started asking for remote access via sftp and ssh. I had to do a slightly modified installation script.

Description

Looking for Root and Busybox
1) Download the script
2) Unpack
3) Start the terminal emulator (well, or something like that)
4) Run the script execution with su rights
5)

su
sh /sdcard/Download/install_ssh.sh

The script will download the necessary packages, install them and create the necessary directories. also requests to enter a new password for ssh access will connect via ssh to the local device and after the exit with the commandexitfrom ssh a timer will restart which can be aborted with the command ctrl + cinstall_ssh.rar(1.75 KB)

What has changed:
Auto installationNANO, SFTP_serverAutomatic file generationprofilefrom the conclusions of your system, the request for changing the password for ssh and sftp access is enabled, the installation of the ssh startup script in init.d and the device’s timer reboot (if not, you can interrupt it).

Post has been editedpsihodelikzp - 08.07.16, 00:59

[kaztost]

psihodelikzp,
Of course, not against, your script saves time creating the correct profile. You just need to keep in mind that on many devices init.d either does not work, or it does not work that way. If SuperSU is installed, then it is safer to place init scripts in /system/su.d/, after creating such a directory (all with 700 permissions). All this is unlikely to be foreseen in the script, but to whom it may be necessary to comment out and adjust unnecessary things manually.

Well and on trifles: the section / system after performance of a script remains in a state rw.

[BSDevil]

kaztostI'm sorry, yes. Bin missed in the description of the problem. man su immediately started reading "su -c / system / bin / sh_old" did not work. Yesterday I changed it without a wipe and rutted it again, installing SuperSU, BusyBox and Xposed after it, it did not take a lot of time.

psihodelikzp,Why the enemy archive format and NANO? What pleased me in entware was the presence of VIM and BASH!

Kaztost @ 07/08/2016, 09:46

If SuperSU is installed, then it is safer to place init scripts in /system/su.d/, after creating such a directory (all with 700 permissions).

Does SuperSU somehow support this directory and launch it from there at startup?


One more question. Why do you need it?

wget http://pkg.entware.net/binaries/armv7/experimental/busybox_1.24.1-50_armv7soft.ipk -O /opt/busybox_1.24.1-50_armv7soft.ipk
/ opt / bin / opkg --force-downgrade install /opt/busybox_1.24.1-50_armv7soft.ipk
rm /opt/busybox_1.24.1-50_armv7soft.ipk

By the way, I do not have / etc / passwd, how to be?

root @ stab: / mnt / shell / emulated / 0 # passwd
Changing password for root
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
New password:
Re-enter new password:
passwd: /etc/passwd.29540: Read-only file system
passwd: cannot lock / etc / passwd; try again later.

And how to humanly change the default shell?

Post has been editedBSDevil - 08.07.16, 11:46

[BSDevil]

Kaztost @ 07/08/2016, 09:46

If SuperSU is installed, then it is safer to place init scripts in /system/su.d/, after creating such a directory (all with 700 permissions).

Does SuperSU somehow support this directory and launch it from there at startup?

[kaztost]

BSDevil,

BSDevil @ 07/08/2016, 11:10

"su -c / system / bin / sh_old" did not work

Well, yes, it should have been. You did not have a shell to do su. It was enough for you to re-flash just the kernel, not necessarily the entire firmware.

BSDevil @ 07/08/2016, 11:10

By the way, I do not have / etc / passwd, how to be?

BSDevil @ 07/08/2016, 11:10

One more question. Why do you need it?

Only through / opt / bin / opkg --force-downgrade install /opt/busybox_1.24.1-50_armv7soft.ipk you can install a patched bibybox containing the applet passwd, which will write to / opt / etc / passwd. Otherwise, the non-patched busybox_1.24.2-1_armv7soft.ipk of the new version is installed.

But if you use unpatched bizybox (apparently, just your case), then you need to create symbolic links (/ system) / etc / passwd->/ opt / etc / passwd. The same goes for / etc / group and / etc / shells

[BSDevil]

Kaztost @ 07/08/2016, 1:18 PM

It was enough for you to re-flash just the kernel, not necessarily the entire firmware.

No, I have a Meizu M2 Note. There is a bootloader locked and it is only possible to flash the whole.

Kaztost @ 07/08/2016, 1:18 PM

But if you use unpatched bizybox

My automaton at the command of adb shell falls into the standard. So I asked how to change human walked. Advice from the Internet, I left without root :-D Of course I understand. Fool himself! Could rm -rf / * advise ...

[gorilloid]

BSDevil @ 07/08/2016, 18:10

By the way, I do not have / etc / passwd, how to be?

remount "/" in rw and create (and then in ro), you can do it every time you start, if you write init.d or its similarity.

BSDevil @ 07/09/2016, 01:55

My automaton at the command of adb shell falls into the standard. So I asked how to change human walked.

H'm ... And what prevents to throw the same bash binary, rename it to "bash" and launch it with "bash" (or how do you call it) while being in your native shell?

Changing the native shell can be fraught with there may be certain bindings to it (this was vividly demonstrated to me by android x86 on vbox). The same is with busybox, where there may be specific applets used by the system that are not in the standard bb.

Post has been editedgorilloid - 11.07.16, 04:15