From 264a11b7be394ff3c10b18ce6d17c938eea95d8c Mon Sep 17 00:00:00 2001 From: Omar Vega Ramos Date: Mon, 30 Nov 2015 20:31:44 -0500 Subject: strongswan-5.3.5-1: updating version --- pcr/strongswan/PKGBUILD | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'pcr/strongswan') diff --git a/pcr/strongswan/PKGBUILD b/pcr/strongswan/PKGBUILD index 4dde9a334..869a86f93 100644 --- a/pcr/strongswan/PKGBUILD +++ b/pcr/strongswan/PKGBUILD @@ -6,12 +6,12 @@ # Contributor (Arch): 458italia # Contributor (Arch): Thermi # Former maintainer (Arch): dkorzhevin -# Maintainer (Arch): Thermi +# Maintainer (Arch): Thermi # Maintainer: Omar Vega Ramos pkgname=strongswan -pkgver=5.3.3 -pkgrel=2 +pkgver=5.3.5 +pkgrel=1 pkgdesc="open source IPsec implementation" url='http://www.strongswan.org' license=("GPL") @@ -21,6 +21,7 @@ conflicts=('openswan') options=(!libtool) backup=( etc/ipsec.conf + etc/swanctl/swanctl.conf etc/strongswan.conf etc/strongswan.d/{charon-logging.conf,charon.conf,pki.conf,pool.conf,scepclient.conf,starter.conf,swanctl.conf} etc/strongswan.d/charon/{aesni.conf,attr-sql.conf,attr.conf,cmac.conf,connmark.conf,\ @@ -37,7 +38,7 @@ source=("https://download.strongswan.org/strongswan-${pkgver}.tar.bz2") # md5 is broken. We use sha256 now. Alternatively, we could check the signature of the file, but that # doesn't yield any more security and just increases the work users initially have to invest. -sha256sums=('39d2e8f572a57a77dda8dd8bdaf2ee47ad3cefeb86bbb840d594aa75f00f33e2') +sha256sums=('2c84b663da652b1ff180a1a73c24a3d7b9fc4b9b8ba6bd07f94a1e33092e6350') # We don't build libipsec because it would get loaded before kernel-netlink and netkey, which # would case processing to be handled in user space. Also, the plugin is experimental. If you need it, -- cgit v1.2.3