Please understand that you do not need to be so concerned about this warning. Many thanks, stay - Describing the results of your experiments is fine, but they won't necessarily apply to other users' configurations. Kindly allow me a few days to do my tests and report back, for the sake of other Tunnelblick users, before I ask for your input, insight or closing this ticket.
Tunnelblick safety trial#
I guess trial and error (and studying is needed) after following the OpenWRT OpenVPN guide here. I will try seeing if setting "Set DNS/WINS" to "Do not set nameserver" option with my untouched script has any effect to this warning (and usability) before trying to see if my router does need the dhcp-option DNS setting for a connection to be established. So I am just launching a fresh installation of Tunnelblick to macOS (Catalina in my case) thus I let it add its own options like -script-security 2 to its startup procedure = I did see this when I read the log after posting here. Please know that I am not using any scripts myself, just an honest-to-God connection to my home's router or NAS, as I have both running as backup (and both show this warning). Hello I appreciate your reply and the time you spent for me, despite being a trivial issue/question for you experienced guys :-D Thank you for replying your insight on this issue, despite not being of critical or major importance. Please see attached (after I removed my sensitive details): But I would expect that configurations override this anyway. I do not know if I need to add somewhere the option -script-security 0 in some default configuration file of the actual Tunnelblick application itself I just launch it on macOS from Applications folder, without messing with hidden configuration files the Preferences window has no mention, nor do I know where to find the "default" client settings. This error is straight-forward in the log output window of Tunnelblick on macOS, highlighted in light-blue colour (when in dark mode): One would think that it follows what is found here: Even if it's not something important or critical, getting this warning prompts to enthusiasts like me to some possible improvement in the whole set up.
Tunnelblick safety code#
I would personally expect at least with value 0 to not show this warning I have no idea if this is a fixed warning in the code of Tunnelblick, regardless of the setting in script-security of each configuration file.
0 kommentar(er)
