On 14/04/14 21:34, Gert Doering wrote:
> Hi,
>
> On Sun, Apr 13, 2014 at 05:26:13PM +0200, Gert Doering wrote:
>> OpenVPN does not currently report the version of the SSL library it is
>> using - which I'm not sure whether it's by design or just because nobody
>> ever added it. Anyway, right now
Hi,
On Sun, Apr 13, 2014 at 05:26:13PM +0200, Gert Doering wrote:
> OpenVPN does not currently report the version of the SSL library it is
> using - which I'm not sure whether it's by design or just because nobody
> ever added it. Anyway, right now I think we need it, to help future
> cases.
OK,
Hi,
On Mon, Apr 14, 2014 at 09:12:05AM +0200, Jan Just Keijser wrote:
> >- how do I get the library version for PolarSSL?
> void version_get_string_full( char *string )
I really wonder what they smoked when designing this API...
/**
* Get the full version string ("PolarSSL x.y.z").
*
* \param
Hi,
On 14-04-14 09:12, Jan Just Keijser wrote:
> Gert Doering wrote:
>> - if we report it, do we want to report it always (as IV_VER) or only
>> if --push-peer-info is set?
>>
> we're reporting the openvpn version info anyway, so adding the SSL lib
> version would not change much; if it is o
On Mon, Apr 14, 2014 at 12:19 AM, Jan Just Keijser wrote:
> I'd vote against enabling TARGET_ANDROID by default
This would not be my first choice either, but it would allow non-root
processes to set up a fully functional VPN connection on Linux hosts
without a special build.
If I'm going to have
On Mon, Apr 14, 2014 at 11:42:23AM +0200, Gert Doering wrote:
> Hi,
>
> On Mon, Apr 14, 2014 at 11:29:28AM +0200, Alberto Gonzalez Iniesta wrote:
> > There're already packages for PolarSSL in Debian (and thus, in Ubuntu).
> > So I don't think there's need to maintain different ones.
>
> What's De
Hi,
On Mon, Apr 14, 2014 at 11:29:28AM +0200, Alberto Gonzalez Iniesta wrote:
> There're already packages for PolarSSL in Debian (and thus, in Ubuntu).
> So I don't think there's need to maintain different ones.
What's Debian's stance on PolarSSL 1.2.x vs. 1.3.x? This is something
that had me wo
On Mon, Apr 14, 2014 at 11:48:46AM +0300, Samuli Seppänen wrote:
>
> > Hi,
> >
> > On Mon, Apr 14, 2014 at 11:13:24AM +0300, Samuli Seppänen wrote:
> >> Currently all of the binary builds we provide[*] are linked to OpenSSL.
> >> Would having both OpenSSL and PolarSSL builds make sense (e.g. start
On Mon, Apr 14, 2014 at 11:56:43AM +0300, Samuli Seppänen wrote:
>
> > Hi,
> >
> > On 04/14/2014 10:28 AM, Gert Doering wrote:
> >> On Mon, Apr 14, 2014 at 11:13:24AM +0300, Samuli Seppänen wrote:
> >>> Currently all of the binary builds we provide[*] are linked to OpenSSL.
> >>> Would having both
- Opprinnelig melding -
> Fra: "Gert Doering"
> Til: openvpn-devel@lists.sourceforge.net
> Sendt: 13. april 2014 17:26:13
> Emne: [Openvpn-devel] RFD: ssl library version numbers
>
> Hi,
>
> OpenVPN does not currently report the version of the SSL library it is
> using - which I'm not s
> Hi,
>
> On 04/14/2014 10:28 AM, Gert Doering wrote:
>> On Mon, Apr 14, 2014 at 11:13:24AM +0300, Samuli Seppänen wrote:
>>> Currently all of the binary builds we provide[*] are linked to OpenSSL.
>>> Would having both OpenSSL and PolarSSL builds make sense (e.g. starting
>>> with 2.4)?
>> I thin
> Hi,
>
> On Mon, Apr 14, 2014 at 11:13:24AM +0300, Samuli Seppänen wrote:
>> Currently all of the binary builds we provide[*] are linked to OpenSSL.
>> Would having both OpenSSL and PolarSSL builds make sense (e.g. starting
>> with 2.4)?
> I think it would be a nice option. We could even start w
Hi,
On 04/14/2014 10:28 AM, Gert Doering wrote:
> On Mon, Apr 14, 2014 at 11:13:24AM +0300, Samuli Seppänen wrote:
>> Currently all of the binary builds we provide[*] are linked to OpenSSL.
>> Would having both OpenSSL and PolarSSL builds make sense (e.g. starting
>> with 2.4)?
>
> I think it wou
Hi,
On Mon, Apr 14, 2014 at 11:13:24AM +0300, Samuli Seppänen wrote:
> Currently all of the binary builds we provide[*] are linked to OpenSSL.
> Would having both OpenSSL and PolarSSL builds make sense (e.g. starting
> with 2.4)?
I think it would be a nice option. We could even start with 2.3.4
On Sunday 13 April 2014 17:24:02 Piotr Zborowski wrote:
> res/openvpn-gui-res-pl.rc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks. I've applied it to the repo, but have not pushed it, yet. Will be
contained in the next openvpn installer.
Heiko
Hi,
Currently all of the binary builds we provide[*] are linked to OpenSSL.
Would having both OpenSSL and PolarSSL builds make sense (e.g. starting
with 2.4)?
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
[*] For Windows, Debian, Ubuntu
Hi
Kevin Cernekee wrote:
On Sun, Apr 13, 2014 at 8:19 AM, Arne Schwabe wrote:
You could look at the TARGET_ANDROID. That uses the management interface and
fds over unix socket to achieve something similar.
Do you think it would be feasible to enable TARGET_ANDROID by default
in the L
Hi Gert,
Gert Doering wrote:
Hi,
OpenVPN does not currently report the version of the SSL library it is
using - which I'm not sure whether it's by design or just because nobody
ever added it. Anyway, right now I think we need it, to help future
cases.
There are a few questions that go along w
18 matches
Mail list logo
