Jump to content
Company Name
  • 0
Support

TorGuard Client v0.3.68

Rate this question

Question

*Release torguard-v0.3.68, 2017-09-05*

*====================================*
 
- All platforms: New TorGuard Logo
 
- All platforms: Add Taiwan (TWN) flag
 
- All platforms: Bug fix
 
   The option "Enable disabled interfaces before connecting = Yes"
    was not savable.
 
- All platforms: Bug fix
 
   When connecting with OpenConnect, there was a small random probability
    that the user experiments a bug resulting in an incorrect warning message:
    "Could not connect to the VPN management socket.
    Please check your firewall settings!"
    The bug is fixed in this patch.
 
- Windows and MacOSX: "Close to tray" is now false by default.
 
   The option "Close to tray" changes the natural behaviour of the "close"
    button, minimizing TorGuard to tray. The user must be aware of this
    in order to recover TorGuard instance when it is minimized.
 
- Windows: Add "Block outside DNS" option to OpenConnect
 
   Original OpenConnect can not block outside DNS. In this version the
    outside DNS option is managed by TorGuard itself (when OpenConnect is used)
 
- Windows: Interfaces list behaviour changed
 
   In the "Select interfaces" dialog the user can see and select
    the enabled interfaces, while the disabled ones are not shown.
    But if an interface was disabled by TorGuard, now it appears
    in the list.
 
- Windows: Check if the disabled interfaces are enabled again before connecting
 
   When the user wants to enable the previously disabled interfaces,
    TorGuard will check that they are indeed enabled before trying to connect.
    This could fix issues in the cases when enabling the interfaces
    took some seconds.
 
- Windows: vpnc-script.js will use the adapter index instead of the adapter friendly-name
 
   Some issues can arise if the enconding of the operative system is
    not understood by the netsh command. In particular the friendly names
    of the adapters can be shown as "??????". Using the index is a more
    stable way to get the right adapter inside the vpnc-script.js.
 
- Windows: Bug fix - two libraries were left in the system after TorGuard unistallation
 
- Windows: Bug fix - connecting to some servers through the tray icon was not working
 
   The connect option from the tray icon was not working if a server in a submenu
    was selected. The bug is fixed in this version
 
- Linux: Bug fix
 
   Handling the Ctrl-C (SIGTERM) signal was not working properly,
    due to wrong values of some environment variables while managing
    user privileges.
 
- Linux Arch: Bug fix
 
   When TorGuard was installed, OpenConnect executable had not the right permissions.
    The bug is fixed in this version.
 

Share this post


Link to post
Share on other sites

9 answers to this question

Recommended Posts

  • 0

Torguard Client notified me there was an update available. Going to the Torguard website to confirm, it said 0.3.68 was available for Mac (I'm running 0.3.66). Downloaded the 0.3.68 update from the website and it installed 0.3.67 instead.

 

Downloaded the update from the TorGuard client and it also downloaded 0.3.67.

 

What's up with this?

Share this post


Link to post
Share on other sites
  • 0

Torguard Client notified me there was an update available. Going to the Torguard website to confirm, it said 0.3.68 was available for Mac (I'm running 0.3.66). Downloaded the 0.3.68 update from the website and it installed 0.3.67 instead.

 

Downloaded the update from the TorGuard client and it also downloaded 0.3.67.

 

What's up with this?

 

 

Apologies for this, we noticed a couple of bugs and pulled the new update for a moment until we released and fixed them in another new release here

 

Regards

Share this post


Link to post
Share on other sites
  • 0

I solved the question myself. I had to register DNS. Now everything works.

27029f.jpg

 

Hi Solo - was the internal based DNS left on your Adapter ?

 

Regards

Share this post


Link to post
Share on other sites
  • 0

Apologies for this, we noticed a couple of bugs and pulled the new update for a moment until we released and fixed them in another new release here

 

Regards

 

Thanks! Running 3.0.69 now.

Share this post


Link to post
Share on other sites

×