Can't SSH to Ubuntu Server 14.04.3 LTS on XenServer
-
@DustinB3403 Doh.....
-
@anonymous said:
@DustinB3403 Doh.....
Simple answer.
You should be able to install it with the CLI. I don't know the commands off hand but I'm certain it starts with
sudo apt-get install -
I have 99 reasons I hate Ubuntu.....
-
It is:
sudo apt-get install openssh-server -
Who uses Ubuntu without SSH?
-
Well IDK, but it's built to be used by a wide range of people... so it's easier to have the tech savvy select what they want, they to choose a base for everyone and force them to maintain it..
-
@anonymous said:
Who uses Ubuntu without SSH?
The DevOps world
-
@anonymous said:
@DustinB3403 With CentOS I just install and go....
CentOS is super easy for general use. Ubuntu is very complex and hard for general use. They are not comparable.
-
@scottalanmiller said:
@anonymous said:
@DustinB3403 With CentOS I just install and go....
CentOS is super easy for general use. Ubuntu is very complex and hard for general use. They are not comparable.
It depends on what you are used to dealing with. I don't have ti disable apparmor to diagnose issues in Ubuntu. I do have to disable SELinux to test issues in the CentOS world. I am still more comfortable running a Ubuntu server than I am a CentOS box, but I haven't come up against anything a quick google usually doesn't fix.
-
@dafyre said:
@scottalanmiller said:
@anonymous said:
@DustinB3403 With CentOS I just install and go....
CentOS is super easy for general use. Ubuntu is very complex and hard for general use. They are not comparable.
It depends on what you are used to dealing with. I don't have ti disable apparmor to diagnose issues in Ubuntu. I do have to disable SELinux to test issues in the CentOS world. I am still more comfortable running a Ubuntu server than I am a CentOS box, but I haven't come up against anything a quick google usually doesn't fix.
Sure, it has that one additional step. But turn that off one time and there you go. You could negate that with sudo on ubuntu.
-
@scottalanmiller said:
@dafyre said:
@scottalanmiller said:
@anonymous said:
@DustinB3403 With CentOS I just install and go....
CentOS is super easy for general use. Ubuntu is very complex and hard for general use. They are not comparable.
It depends on what you are used to dealing with. I don't have ti disable apparmor to diagnose issues in Ubuntu. I do have to disable SELinux to test issues in the CentOS world. I am still more comfortable running a Ubuntu server than I am a CentOS box, but I haven't come up against anything a quick google usually doesn't fix.
Sure, it has that one additional step. But turn that off one time and there you go. You could negate that with sudo on ubuntu.
I'm usually running in sudo -i on whatever Linux distro I am troubleshooting at the time, lol. Typing sudo all the time drives me crazy.
Edit: But you are right. But why simply disable tools that are built to make your system more secure?
-
@dafyre said:
Edit: But you are right. But why simply disable tools that are built to make your system more secure?
Because if you are choosing one distro because it has that off by default, why not choose the other one and disable it? The logic of "why disable it" would equally mean "avoid Ubuntu."
-
@scottalanmiller True. However, in Ubuntu, I generally don't have to disable AppArmor, as it isn't quite as spastic about security as SELinux.
(forgive my ignorance here, but aren't AppArmor and SELinux two different ways of doing the same thing? Don't want to be comparing apples & oranges).
-
Yes, AppArmor is the Suse way, SELinux is the Red Hat way.
-
@dafyre said:
@scottalanmiller said:
@anonymous said:
@DustinB3403 With CentOS I just install and go....
CentOS is super easy for general use. Ubuntu is very complex and hard for general use. They are not comparable.
It depends on what you are used to dealing with. I don't have ti disable apparmor to diagnose issues in Ubuntu. I do have to disable SELinux to test issues in the CentOS world. I am still more comfortable running a Ubuntu server than I am a CentOS box, but I haven't come up against anything a quick google usually doesn't fix.
The nice thing about SELinux is if you check /var/messages it usually tells you exactly what you need to do. Same on Fedora, the SELinux troubleshooting gui will pretty much give you commands to copy and paste.
