Confused with SUDO and users after FW 3.3.0

Drobo - End of Sale Drobo 5N
1

Hello,

I finally managed to SSH to my Drobo after reading these threads:
http://www.drobospace.com/forums/showthread.php?tid=144858
http://www.drobospace.com/forums/showthread.php?tid=145005
Yet I’m really confused as I can’t [font=Courier]cd[/font] anymore to my data folders like this one:
[font=Courier]drwx—S— 15 root root 4096 Oct 23 13:48 Movies[/font]

I did not change anything in the various files, just logged with the admin and pass from my Drobo Dashboard (well, I think that’s what I did).
I previously had installed the sudo package. I’ve just uninstalled it now.

I’ve checked on the files from the threads, here they are for reference:
/etc/shadow

daemon:*:10933:0:99999:7::: avahi:*:10933:0:99999:7::: sshd:*:10933:0:99999:7::: root:!*:10933:0:99999:7::: nobody:*:10933:0:99999:7::: GeJe:781W2ih/10Qlk:16734:0:99999:7::: mysql:!:16734:0:99999:7:::

/etc/sudoers

root ALL=(ALL) ALL %wheel ALL=(ALL) NOPASSWD: ALL #includedir /mnt/DroboFS/System/sudoers.d

/etc/group

root:x:0:root daemon:x:1:daemon wheel:x:10:root nobody:x:99:nobody,mysql nogroup:x:99: avahi:x:100:avahi GeJe:x:1000:

/mnt/DroboFS/System/sudoers.d contains [font=Courier]admin[/font]with the following content:

GeJe ALL=(ALL) ALL

So, how could I have a user than can run commands as before, and of course [font=Courier]cd[/font] to data directory as the Finder does (yes, I can still browse with Finder) ?

One final note here: since the update, I’ve lost all the personal icons over folders I’ve customized. Only personal icons on files survived.

I thank you for looking at this issue.

2

Okay,
I’ve finally used the sudo passwd method to re-enable the root. It works so far, so thank you Ricardo!

3

Can you post what exactly you did? I just recently upgraded my firmware, now I can no longer access my Drobo via the Root user, since it seems to be disabled by default now.

I tried:
sudo passwd = [adminUser] not in sudo’ers list
passwd root = must be a value suid.

Connected via OpenSSH using my Admin users login credentials.

For anyone that reads this and wondering why I need this, well I a RPi2 connecting to my Drobo via SFTP, which has some services running on it that write/read/move files around. My Drobo is not accessible by the outside world, so I don’t care about the whole security issues with enabling root again. Just need to know how.

Drobo 5N
Firmware: 3.5.6 [8.84.79430]

4

hi drofnas,
there was another raspberry pi user who recently managed to get a connection to work when using cifs.
am not sure if it helps in your case but here is a link for you:
http://www.drobospace.com/forums/showthread.php?tid=145722

5

Well I actually have come to no definitive solution as I have to use the passwd command after every reboot.
Something is most probably wrong with my sudoers and admin group, but I couldn’t find a tutorial clear enough to me to figure out what I need to check :confused:

6

Had an issue after 3.3 with my sudo as well. The right thing to do is uninstall sudo via the Dashboard, but if you want some more knowledge, keep reading.

As everyone knows, 3.3 turns off root, but I had the DroboApps version of sudo installed (and I was remote, so no Dashboard). So after I upgraded, sudo [command] was no longer working. That’s because it was trying to run the DroboApps version of sudo and not the native command.

To check if your sudo is DroboApps, which sudo should return /bin/sudo. If it does returns /mnt/DroboFS/Shares/DroboApps/sudo/bin/sudo, you are running the DroboApps version.

To use the REAL sudo, just use the command /bin/sudo. In Linux, by default, it searches your PATH for the application, but if you specific the location, it will use that application. You may be confused because you have multiple versions of sudo installed (DroboApps version, and native) but you had no way of knowing.

The more confusing thing, is that the DroboApps version is using the configuration from the DroboApps directory, but the native version is reading from the native directories /etc/sudoers which includes /mnt/DroboFS/System/sudoers.d.

So, first step is to use the REAL sudo. And, for now, you have to run it with the full path, so /bin/sudo su - will get you to root, from there, you win.

Secondly, uninstall the DroboApp version of sudo. You should do it via the Dashboard, but you can do it through the command-line now that you have root access. Just rm -rf /mnt/DroboFS/Shares/DroboApps/sudo/.

The reason the DroboApps version of sudo was running “first”, rather than the native one, was because of your PATH. It is the variable that searches for applications in certain directories. I had the DroboApps version of bash installed, which has a file /mnt/DroboFS/Shares/DroboApps/bash/etc/droboapps.profile when read, PREFIXes all the DroboApps to the PATH. Which means it will run the DroboApp version before the native version.