[My apologies for any formatting issues; my employer likes Outlook.]
James Yonan wrote:
> On 18/06/2013 01:23, Joachim Schipper wrote:
> > Joachim Schipper wrote [I'm continuing my own message here]:
> >> Kenny Root wrote:
> >>> I wrote a patch to add AEAD ciph
>From James Yonan :
> This is the TLS versioning patch as discussed in last Thursday's IRC
> meeting.
>
> It combines these two patches:
>
> https://github.com/jamesyonan/openvpn/commit/03a5599202bdc3ba07983dc4ef
> dae387fb8fb436
>
> https://github.com/jamesyonan/openvpn/commit/d23005413b0e0f28a
>From James Yonan :
> On 18/06/2013 01:41, Joachim Schipper wrote:
> > From James Yonan :
> >> On 14/06/2013 02:47, Joachim Schipper wrote:
> >>> >From James Yonan :
> >>>> TLS Protocol
> >>>>
> >>&
From: James Yonan :
> On 14/06/2013 02:47, Joachim Schipper wrote:
> >>From James Yonan :
> >> TLS Protocol
> >>
> >>
> >> Since day 1, OpenVPN has used TLS 1.0 as a control channel and key
> >> exchange mechanism. But
Joachim Schipper wrote [I'm continuing my own message here]:
> > -Original Message-
> > From: Kenny Root [mailto:ke...@the-b.org]
> > Sent: dinsdag 4 juni 2013 2:15
> > To: openvpn-devel@lists.sourceforge.net
> > Subject: [Openvpn-devel] Adding support
> -Original Message-
> From: Kenny Root [mailto:ke...@the-b.org]
> Sent: dinsdag 4 juni 2013 2:15
> To: openvpn-devel@lists.sourceforge.net
> Subject: [Openvpn-devel] Adding support for AEAD cipher modes
> (AES-GCM, et al.)
>
> I wrote a patch to add AEAD cipher modes to OpenVPN. This is
>From James Yonan :
> TLS Protocol
>
>
> Since day 1, OpenVPN has used TLS 1.0 as a control channel and key
> exchange mechanism. But now we have TLS 1.1 and 1.2, each of which
> addresses significant shortcomings in its predecessor. Fortunately,
> SSL/TLS already includes dynamic ve
> Hi,
>
> our setup needs openvpn UDP/TLS tunnels with dynamic client IP addresses, so
> I implemented a fix for the bug #49 that has been open for over two years.
>
> The patch is for version 2.2.2 as I had trouble compiling the 2.3.x tarball
> from openvpn.net. As the solution is rather simple
A very simple client for --management-external-key based on an on-disk keyfile.
Useful for testing.
Signed-off-by: Joachim Schipper
---
.gitignore |1 +
contrib/management-external-key-client/Makefile| 12 +
contrib/management-external-key
Signed-off-by: Joachim Schipper
---
configure.ac |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index d3d974d..2f780b7 100644
--- a/configure.ac
+++ b/configure.ac
@@ -934,7 +934,7 @@ if test "${enable_ssl}" = "yes";
Signed-off-by: Joachim Schipper
---
doc/management-notes.txt |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/management-notes.txt b/doc/management-notes.txt
index 79e71ad..ef39b85 100644
--- a/doc/management-notes.txt
+++ b/doc/management-notes.txt
@@ -774,7 +774,7
When specifying --tls-client --cert ... without a --key (or --pkcs11) option,
OpenVPN should complain: "You must define private key file (--key)...". Ensure
that this works even when compiling with MANAGMENT_EXTERNAL_KEY.
Signed-off-by: Joachim Schipper
---
src/openvpn/options.c |
Yes, that seems to be correct. Sorry!
Joachim
-Original Message-
From: David Sommerseth [mailto:openvpn.l...@topphemmelig.net]
Sent: dinsdag 20 november 2012 10:19
To: Joachim Schipper
Cc: openvpn-devel@lists.sourceforge.net; Adriaan de Jong
Subject: Re: [Openvpn-devel
13 matches
Mail list logo
