- Individual Applications
Protect
Filter
Perform
Connect
Add-Ons
- Software Packages
- Complete Appliances
|
|
#2 (permalink) | |||
|
Master Untangler
Join Date: Dec 2007
URLs submitted: 1
Posts: 202
![]() |
I believe it also runs the rbot ruby program which maybe a security issue. I don't think anybody at Untangle has officially commented on rbot, but I did start a thread regarding it.
You can leave support disabled and manually create symlinks to start ssh. FWIW, the ssh that Untangle starts is susceptible to brute force attacks since it allows root access and every cracking script will try to login as root (among other often used usernames such as, believe it or not "fluffy"). You might want to take a look at the DenyHosts statistics page: http://stats.denyhosts.net/stats.html which shows over 111,000 unique hosts that have launched brute force attacks against SSH servers. One way of securing the SSH server on Untangle is to make it accessible only to the internal interface (such that nobody can connect to it from a remote server). To do so, edit the file /etc/ssh/sshd_config: Comment out the existing ListenAddress: Quote:
Quote:
Quote:
|
|||
|
|
|
|
#3 (permalink) |
|
Master Untangler
Join Date: Dec 2007
Posts: 102
![]() |
Well my goal is to access that box from work, we run a number of external websites here so it's more aof a convenience thing to be able to SSH tohome, then validate a url thru Lynx. I realize there's probably many other ways to do that, this was is comfortable.
However symlinks are over my head ![]() So if I want to setup a more secure SSH should I disable the gui's Remote Support" and just setup a normal SSHD? |
|
|
|
|
#4 (permalink) | |
|
Master Untangler
Join Date: Dec 2007
URLs submitted: 1
Posts: 202
![]() |
Quote:
Alternatively, you could setup another user on Untangle (using "useradd") and disable root logins which is notoriously BAD in /etc/ssh/sshd_config: <quote> PermitRootLogin no </quote> This way, you could SSH into Untangle externally but as a non-root user. If you require root access, use "sudo" once logged in. |
|
|
|
|
|
#5 (permalink) |
|
Master Untangler
Join Date: Dec 2007
Posts: 102
![]() |
ok i editted the sshd_conf file and change the permitrootuser to no. however right now I am unable to ssh into the box...remote support is enabled but its non responsive.. I was checking my config and I noticed how Im showing an Internal and a DNZ interface are linked up. This box only has two nics so I wonder if the fact that according to Untangle it's External interface has no link and is in a down state have anything to do with my issues? Is there a way I can totally remove the DMZ?
|
|
|
![]() |
| Thread Tools | |
|
|