Hi,
I was trying to install docker-compose and other components and found that there is no package manager or run cURL commands, no sudo. How can those be installed? This will help make Terra Master powerful development environment.
Missing package manager, cURL, Sudo.
Re: Missing package manager, cURL, Sudo.
Hi, you cannot use this cmd sudo when SSH login as admin, while you can login as root ( the login password is the same as admin).
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Missing package manager, cURL, Sudo.
I had logged into the root, but still not able to use sudo.
- Attachments
-
- sudoNotFound.png (20.84 KiB) Viewed 5663 times
-
- sudoNotFound.jpg (17.05 KiB) Viewed 5663 times
Re: Missing package manager, cURL, Sudo.
sudo is not supported in TNAS.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Missing package manager, cURL, Sudo.
As TOS is not a complete Linux system, it does not contain all Linux modules, for example sudo is not included.
One interesting question: you can login the TOS as a root user, why you still need sudo?
One interesting question: you can login the TOS as a root user, why you still need sudo?
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Missing package manager, cURL, Sudo.
Opening root login, particularly on remote sessions like SSH is a security risk for the device: most distribution prevent that for good reasons.
sudo is a more commonly accepted method to run few ad-hoc commands as root: it also ensures you do not stay root when you need (or should) not.
So, adding sudo, and disabling root login & ssh would definitely be desirable for security concerns.
BTW: root motd has a typo: Wellcom to TNAS: should be: Welcome to TNA
TerraMaster F2-210 under TOS 4.2.43, RAID1, Btrfs, serving Mac, Linux & Windows clients
Re: Missing package manager, cURL, Sudo.
It's "Welcome to TNAS" actually.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Missing package manager, cURL, Sudo.
We found it's Wellcom as you posted with ARM models, and it will be fixed soon. Thank you.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Missing package manager, cURL, Sudo.
Ok.
Now, the most critical thing, for security reason is probably to disable any remote root login (ssh in particular).
Thanks.
Now, the most critical thing, for security reason is probably to disable any remote root login (ssh in particular).
Thanks.
TerraMaster F2-210 under TOS 4.2.43, RAID1, Btrfs, serving Mac, Linux & Windows clients
- JayBlingham
- Posts: 98
- Joined: 04 Oct 2020, 10:34
Re: Missing package manager, cURL, Sudo.
I agree that disabling root SSH/remote login is the more secure way to go, but I also agree with TM that implementing commands like sudo and the like are just setting them up to have to start supporting users at the command line when things don't work (or they break stuff due to inexperience). As I've said before, these devices are not Linux servers, they're meant to be NAS appliances. I love that TM gives us the ability to hit the command line and dive into some more advanced configurations on our own, but it shouldn't be made easier for novices to break things.
Just brainstorming possible options here at 7:30AM while watching the internet panic because Google services are down:
Option 1:
Enable sudo, disable remote root SSH, admin account gets sudo/ssh by default, CLEAR disclaimer that anything done via command line is the user's responsibility and TM is not liable for data loss. Support for Linux command line is "best-effort", or Forum (community) based only.
Option 2:
Disable remote root SSH, add option to TOS to enable root login when/if needed for those that require cli occasionally.
Anyone have any other creative suggestions to satisfy both sides? I've logged into SSH a few times, but only because I find it easier to move data around, and set permissions recursively. I could honestly live without it, but understand the value.
Just brainstorming possible options here at 7:30AM while watching the internet panic because Google services are down:
Option 1:
Enable sudo, disable remote root SSH, admin account gets sudo/ssh by default, CLEAR disclaimer that anything done via command line is the user's responsibility and TM is not liable for data loss. Support for Linux command line is "best-effort", or Forum (community) based only.
Option 2:
Disable remote root SSH, add option to TOS to enable root login when/if needed for those that require cli occasionally.
Anyone have any other creative suggestions to satisfy both sides? I've logged into SSH a few times, but only because I find it easier to move data around, and set permissions recursively. I could honestly live without it, but understand the value.
Jay
---------------------------------------
F5-221, 5.0.171-00221
---------------------------------------
---------------------------------------
F5-221, 5.0.171-00221
---------------------------------------