public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. d1b0815ff7a5bf14cd65a6f9d61edb4916d288dc
Date: Tue, 22 Apr 2014 17:47:09 +0200	[thread overview]
Message-ID: <20140422154710.343FC20AC4@argus.ipfire.org> (raw)

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

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, master has been updated
       via  d1b0815ff7a5bf14cd65a6f9d61edb4916d288dc (commit)
      from  2ed8330ee5ea5164b580f673cc2e608abcb9384d (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d1b0815ff7a5bf14cd65a6f9d61edb4916d288dc
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Apr 22 17:46:32 2014 +0200

    strongswan: Enable XAUTH noauth plugin.
    
    See #10468.

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/common/strongswan | 3 +++
 lfs/strongswan                     | 1 +
 2 files changed, 4 insertions(+)

Difference in files:
diff --git a/config/rootfiles/common/strongswan b/config/rootfiles/common/strongswan
index 05ecef0..6d7bb0d 100644
--- a/config/rootfiles/common/strongswan
+++ b/config/rootfiles/common/strongswan
@@ -58,6 +58,7 @@ etc/strongswan.d/charon/updown.conf
 etc/strongswan.d/charon/x509.conf
 etc/strongswan.d/charon/xauth-eap.conf
 etc/strongswan.d/charon/xauth-generic.conf
+etc/strongswan.d/charon/xauth-noauth.conf
 etc/strongswan.d/charon/xcbc.conf
 etc/strongswan.d/starter.conf
 etc/strongswan.d/tools.conf
@@ -134,6 +135,7 @@ usr/lib/ipsec/plugins/libstrongswan-updown.so
 usr/lib/ipsec/plugins/libstrongswan-x509.so
 usr/lib/ipsec/plugins/libstrongswan-xauth-eap.so
 usr/lib/ipsec/plugins/libstrongswan-xauth-generic.so
+usr/lib/ipsec/plugins/libstrongswan-xauth-noauth.so
 usr/lib/ipsec/plugins/libstrongswan-xcbc.so
 #usr/libexec/ipsec
 usr/libexec/ipsec/_copyright
@@ -212,6 +214,7 @@ usr/sbin/ipsec
 #usr/share/strongswan/templates/config/plugins/x509.conf
 #usr/share/strongswan/templates/config/plugins/xauth-eap.conf
 #usr/share/strongswan/templates/config/plugins/xauth-generic.conf
+#usr/share/strongswan/templates/config/plugins/xauth-noauth.conf
 #usr/share/strongswan/templates/config/plugins/xcbc.conf
 #usr/share/strongswan/templates/config/strongswan.conf
 #usr/share/strongswan/templates/config/strongswan.d
diff --git a/lfs/strongswan b/lfs/strongswan
index f9f6e78..ba49210 100644
--- a/lfs/strongswan
+++ b/lfs/strongswan
@@ -89,6 +89,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
 		--enable-farp \
 		--enable-openssl \
 		--enable-xauth-eap \
+		--enable-xauth-noauth \
 		--enable-eap-radius \
 		--enable-eap-tls \
 		--enable-eap-ttls \


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2014-04-22 15:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140422154710.343FC20AC4@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@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