unzip error !

magisk 25.2

After installation, i generate key and rsa_id in root/authorized_keys and shell/authorized_keys. But still i can't connect SSH from remote and it said Permission denied (publickey,keyboard-interactive). Do you have any idea?

Hello!
I believe that the module stopped working after Magisk 17.0 update.
The issue might be the removal of /magisk symlink.

C:\Users\User\Desktop\platform-tools>adb shell /sbin/.core/img/ssh/opensshd.init start
starting /magisk/ssh/usr/bin/sshd... /sbin/.core/img/ssh/opensshd.init: Error 127 starting /magisk/ssh/usr/bin/sshd... bailing.
/sbin/.core/img/ssh/opensshd.init[90]: /magisk/ssh/usr/bin/sshd: not found

All the best!

If you are manually start/stopping the sshd-service, /opensshd.init start won't work. Running the service script will, by using /magisk/ssh/service.sh start. You will however need to give the script file execute permission. You can do this at a terminal by changing the working directory; cd /magisk/ssh , and then assigning the execute permission to the script file chmod +x service.sh. OR you can do all this on a file explorer with root access.

I installed it on miui 11 on a Redmi Note 8 via magisk.

I can login with ssh but when i try to use Rsync this is what i get:

#As root
:/data/ssh/root # rsync
CANNOT LINK EXECUTABLE "rsync": library "libcrypto.so.1.1" not found

#As shell
:/data/ssh/shell $ rsync
sh: rsync: not found

Any idea how to fix it ?

Please consider creating releases tags in this repository

I want to login as user u0_a169, I

• created /data/ssh/u0_a169/.ssh/authorized_keys
• chowned it to u0_a169:u0_a169
• chmod 600 it

But it still doesn't work

~ $ ssh [email protected]
[email protected]: Permission denied (publickey,keyboard-interactive).

shell@mx4:/ $ getprop |grep sdk
[ro.build.version.sdk]: [22]
[ro.mediatek.version.sdk]: [4]
shell@mx4:/ $ getprop |grep cpu
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: []
[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]

/data/adb/modules/ssh/opensshd.init start <
starting /data/adb/modules/ssh/usr/bin/sshd... WARNING: linker: /data/adb/modules/ssh/usr/bin/raw/sshd: unused DT entry: type 0x6ffffffe arg 0x3cc4
WARNING: linker: /data/adb/modules/ssh/usr/bin/raw/sshd: unused DT entry: type 0x6fffffff arg 0x2
WARNING: linker: Unsupported flags DT_FLAGS_1=0x9
WARNING: linker: libcrypto.so.1.1: unused DT entry: type 0x6ffffffe arg 0x3256c
WARNING: linker: libcrypto.so.1.1: unused DT entry: type 0x6fffffff arg 0x2
CANNOT LINK EXECUTABLE: cannot locate symbol "openpty" referenced by "/data/adb/modules/ssh/usr/bin/raw/sshd"...
/data/adb/modules/ssh/opensshd.init: Error 1 starting /data/adb/modules/ssh/usr/bin/sshd... bailing.

Basically what the title says. I've installed the module through Magisk Manager.

Magisk version: v18.1 (18100)
Magisk Manager version: v7.0.0 (185)
SSH for Magisk version: v0.7

Furthermore if trying to start the service manually on adb shell (as root) it bails without starting:

/sbin/.magisk/img/ssh # sh opensshd.init start
opensshd.init[89]: /sbin/.magisk/img/ssh/usr/bin/ssh-keygen: can't execute: Permission denied
opensshd.init[89]: /sbin/.magisk/img/ssh/usr/bin/ssh-keygen: can't execute: Permission denied
opensshd.init[89]: /sbin/.magisk/img/ssh/usr/bin/ssh-keygen: can't execute: Permission denied
opensshd.init[89]: /sbin/.magisk/img/ssh/usr/bin/ssh-keygen: can't execute: Permission denied
starting /sbin/.magisk/img/ssh/usr/bin/sshd... opensshd.init[89]: /sbin/.magisk/img/ssh/usr/bin/sshd: can't execute: Permission denied
opensshd.init: Error 126 starting /sbin/.magisk/img/ssh/usr/bin/sshd... bailing.

