Replies: 4 comments
-
The "remote problem" is not new, there are several ways to solve it. One thing first: Possible would be e.g.:
For Windows users you can use ssh + putty with tunnel options and a So you don't need a https-Web-If for the freetz-NG-Web-If, Das "Remote-Problem" ist doch nicht neu, es gibt mehrere Möglichkeiten dieses zu lösen. Eines vorweg: Möglich wäre z.B.:
Für Windows-Nutzer bietet sich ssh + putty mit Tunnel-Optionen + Browser an. Ein https-Web-If für das freetz-Web-If braucht es dafür also nicht unbedingt, |
Beta Was this translation helpful? Give feedback.
-
I know how to make one myself. |
Beta Was this translation helpful? Give feedback.
-
I mostly use the easy way via SSH (dropbear already works on the box) and putty/kitty as the gateway. |
Beta Was this translation helpful? Give feedback.
-
I use lighttpd for various local http/-s servers. It can forward with "mod_proxy" depending on http-subdir or http-hostname to a servers in the lan. Also you could use seprarate ssl certs for every host, or letsencrypt or le wildcard. An additional authentification is also possible eg
This even prevent bruteforce on this server as the host or subdir are not public. |
Beta Was this translation helpful? Give feedback.
-
I'm accessing the Freetz WebIF remotely on several boxes.
It's done with http which is a security-risk if somehow the connection is compromised.
Are there any plans put ssl in front?
I'm talking about a standardized solution selectable with make menuconfig.
Or is no-one interested in it?
Beta Was this translation helpful? Give feedback.
All reactions