Web Hosting Talk : Web Hosting Main Forums : Reseller Hosting : SSH is unsecure? why not use SSH?

[DewlanceHosting]

hi,

i have one master reseller hosting(No SSH access)


and also i have One Dedicated Server (Personal - Testing Server only, no website) from InternetGateway(Full SSH Root Access)


i am use SSH for installing scripts(like awstat,cPanel,config,etc)
example: wget http://....site...tar.gz


this is secure? or never use ssh for security reason?

[inspiron]

If you are concerned about your ssh security better one the good thing you can do to secure your ssh. You should change your ssh port no from sshd_config file. This can be advantage for you to reduced the attack.

[SSHocker]

Should be fine as long as your dedicated server is secure

[njoker555]

Secure Shell...

And changing ports as suggested above helps a lot. Just make it a random high number and you should be fine.

[fabrini]

You can further secure your SSH by disabling password based login and generating a key pair for authentication. I'd also recommend disabling the root account from connecting via SSH. Create a new account and SSH into that one, then su to root, or sudo when you need to run something as root.

[e-Sensibility]

Originally Posted by njoker555

Secure Shell...

And changing ports as suggested above helps a lot. Just make it a random high number and you should be fine.

A lot of people are under the impression that changing the port will help -- but it won't.

-Keep out the brute-forcers with firewall restrictions
-Disable password auth/enable public key auth

Period. Any script-kiddy who knows how to point and click can find out what alternate port an SSH Server is running on.

[LVPSHosting]

You can also block all IP addresses in the firewall, except your IP address, or if you are using dynamic IP, your class of IP addresses and you should be fine.

[MikeDVB]

Originally Posted by e-Sensibility

A lot of people are under the impression that changing the port will help -- but it won't.

-Keep out the brute-forcers with firewall restrictions
-Disable password auth/enable public key auth

Period. Any script-kiddy who knows how to point and click can find out what alternate port an SSH Server is running on.

Changing the port alone won't help without a login failure daemon + port scan detection.

The PSD will block most before they find the right port and the LFD will block those that find it and try to log in with incorrect credentials.

Changing the port alone is just security thru obscurity but anybody really wanting in will find it.

[ImPr3zA]

SSH is generaly crypted

[aeris]

Originally Posted by e-Sensibility

A lot of people are under the impression that changing the port will help -- but it won't.

Well, it does help, at least by preserving your sanity when reviewing logs. When I changed the port on my servers to a different one, random login attempts went from hundreds a day per server, to 0.

[keserhosting]

Also edit the /etc/ssh/sshd_config file ,

Allow only Protocol 2:

Protocol 2

Protocol 1 is less secure and obsolete.

[mellow-h]

i am use SSH for installing scripts(like awstat,cPanel,config,etc)
example: wget http://....site...tar.gz


this is secure? or never use ssh for security reason?

As long as you know what you are doing, I am sure it is secure

[M Bacon]

Do not give your clients shell. Just give yourself shell. It probably would make you feel better in the long run.