Access to DSS server command shell

[enealDC]

Open-E I've been thinking about this a-lot. I believe you should give an advanced shell to customers.
I can understand making this restriction on an appliance, but Open-E *is* software. So I can't understand why the restriction. In other words, it's *not* in my best interest that I don't have access to the command line.
Let's look at other software products that give you access to a command shell that run on Linux and are as complex (if not more) than Open-E.

VMWARE ESXI
OracleVM
Virtual Iron (now a part of Oracle VM)

And a few others that I can't think of

I believe you guys need to strongly consider this....

[DIESOFTWARE-RS]

Strongly agree.

Regards

[DIESOFTWARE-RS]

But since ANY request regarding "root shell" NEVER received ANY acceptable response from OPEN-E in the past
and obviously will also not in the future and because we got a little upset about that,
we did a little investigation to possibly solve the "problem" ourselfs.

OPEN-E support does in fact have the option to shh to the nas via remote support.
And here is how they do it:

root 26933 0.0 0.0 2464 1172 ? Ss 10:16 0:00 /bin/bash /var/nasexe/administration_start
root 26971 0.0 0.0 2868 1080 ? S 10:16 0:00 \_ /var/nasexe/kbtest
root 2828 0.0 0.0 3216 1980 ? S 12:43 0:00 \_ /bin/bash /var/nasexe/admintools
root 11096 0.0 0.0 4152 1132 ? S 13:32 0:00 \_ /usr/bin/scp -i /home/support/.ssh/id_rsa -P 65500 /etc/motd notificator@83.18.247.42 /home/notificator/tickets/ticket
root 11097 0.0 0.0 4372 1624 ? S 13:32 0:00 \_ /usr/bin/ssh -x -oForwardAgent no -oPermitLocalCommand no -oClearAllForwardings yes -i/home/support/.ssh/id_rsa -p65500 -lnotificator 83.18.247.42 scp -t /home/notificator/tickets/ticket

and

root 29390 0.0 0.0 4852 1096 ? Ss 11:53 0:00 /usr/sbin/sshd -f /etc/ssh/HB_sshd
root 11058 0.0 0.0 4852 1048 ? Ss 13:32 0:00 /usr/sbin/sshd -o PidFile=/var/run/sshd_rss.pid -f /var/nasconf/rss/sshd_config_rss
root 11062 0.0 0.0 3368 1384 ? S 13:32 0:00 /usr/bin/ssh_rss -2 -p 65500 -o ConnectTimeout=1 -n -N -R 44400:localhost:65535 supporter@83.18.247.42 -F . -i /home/support/.ssh/id_rsa

and

[quote
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:40000 0.0.0.0:* LISTEN 29390/sshd
.
.
tcp 0 0 127.0.0.1:65535 0.0.0.0:* LISTEN 11058/sshd
[/quote]

Let's see, how we get further now.

Regards

[adamvh]

Hi,

Yes I agree we should be given a full root access.
Having these restricted cli and api logins just isn't good enough.

As a competent linux admin I find it frustrating than I cannot get behind the scene to perform minor configurations/tweaks. There is many basic samba changes that are not possible via any presented interfaces to your software.

-Adam