Closed GoogleCodeExporter closed 9 years ago
I suggest instead that Tunnelblick use the original DNS value to look up the
server
and reestablish the connection. Only if that fails should the original network
connection be restored, after notifying the user.
The user should be informed* that the secure connection is no longer being used,
otherwise they may think they have a secure connection when they do not. If the
"--redirect-gateway" OpenVPN directive has been specified, once the tunnel is
established no IP traffic should go outside of the tunnel without the user's
permission. The user may be sending sensitive information out when the
connection
goes down; that information should not be sent to the pre-tunnel network.
* In my view, it would not be enough to change the Tunnelblick icon to show the
change in status; a popup window should be used to force the user's
acknowledgement,
preferably before restoring the original network connection.
Original comment by jkbull...@gmail.com
on 17 Mar 2009 at 10:03
Does version 3.0b12 fix this?
Original comment by jkbull...@gmail.com
on 5 Aug 2009 at 7:40
Original comment by jkbull...@gmail.com
on 30 Aug 2009 at 4:06
Original issue reported on code.google.com by
fduf...@som.ca
on 27 Feb 2009 at 7:19