Hi there,
I was just wondering if anybody has seen the new Android 4.0 VPN API.
It looks like a promising way to have a native Java OpenVPN solution
on Android.
http://developer.android.com/reference/android/net/VpnService.html
There is a lot of interest in having an Android implementation of
This is nice!
Some questions:
1. Why not enable this automatically if openssl is sufficient version?
There is no point in not using this if available.
2. I would have liked to see this in negotiation as well, so server will
use EC if supported by the client and fallback if not... This way
sorry about the noise, folks; this was my second git patch attempt :)
cheers,
JJK
Jan Just Keijser wrote:
> Made some options connection-entry specific:
> fragment
> mssfix
> tun-mtu
> tun-mtu-extra
> link-mtu
> mtu_discover_type
> explicit-exit-notification
> in order to support
Made some options connection-entry specific:
fragment
mssfix
tun-mtu
tun-mtu-extra
link-mtu
mtu_discover_type
explicit-exit-notification
in order to support stuff like
remote host
proto udp
fragment
explicit-exit-notification 3
remote host
proto tcp
Signed-off-by:
In commit bee92b479414d12035b0422f81ac5fcfe14fa645 the gc_malloc() was hardened
to always require a gc_arena object for garbage collection. Some places in the
code expected the old behaviour of a normal malloc() in these cases, that is a
memory allocation without garbage collection.
This old
Hi,
I'm forwarding this "as-is", as I do not have enough understanding of
autoconf to say whether this is necessary, or "the right fix" - but
anyway, I've been told that this is needed to make our configure
behave on MacOS 10.7.
gert
--
USENET is *not* the non-clickable part of WWW!
Thank you, that patch had more impact than I thought it would. I'm sorry about
the inconvenience, it's a bug I'm looking into at the moment.
David, could you revert the patch please, so I have a little more time to
refactor there? I'm looking into the best way to refactor that function with a
