public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Update to version 2.3.11.
Date: Mon, 27 Jun 2016 17:58:03 +0200	[thread overview]
Message-ID: <33B65FF2-DAF0-4D00-8705-BD61B72F96FC@ipfire.org> (raw)
In-Reply-To: <1467042197-28617-1-git-send-email-erik.kapfer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2490 bytes --]

Hi all,
this update includes improvements but also some security related fixes. Changelog can be overviewed in here --> https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn23#OpenVPN2.3.11 . Please keep in mind that the current OpenVPN version on IPFire is 2.3.7 , this update includes OpenVPN version 2.3.11 .
The "--enable-password-save" option has been changed to "enable_password_save=yes" which is also included in this patch. Have made some tests with the via-env method like described in here --> http://forum.ipfire.org/viewtopic.php?t=5995#p41498 which seems to work without problems.

Sources has been uploaded.

Greetings,

Erik


Am 27.06.2016 um 17:43 schrieb Erik Kapfer <erik.kapfer(a)ipfire.org>:

> The enable-password-save option has been removed with enable_password_save=yes .
> 
> Signed-off-by: Erik Kapfer <erik.kapfer(a)ipfire.org>
> ---
> lfs/openvpn | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/lfs/openvpn b/lfs/openvpn
> index 96e37f7..10934fc 100644
> --- a/lfs/openvpn
> +++ b/lfs/openvpn
> @@ -1,7 +1,7 @@
> ###############################################################################
> #                                                                             #
> # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2015  IPFire Team  <info(a)ipfire.org>                          #
> +# Copyright (C) 2016  IPFire Team  <info(a)ipfire.org>                          #
> #                                                                             #
> # This program is free software: you can redistribute it and/or modify        #
> # it under the terms of the GNU General Public License as published by        #
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 2.3.7
> +VER        = 2.3.11
> 
> THISAPP    = openvpn-$(VER)
> DL_FILE    = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = 5b819f7cd0b875f55f20a947224967aa
> +$(DL_FILE)_MD5 = fe17a25235d65e60af8986c6c78c4650
> 
> install : $(TARGET)
> 
> @@ -74,7 +74,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> 		--prefix=/usr \
> 		--sysconfdir=/var/ipfire/ovpn \
> 		--enable-iproute2 \
> -		--enable-password-save \
> +		enable_password_save=yes \
> 		--enable-plugins \
> 		--enable-plugin-auth-pam \
> 		--enable-plugin-down-root
> --
> 2.7.4
> 


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

      reply	other threads:[~2016-06-27 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 15:43 Erik Kapfer
2016-06-27 15:58 ` ummeegge [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=33B65FF2-DAF0-4D00-8705-BD61B72F96FC@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox