Hi guys,
I'm using the latest openvpn from GIT on OpenSUSE 11.4 and am
experiencing a problem with IPv6 payload setup. It works but openvpn
seems to be somewhat confused when setting up the v6 route.
Here is the start-up sequence, that works fine:
16:27:27 OpenVPN 2.x-master x86_64-suse-linu
Hi,
On Wed, Nov 23, 2011 at 04:56:22PM +1300, Michal Ludvig wrote:
> I'm using the latest openvpn from GIT on OpenSUSE 11.4 and am
> experiencing a problem with IPv6 payload setup. It works but openvpn
> seems to be somewhat confused when setting up the v6 route.
There's two interesting things
Hi,
bugfixing the tap driver is nice and well, but I think we MUST bump the
driver version as well, and we SHOULD have a check in tun.c to refuse
operation if the known-buggy version (9.8) is detected.
Patches below.
gert
--
USENET is *not* the non-clickable part of WWW!
Hi,
On Fri, Nov 18, 2011 at 01:39:50PM +0100, David Sommerseth wrote:
> Without this patch, the default path used by OpenVPN is hard coded
> to C:\WINDOWS. As users might install Windows in a different directory,
> this approach will cause OpenVPN to malfunction in some configurations.
>
> OpenV
As many of you know, my company, Fox-IT, has been hired to help the Dutch
government prepare OpenVPN for government evaluation. Part of that process was
the addition of more API documentation, and the refactoring of the backend
crypto system. We've tried to return all of the (useful) patches to
The UTF-8 support that came with commit 2627335 does allow international
usernames and passwords. This patch introduces UTF-8 support for X.509 DNs.
Additionally, instead of using the legacy openssl format, DNs are now
displayed in RFC 2253 format; "/C=ru/L=\xD0\x9C\xD0\xBE\xD1\x81\xD0\xBA\xD0
\xB2
This patch makes openvpn read unicode from the console and convert the input
to UTF-8. And then display UTF-8 output to the console correctly.
Signed-off-by: Heiko Hund
---
configure.ac |1 +
openvpn.c|4
win32.c |8 +++-
3 files changed, 12 insertions(+), 1 deletio
As this is inserted into environment, what happens if locale is not
unicode enabled?
I think this may break some configurations.
On Wed, Nov 23, 2011 at 4:14 PM, Heiko Hund wrote:
> The UTF-8 support that came with commit 2627335 does allow international
> usernames and passwords. This patch intr
OpenVPN output is not always a console.
I am not sure this patch is valid.
On Wed, Nov 23, 2011 at 4:15 PM, Heiko Hund wrote:
> This patch makes openvpn read unicode from the console and convert the input
> to UTF-8. And then display UTF-8 output to the console correctly.
>
> Signed-off-by: Heiko
Hi,
On Wed, Nov 23, 2011 at 11:23:44AM +0100, Gert Doering wrote:
> bugfixing the tap driver is nice and well, but I think we MUST bump the
> driver version as well, and we SHOULD have a check in tun.c to refuse
> operation if the known-buggy version (9.8) is detected.
Samuli built an installer w
On Wednesday 23 November 2011 14:55:57 Alon Bar-Lev wrote:
> OpenVPN output is not always a console.
What output are you concerned about? Log file is fine, as much as management
interface.
Regards
Heiko
--
Heiko Hund | Software Engineer | Phone +49-721-25516-237 | Fax -200
Astaro a Sophos Compa
On Wednesday 23 November 2011 14:53:06 Alon Bar-Lev wrote:
> As this is inserted into environment, what happens if locale is not
> unicode enabled?
Then the script will receive funny looking strings depending on your locale's
code page. However, this is nothing that's being introduced with this p
On Wed, Nov 23, 2011 at 5:02 PM, Heiko Hund wrote:
> On Wednesday 23 November 2011 14:55:57 Alon Bar-Lev wrote:
>> OpenVPN output is not always a console.
>
> What output are you concerned about? Log file is fine, as much as management
> interface.
>
> Regards
> Heiko
Pipes when run as service.
On Wed, Nov 23, 2011 at 5:14 PM, Heiko Hund wrote:
> On Wednesday 23 November 2011 14:53:06 Alon Bar-Lev wrote:
>> As this is inserted into environment, what happens if locale is not
>> unicode enabled?
>
> Then the script will receive funny looking strings depending on your locale's
> code page.
On Wednesday 23 November 2011 15:43:04 Alon Bar-Lev wrote:
> Pipes when run as service.
Good one! I'll post an updated patch.
Regards
Heiko
--
Heiko Hund | Software Engineer | Phone +49-721-25516-237 | Fax -200
Astaro a Sophos Company | Amalienbadstr. 41 Bau 52 | 76227 Karlsruhe | Germany
Commer
This patch makes openvpn read unicode from the console and convert the input
to UTF-8. And then display UTF-8 output to the console correctly.
Signed-off-by: Heiko Hund
---
configure.ac |1 +
openvpn.c|4
win32.c | 14 +-
3 files changed, 18 insertions(+), 1 d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/11/11 13:39, David Sommerseth wrote:
> Without this patch, the default path used by OpenVPN is hard coded to
> C:\WINDOWS. As users might install Windows in a different directory,
> this approach will cause OpenVPN to malfunction in some
> co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/11/11 11:23, Gert Doering wrote:
> Hi,
>
> bugfixing the tap driver is nice and well, but I think we MUST bump
> the driver version as well, and we SHOULD have a check in tun.c to
> refuse operation if the known-buggy version (9.8) is detected
18 matches
Mail list logo
