Package Details: strongswan 5.5.2-1

Git Clone URL: https://aur.archlinux.org/strongswan.git (read-only)
Package Base: strongswan
Description: open source IPsec implementation
Upstream URL: http://www.strongswan.org
Keywords: IPsec strongswan
Licenses: GPL
Conflicts: openswan
Submitter: jayray
Maintainer: Thermi
Last Packager: Thermi
Votes: 109
Popularity: 5.742979
First Submitted: 2007-04-22 16:41
Last Updated: 2017-03-28 19:56

Pinned Comments

Thermi commented on 2017-01-08 15:20

@ltcmdrdata
Please only paste output with LANG=C.
The error appears because you don't have the necessary GPG key to authenticate the signature in your GPG keyring. The necessary GPG key's ID is specified in the PKGBUILD. It is "948F158A4E76A27BF3D07532DF42C170B34DBA77" (Andreas Steffen's public key). You need to download it from a GPG keyserver and import it in your gpg keyring. Use `gpg --recv-keys 948F158A4E76A27BF3D07532DF42C170B34DBA77` (assuming your version of gpg works, you have a keyserver defined and your gpg version can interact with gpg keyservers[1].

NO, YOU DO NOT AND *MUST NOT* IMPORT THE KEY INTO YOUR PACMAN KEYRING!

[1] https://bugs.archlinux.org/task/52354

Latest Comments

jabbas commented on 2017-04-15 11:57

Tested my patched PKGCONFIG on armv7 - works.

jabbas commented on 2017-04-11 19:06

I've created a version which compiles on different arch's than x86 and x86_64.

https://gist.github.com/jabbas/28e6c37e38032c0fc45e4c3b0be936c3

You can't do --enable-aesni on those, since it needs SSE3.

Tested on Odroid C2 but should work on rPi (and other ARM's) as well.

GitHub repository with changes: https://github.com/jabbas/archlinux-strongswan

amuri-de commented on 2017-04-03 04:28

if you get error like this:
==> Verifying source file signatures with gpg...
strongswan-5.5.2.tar.bz2 ... FAILED (unknown public key DF42C170B34DBA77)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build strongswan.

you can try to add pgp key with:
gpg --keyserver pool.sks-keyservers.net --recv-keys DF42C170B34DBA77

I hope it will fix the problem

Thermi commented on 2017-02-18 17:59

@tapir

This is not the place to discuss this or ask help regarding the software. Please do this on the forums of Archlinux or the bugtracker of the project. Preferably the forums, because this seems really trivial.

tapir commented on 2017-02-18 17:57

I have my client certificates in the user home directory but when I try to connect to my VPN server, networkmanager complains that "Permission denied" for the certifiacte files. I've made them even 0777 just to make sure. Still the same problem. Any ideas?

Thermi commented on 2017-02-12 20:16

Of which all but one are either pulled in by something in the base group.
Only the sqlite dependency is because of sqlite support, but that's something that the previous maintainer did and not something I want to remove, because it could existing installations.

ilpianista commented on 2017-02-12 10:55

Well we already have 17 dependencies... however I don't really care since I already have to edit the PKGBUILD for NM support.

Instead, I think that you could suggest to use the new option "--with-nm-ca-dir=/etc/ssl/certs" when enabling NM support. Thank you

Thermi commented on 2017-02-11 19:38

I reject this request, because compiling with unbound support requires libunbound at build time.

ilpianista commented on 2017-02-11 19:00

Please consider to add unbound support.

Thermi commented on 2017-01-08 15:20

@ltcmdrdata
Please only paste output with LANG=C.
The error appears because you don't have the necessary GPG key to authenticate the signature in your GPG keyring. The necessary GPG key's ID is specified in the PKGBUILD. It is "948F158A4E76A27BF3D07532DF42C170B34DBA77" (Andreas Steffen's public key). You need to download it from a GPG keyserver and import it in your gpg keyring. Use `gpg --recv-keys 948F158A4E76A27BF3D07532DF42C170B34DBA77` (assuming your version of gpg works, you have a keyserver defined and your gpg version can interact with gpg keyservers[1].

NO, YOU DO NOT AND *MUST NOT* IMPORT THE KEY INTO YOUR PACMAN KEYRING!

[1] https://bugs.archlinux.org/task/52354

All comments