Site Tools


admin_access

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
admin_access [2023/06/23 21:28] – [SSL Certificate] -condense hogwildadmin_access [2023/06/23 21:33] (current) – [SSH Daemon] -condense, formatting hogwild
Line 66: Line 66:
 ===== SSH Daemon ===== ===== SSH Daemon =====
  
-Secure SHell is a tunneling protocol that allows you to make secure local and remote connections to the FreshTomato router. With the help of the Dropbear service, it also allows you to make SSH connections //though //the router, to LAN client devices. Setings in this section let you enable or disable the SSH Daemon and the Dropbear daemon, and configure their operation.+Secure SHell is a tunneling protocol that allows you to make secure local and remote connections to the FreshTomato router. With the help of the Dropbear service, it also allows you to make SSH connections //though //the router, to LAN clients. Setings here enable or disable the SSH and the Dropbear daemon, and configure their operation.
  
 **Enable at Startup:** Checking this starts the SSH Daemon when the router boots. (Default: Enabled). **Enable at Startup:** Checking this starts the SSH Daemon when the router boots. (Default: Enabled).
  
-**Extended MOTD:** Checking this enables the Message of the Day function. This function displays a custom message when you first log in via Telnet. The message can be can be important information or updates about the system or just a personal greeting from the system administrator.+**Extended MOTD:** Checking this enables the Message of the Day function. This displays a custom message when you first log in via Telnet. The message can be important informationupdates about the system or just a personal greeting.
  
  \\  \\
Line 84: Line 84:
 For example, let's say you want to be able to access a Windows PC on your LAN via Remote Desktop, but you don't want the security risk of opening up a port for RDP to the Internet via standard Port Forwarding. Instead, you can make an SSH connection into the router with an SSH port tunnel/forward configured (example: 127.0.0.1:1234 gets tunnelled/forwarded through SSH to 192.168.1.66:3389. This way, when you're connected via SSH to the router, you can open up RDP on the machine running the SSH client, and connect to 127.0.0.1:1234 and you're securely connected to 192.168.1.66 on your LAN. All traffic flows through SSH, and thus is encrypted. (RDP already uses encryption, but it's weaker than that provided by SSH). For example, let's say you want to be able to access a Windows PC on your LAN via Remote Desktop, but you don't want the security risk of opening up a port for RDP to the Internet via standard Port Forwarding. Instead, you can make an SSH connection into the router with an SSH port tunnel/forward configured (example: 127.0.0.1:1234 gets tunnelled/forwarded through SSH to 192.168.1.66:3389. This way, when you're connected via SSH to the router, you can open up RDP on the machine running the SSH client, and connect to 127.0.0.1:1234 and you're securely connected to 192.168.1.66 on your LAN. All traffic flows through SSH, and thus is encrypted. (RDP already uses encryption, but it's weaker than that provided by SSH).
  
-**Port: **Here, you can enter the port number on which you want SSH traffic to flow. (Default: 22). Changing the port from the default is highly recommended, as port 22 is being constantly scanned by Internet hackers.+**Port: **Here, can enter the port number on which SSH traffic will flow. Changing from the default is recommended, as port 22 is being constantly scanned by hackers. (Default: 22).
  
-**Allow Password Login: **Checking this allows clients to login via SSH with only FreshTomato'normal username and password. No authorized encryption key is needed. When disabled, SSH will require an authorized key to allow a client to log on.+**Allow Password Login: **Checking this let clients login via SSH with only the normal administrative username and password. No authorized encryption key is needed. When disabled, SSH will require an authorized key to allow log on.
  
 **Authorized Keys:** Here you can enter one or more encryption keys which authorize an SSH client to access to the LAN. **Authorized Keys:** Here you can enter one or more encryption keys which authorize an SSH client to access to the LAN.
  
-**Stop Now:** Clicking this button immediately stops the SSH daemon. SSH will start again at the next bootup.+**Stop Now:** Clicking this button immediately stops the SSH daemon. SSH will start again at the next bootup. After clicking Stop Now, the button will display as "Start Now". Clicking this will immediately start the SSH daemon.
  
  
admin_access.txt · Last modified: 2023/06/23 21:33 by hogwild