[Openvpn-devel] OpenVPN GUI and ntlm Proxy password

2011-03-17 Thread Thomas Glanzmann
Hello Mathias, I would like to use you OpenVPN GUI for Windows to authenticate over an NTLM proxy in Windows and wonder if you're thinking about asking and supplying the password for NTLM-proxy authentication or planing on doing so. The very recent versions of (2.2.x) of OpenVPN support not only b

Re: [Openvpn-devel] OpenVPN GUI and ntlm Proxy password

2011-03-18 Thread Thomas Glanzmann
Hello Heiko, > I fear Mathias is not involved with the OpenVPN GUI since five years or so. > There's a project on SourceForge now where I forked the GUI and try to > improve > it: https://sourceforge.net/projects/openvpn-gui/ I see. Thanks for putting in the effort. > Maybe you want to check

Re: [Openvpn-devel] OpenVPN GUI and ntlm Proxy password

2011-03-18 Thread Thomas Glanzmann
Hello Heiko, > > Fri Mar 18 13:56:53 2011 Error opening 'HTTP Proxy' auth file: > > C:\DOCUME~1\adglth0\LOCALS~1\Temp\openvpn_authfile.: Das System kann die > > angegebene Datei nicht finden. (errno=2) > That's a openvpn error message not one of the GUI. Did you see the dot > (.) at the end of

Re: [Openvpn-devel] OpenVPN GUI and ntlm Proxy password

2011-03-18 Thread Thomas Glanzmann
Hello Heiko, > The incomplete filename is caused by a too small buffer in the GUI. > You must be using a hostname for the proxy and it's somewhere close to > 30 characters long, right? I'll add a bug to the tracker for this > then. In the meantime, could you please try if it works for you using >

Re: [Openvpn-devel] ngx_stream_ssl_preread_module does not seem to extract the server_name when connecting with openconnect

2016-12-15 Thread Thomas Glanzmann
Hello Roman, > You can try logging $ssl_preread_server_name in access_log. thank you. It seems that nginx is not able to extract the server_name from openconnect correctly: 2a01:598:8181:37ef:95e1:682:4c98:449e - [15/Dec/2016:17:45:57 +0100] "" When I connect with a browser: 2a01:598:8181:37ef

Re: [Openvpn-devel] ipv6 netbsd support

2004-01-30 Thread Thomas Glanzmann
Hi, > is there an ipv6-netbsd support planed ? Can you give me detailed > information what must be changed so that I can try to write a patch? I thought I had made a netbsd patch ready, but I can't find it anylonger. But it should be quiet easy looking at the patches which were necessary to enab

Re: [Openvpn-devel] ipv6 netbsd support

2004-02-05 Thread Thomas Glanzmann
Hi together, > If you can give me access to a NetBSD system *including* root access > and kernel sources extracted I should be able to patch and test > openvpn within hours to support IPv6 via tun devices. one of my openvpn/ipv6 users did patch NetBSD tun device itself and maybe openvpn, too. I t

Re: [Openvpn-devel] tap support for freebsd

2004-02-20 Thread Thomas Glanzmann
Hi, I submitted that patch. And will fix it. - If you not already did that. > I have been attempting to use 1.6_beta6 and found that support for the > tap device wasn't working on FreeBSD 5.1. I discovered it worked fine > on FreeBSD 5.1 with 1.6_beta1. Ic. > I believe that it is necessary to

[Openvpn-devel] CVS repository for version 2 - but where?

2004-09-10 Thread Thomas Glanzmann
Hello James, I am unable to find the CVS repository to the upcomming 2.0 version. Honestly, Thomas [ Who want's to implement a compression functionality to compress static things like ipv(6) addresses, prots and maybe parts of tcp header function within one byte using a sim

Re: [Openvpn-devel] minimum cipher in openssl ?

2004-09-13 Thread Thomas Glanzmann
Hi Gary, > I want to run openvpn on WRT54G but the crypto library of openssl is > extremely large for the device. I understand that I can trim away some > ciphers but would like to know what minimum ciphers I have to include. > I want to include only 3 symmetric cipher (blowfish, des and aes) and

Re: [Openvpn-devel] OpenVPN Licensing Issues

2004-09-14 Thread Thomas Glanzmann
Hello James, > I'd like to invite some discussion on this idea, and I'd especially > like feedback from past OpenVPN contributors as to whether this is > something they could agree to. I didn't submit that much code, but of course I would aggree to dual licensing. Honestly, Thomas