The NetworkState boolean tells launchd to restart the tunnel whenever it exits, so as long as the network is up. KeepAlive helps launchd determine when a restart a failed process. The most interesting bits are the KeepAlive and LimitLoadToSessionType sections. It lives at $HOME/Library/LaunchAgents/-forwards Here’s the launchd configuration file I use to access my IRC bouncer running on a local port on a remote server. Furthermore, launchd can respond to environmental changes to start and stop your daemons depending on the presence of files or the state of the network. Luckily, launchd (MacOS’s version of an init system) makes it easy to set up background process to run automatically without any special privileges. On MacOS, the stock /etc/sudoers file doesn’t come configured to use an #includedir, so managing custom rules is cumbersome and subject to breakage during upgrades.
#Ssh tunnel keep alive password#
Sshuttle requires local administrative access to do its magic, and that means either entering your password when sshuttle starts or managing changes to your sudoers file. When you only need to manage a single tunneled port, however, the choice isn’t so clear. It’s more flexible than plain OpenSSH when it comes to managing access to multiple remote ports, and it’s a breeze to set up. In the past, I’ve used the excellent sshuttle to manage my tunneled SSH connections.
0 kommentar(er)