In Android 9, I think, I could access files from my work profile. Now I can't (it's garbage looking names only).

How can I access all user files, not just the main user?

When copying (SFTP) files of large size (> 2GB), the size of the copy file is limited to 2GB without an error message ...

I can't login as root or shell. It works on my old phone, but not my new one with Android 10.

Placed key in both /data/ssh/root/.ssh/authorized_keys and /data/ssh/shell/.ssh/authorized_keys

chmodded both to 0600.

Is there a way to see the ssh log?

First generate a key pair using ssh-keygen

1. Get the public key (assuming it's named id_rsa.pub) from your computer (in $HOME/.ssh/ folder assuming you are on Linux), to your phone.

2. Copy the contents of your public key inside your phone using root browser's text editor or any other text editor of your choice.

3. Create a file named authorized_keys inside the /data/ssh/root/.ssh/ folder.

4. Paste the contents of your public key into the authorized_keys file using the text editor of your choice.

5. Copy that file into the /data/ssh/shell/.ssh/ folder if you want shell login too.

6. Now to login into your phone using ssh, you need the private key (assuming it is named id_rsa) that was generated with your public key. Type this command onto your computer in the same folder as your private key file. ssh -i id_rsa root@[_your phone's local ip_]. You don't need to type the -i id_rsa if you private and public key file is in your computer's $HOME/.ssh/ folder.

You got yourself a perfectly functioning key with right permissions! (Unless you didn't follow the instructions correctly)

https://github.com/Magisk-Modules-Repo/ssh/blob/master/install.sh#L158-L161
These directories are not deleted when uninstalling. So an uninstall.sh file should be created which should remove extra dirs that Magisk won't remove on uninstall.

Possibly the cause of other posts related to "sshd not running": Especially after installing updates of ssh for Magisk did sshd fail to start on next device boot. The cause has been found to be a stale /data/ssh/sshd.pid file. After deleting that file manually, sshd will run on next boot, and can alternatively be manually launched by executing opensshd.init
Path of opensshd.init doesn't match the path specified in the instructions. This may be due to Magisk hidden on my system. I find it it here: /sbin/.magisk/img/ssh/opensshd.init
My workaround for the pid problem is now to let shutdown trigger execution of rm -f /data/ssh/sshd.pid

Just in case if you are not aware, a completely new Magisk Module Installer replaces the old Magisk module template. This new format decouples ALL installation logic from modules, and encourages developers to use the provided API for installation. This new format is ENFORCED, meaning all existing modules should upgrade ASAP, and new modules are REQUIRED to follow the rules.

Carefully read through the updated docs!

Warning: All existing modules that does not use the new module format will be automatically removed on May 1st, 2019. Module devs: upgrade your existing modules ASAP!

P.S. This issue is just a kind reminder, you can close it after reading this message :)

I can run it manually with /data/adb/modules /ssh/opensshd.init start, but since upgrade from LineageOS 16 to LineageOS 17 it doesn't autostart anymore.

SSHD is not starting/running because execute permission is not set for files in raw directory

Missing in config.sh after copying files and making links:
set_perm_recursive $MODPATH/usr/bin/raw 0 0 0755 0755

config_fixed.txt

Though it is trivial, changing permission of authorized_keys is necessary to login to ssh
A sudo chmod 600 /data/ssh/root/.ssh/authorized_keys will do the trick

This old bug affects both scp and sftp. It has persisted since at least 2019.

This module seems to be broken on the latest Magisk Canary build MagiskManager v7.5.2-ed58cf95(274) and Magisk 20.4 ed58cf95 (20304)

With this module i can login, but ssh is not in the path. (Is at /data/adb/modules/ssh/usr/bin/ssh)

My computer is a desktop computer, because the network settings cannot make the computer and mobile phone under the same LAN

Gives me the following output for both shell and root:

ssh [email protected]
mktemp: Failed to create file /tmp/tmp.M1EJnqCXFr: No such file or directory
sh: can't create : No such file or directory
rm: Needs 1 argument (see "rm --help")
sh: tic: inaccessible or not found
Connection to 192.168.209.94 closed.

I have this module working perfectly on 12 atvs with android 64bits 7.1.2

Today I setup an Android 32bits 9 box and when I try to connect I get "unable to negotiate cypher" and was offered a list of old protocols. I added those old protocols to my config file but then the atv offered OTHER cyphers like ssh-rsa and ssh-dsa. No matter what cyphers I add to the client, the atv will offer others.

I don't understand how this more recent atv isn't able to negotiate a cypher like all others. My install was exactly the same.

Hi, it seems the service is not starting:

When trying to start with ./sbin/.magisk/img/ssh/opensshd.init start I get an error message:
Privilege separation user sshd does not exist

(oneplus with lineageos 15.1)

Any idea's?

Greetimgs René

Module is installed, keys are in place, when I try to connect I get:

lemmy@akari:~/Work/susebuildservice/home:lemmy04/Telegram> ssh root@s8
/system/bin/sh: Permission denied
Connection to s8 closed.

ssh-ing in as the shell user works tho.

there are no releases in the release section

How can i add more PATHs? Is there something like a .bashrc?

I'm trying to use scp to transfer files to my phone but all I get is this error:
CANNOT LINK EXECUTABLE "scp": CANNOT LINK EXECUTABLE "scp": library "libcrypto.so.1.0.0" not found

rsync works...

Running Magisk 18, Android 8.0.0 on a Galaxy S8+

Any ideas?

When I installed the module it was chowned by root. I could not log on as shell via ssh until I chowned the directory to shell. It looks like sshd was unable to read ,ssh/authorized_keys until I did so.

The scp command does not work.
It shows:
/usr/local/bin/ssh: No such file or directory
lost connection

The reason is, that scp looks for ssh and cannot find it, as the path of ssh is hardcoded in
/data/adb/modules/ssh/usr/bin/raw/scp as "/usr/local/bin/ssh"

ssh and rsync work fine.

Thank you for the module.

my phone was installation failed,does it not support higher magisk?my magisk is 20.4.
install.sh,customize.sh?

dear maintainer team

i have to change MODDIR path from /magisk/ssh to /sbin/.core/img/ssh in the opensshd.init file to make the script to work
#: ${MODDIR:=/magisk/ssh}
: ${MODDIR:=/sbin/.core/img/ssh}

device: xiaomi redmi note 3
magisk: 18 stable
os: mokee 7.1

thanks

if sshd is set to listen on VPN IP adress, it will not launch. probably because sshd tries to run before the vpn interface is brought up during boot by android, doesn't see the IP valid, and bails.

i'm using with wireguard, set to "always on" in android settings.

PixelExperience_caf_whyred-9.0
Magisk 19.2

Can not run some su CMDs over SSH shell, but over ADB everything is OK
The error gives a sign of 'Aborted'
Have been using SSH-Module for some time now, started giving this error recently

Examples:
media volume --stream 2 --set 5
input keyevent KEYCODE_HOME
input swipe 530 1962 533 1962 100
content insert --uri content://settings/system --bind name:s:show_touches --bind value:i:0

LOGCAT.txt

So I installed Magisk and the ssh module on a stock firmware Galaxy S7,

I generated a private/public keypair using puttygen, pasted the public key in /data/ssh/.ssh/root/authorized_keys and used the generated private key in putty in order to connect to root@, but server keeps refusing my key.

I have used this module numerous times and suddenly, now, it doesn't work.

Any ideas?

Besides the permissions of authorized_keys, in my device it was also needed to change the permissions of the parent directories as well as their ownership for the ssh login to work.

More Specifically .ssh and root or shell (depending on which you are going to use).

So we got:

chmod 600 /data/ssh/root/.ssh/authorized_keys
chmod 600 /data/ssh/shell/.ssh/authorized_keys

chown root /data/ssh/root/.ssh/authorized_keys
chown shell /data/ssh/shell/.ssh/authorized_keys

chmod 700 /data/ssh/root/.ssh
chmod 700 /data/ssh/shell/.ssh

chown root /data/ssh/root/.ssh
chown shell /data/ssh/shell/.ssh

chmod 700 /data/ssh/root
chmod 700 /data/ssh/shell

chown root /data/ssh/root
chown shell /data/ssh/shell