no acces to the root by CPI , SSH off my NAS540 after firmware updateV5.21(AATB.13)

mike4088

hello All ,,

A few weeks ago my NAS 540 prompted me in the web-interface a that there is a new firmware update available V5.21(AATB.13) because critical security issues an installed it succesfully but after that , am not able to acces by CPI as administrator to acces the root by ssh , an will be directly forwarded to Busybox environment .. am i the only one who encounter this problem ? an how can solve this , i hope someone can help me with this .

Regards

Mike

Mijzelf

Your problem isn't clear. What did you get when logging in over ssh, and what do you get now?

mike4088

when o login with over ssh by CLI with my admin account , i come in the busybox environment an not directly in root off my NAS an have limited acces even i do : su root an give my password ,, iam still in busybox ?.. it looks like that there is something not working an my md0 md1 md2 are not correctly mounted ..?
I notice this after i updated the firmware ,

I also thought that maby the firware is not good installed an reinstalled the firmware again but that did not solve the issue

Mijzelf

It is normal, and has always been, that you get in a busybox environment when you login over ssh. When you execute 'su', you are still in a busybox environment, only with changed credentials.

Don't know what you mean by 'directly in root'. The data partitions are mounted on /i-data/<some-hex-code>/, where <some-hex-code> is the first 4 bytes of the GUID of the raid array hexadecimally printed.

mike4088

oke thanks for your answer , is it maby also an securty reason why zyxel configued it this way ,to prevent hacks from outside ??

If it belongs this way ..i will accepting it
do you have your self also an nas540 who has this ??

Mijzelf

do you have your self also an nas540 who has this ??

Yes.

is it maby also an securty reason why zyxel configued it this way ,to prevent hacks from outside ??

No. The shell is the most powerful utility in the box, and it's disclosed by ssh. (ssh stands for Secure SHell. Secure is about the encrypted connection. Not about the shell itself).

It's not clear to me what you expected to get on your ssh connection. By default you get the shell which is specified in /etc/password for the user who logs in. On a full blown Linux box that is in most cases bash. On embedded Linux busybox shell.