Dashboard opens with blank only

[fvdw]

seems you are trying to login with user fausto

Code: Select all

2021-03-26 09:24:09   Will enable zlib (RFC1950) decompression after user authentication
2021-03-26 09:24:13   Entered username: Fausto
2021-03-26 09:24:13   Server supports following auths:  publickey password keyboard-interactive
2021-03-26 09:24:13   Attempting keyboard-interactive authentication
2021-03-26 09:24:13   Server refused keyboard-interactive authentication
2021-03-26 09:24:13   Server supports following auths:  publickey password keyboard-interactive
2021-03-26 09:24:16   Sent password
2021-03-26 09:24:16   Initialised delayed zlib (RFC1950) decompression
2021-03-26 09:24:16   Initialised delayed zlib (RFC1950) compression
2021-03-26 09:24:16   Access granted with AUTH_TYPE_PASSWORD
2021-03-26 09:24:19   Requesting activation of MobaXterm remote monitoring...

That probably fails because user fausto is not entitled to login via ssh
You can see this in file /md8/etc/passwd, the line with fausto probably ends with /bin/false meaning no shell opening is disabled
Why don't you use user root ?
root is entitled to get a shell I expect but to be sure please post the content of
md8/etc/passwd and /md8/etc/shadow

[fariaslcfs]

Can you try to specify your own command:

Code: Select all

ssh <user>@<ip-address>  /bin/sh -i

And can you try if you can connect using scp? On Windows you can use WinSCP for that, on Linux scp.

Code: Select all

scp <user>@<ip-address>:/bin/sh .

should copy /bin/sh from the NAS to your local directory.

Hi @Mijzelf
With PuTTY, I just entered the ip, and then the black screen opens, asking for login and password.
I think the commands you stated above are used after the session successfully started, isn't it?
The problem is that the session closes as soon as the login and password are accepted.

[fariaslcfs]

seems you are trying to login with user fausto

Code: Select all

2021-03-26 09:24:09   Will enable zlib (RFC1950) decompression after user authentication
2021-03-26 09:24:13   Entered username: Fausto
2021-03-26 09:24:13   Server supports following auths:  publickey password keyboard-interactive
2021-03-26 09:24:13   Attempting keyboard-interactive authentication
2021-03-26 09:24:13   Server refused keyboard-interactive authentication
2021-03-26 09:24:13   Server supports following auths:  publickey password keyboard-interactive
2021-03-26 09:24:16   Sent password
2021-03-26 09:24:16   Initialised delayed zlib (RFC1950) decompression
2021-03-26 09:24:16   Initialised delayed zlib (RFC1950) compression
2021-03-26 09:24:16   Access granted with AUTH_TYPE_PASSWORD
2021-03-26 09:24:19   Requesting activation of MobaXterm remote monitoring...

That probably fails because user fausto is not entitled to login via ssh
You can see this in file /md8/etc/passwd, the line with fausto probably ends with /bin/false meaning no shell opening is disabled
Why don't you use user root ?
root is entitled to get a shell I expect but to be sure please post the content of
md8/etc/passwd and /md8/etc/shadow

Hi @fvdw.
True, I was just trying with "admin" and "Fausto", and forgot "root".
However, all times "root" was tried were not successful.
Next week, I'll try then with "root".
However, what password shall I use? Anyone of "admin" or "Fausto"?

[fvdw]

you should use password :

Code: Select all

admin

be sure not to use capitials as passwords are case sensitive

[fvdw]

and please post the content of
md8/etc/passwd and /md8/etc/shadow

[Mijzelf]

Can you try to specify your own command:

Code: Select all

ssh <user>@<ip-address>  /bin/sh -i

And can you try if you can connect using scp? On Windows you can use WinSCP for that, on Linux scp.

Code: Select all

scp <user>@<ip-address>:/bin/sh .

should copy /bin/sh from the NAS to your local directory.

Hi @Mijzelf
With PuTTY, I just entered the ip, and then the black screen opens, asking for login and password.
I think the commands you stated above are used after the session successfully started, isn't it?
The problem is that the session closes as soon as the login and password are accepted.

No, these commands are run client side. Sometimes you can't start an ssh session because you can't get a pty allocated, or because the shell specified in /etc/passwd is (intentionally) broken. In that case the first option might give you shell access (not as powerful as running a shell on a 'real' pty, but usable), and the 2nd option might give disk access.

[fariaslcfs]

you should use password :

Code: Select all

admin

be sure not to use capitials as passwords are case sensitive

Hi! I'm back
Tried login "root" and password "admin" (both without quotes and lowercase).
Result: "Access denied"

and please post the content of
md8/etc/passwd and /md8/etc/shadow

Code: Select all

root@(fvdw-kirkwood):/md8/etc # cat passwd
root:x:0:0:root:/root:/bin/sh
bin:x:1:1:bin:/bin:/bin/false
daemon:x:2:2:daemon:/sbin:/bin/false
sync:x:5:0:sync:/sbin:/bin/sync
shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown
halt:x:7:0:halt:/sbin:/sbin/halt
operator:x:11:0:operator:/var:/bin/sh
sshd:x:22:22:sshd:/dev/null:/bin/false
nobody:x:65534:65534:Nobody:/:/bin/false
anonymous:x:65534:65534:Nobody:/:/bin/false
messagebus:x:101:101::/dev/null:/bin/false
haldaemon:x:102:102::/dev/null:/bin/false
avahi:x:103:103::/dev/null:/bin/false
admin:x:500:100:LaCie Ethernet Disk mini Admin:/home:/bin/false
root@(fvdw-kirkwood):/md8/etc # cat shadow
root:$1$$CoERg7ynjYLsj2j4glJ34.:12542:0:99999:7:::
bin:*:12488:0:99999:7:::
daemon:*:12488:0:99999:7:::
sync:*:12488:0:99999:7:::
shutdown:*:12488:0:99999:7:::
halt:*:12488:0:99999:7:::
operator:*:12488:0:99999:7:::
nobody:*:12488:0:99999:7:::
anonymous::12488:0:99999:7:::
messagebus:!:12488:0:99999:7:::
haldaemon:!:12488:0:99999:7:::
avahi:!:12488:0:99999:7:::
admin:$1$$CoERg7ynjYLsj2j4glJ34.:12488:0:99999:7:::


[fvdw]

And what is reponse if you try to login with user: admin and password: admin

If this gives remote host closed connection then modify in file /md8/etc/ passwd the admin line, replace /bin/false by by /bin/sh

It us curious that user fausto is not mentioned in passwd file as sshd daemon seems to accept that username and passwd. Maybe this old lacie firmware uses a different location for the passwd and shadow file?? :scratch

[Mijzelf]

Maybe this old lacie firmware uses a different location for the passwd and shadow file?? :scratch

In one of the upper layers of the layered filesystem.

[fvdw]

that must be then coming from partiton 7.

Fausto try to assemble an array from sdx7 and have a look in /md7/etc if there a passwd and shadow file is present, if yes post content please