Search Criteria
Package Details: openswan 2.6.52.3-1
Git Clone URL: | https://aur.archlinux.org/openswan.git (read-only, click to copy) |
---|---|
Package Base: | openswan |
Description: | Open Source implementation of IPsec for Linux |
Upstream URL: | https://www.openswan.org |
Licenses: | |
Conflicts: | |
Submitter: | Allan |
Maintainer: | severach |
Last Packager: | severach |
Votes: | 143 |
Popularity: | 0.000005 |
First Submitted: | 2009-11-07 14:39 |
Last Updated: | 2020-12-20 00:35 |
Dependencies (6)
- gmp (gmp-hg, scipoptsuite, scipoptsuite-bin)
- iproute2 (iproute2-git, iproute-mptcp, iproute2-selinux)
- perl (perl-git)
- bison (byacc-bison, bison-git) (make)
- flex (flex-git) (make)
- python2 (optional)
Required by (4)
- hash-slinger (optional)
- hash-slinger-git (optional)
- l2tp-ipsec-vpn
- l2tp-ipsec-vpn-daemon
Latest Comments
1 2 3 4 5 6 ... Next › Last »
xexaxo commented on 2020-12-01 05:04
Please consider pulling my fix on the next update. Upstream has merged it, although it not in any release yet.
Edit: fix has been included in 2.6.52.3
xexaxo commented on 2020-09-28 16:43
You may want to include https://github.com/xelerance/Openswan/pull/447. Otherwise "self-proposal" errors may occur as seen in https://bbs.archlinux.org/viewtopic.php?id=253434.
buzz commented on 2020-07-09 17:59
Could you support
aarch64
?I successfully compiled for this architecture by adding
aarch64
toarch
inPKGINFO
.Thank you
greenlean commented on 2020-05-21 09:40
The package does not build on gcc 10-1. A workaround is to downgrade to gcc 9.2 and then build it.
$ yay -S downgrade
# downgrade gcc gcc-libs
There are also issues with xmlto, is better to remove it:
# pacman -R xmlto
lineage commented on 2020-01-30 19:24
One of the makefiles tries to remove a real system file during packaging. Non-root builds where a version is already installed barf. root builds would silently remove the file. This will fix it
amdg commented on 2020-01-21 09:26
This package is missing the following build dependencies:
severach commented on 2019-08-10 01:04
The "normal" diff format isn't very good. It won't apply if everything isn't exact. The context and unified will apply. Unified are the easiest to read.
Subtracting 1 isn't enough. That may shut the compiler up but it will earn us a CVE. strncpy() does not guarantee a nul end of string. The referenced patch has a decent way to guarantee a nul but I like my way better because it also guarantees no random text can appear after the nul.
The real answer is to write a custom strncpy() that has all the behavior we want, guaranteed nul and all nul to end of buffer.
mickybart commented on 2019-08-09 19:26
@stramaz
I have the same issue when I copy/paste it from my comment.
Here is base64 version to avoid that as I don't know how to share it in a proper way.
the sha512sum is d4b5c8418cb623fc720d9e401cbbaf1668c172af8b5c658f95efadcce165840fd35c3f4dbb62925de73c1c3e212093e2cb427424b0db4e92ff96eb1c83cd84c4
stramaz commented on 2019-08-09 14:35
Unfortunately the patch of @mickybart doesn't work for me...:
mickybart commented on 2019-07-17 14:50
That need to be fixed upstream but the patch should look something like that to fix the compilation:
You can add the patch in PKGBUILD/prepare():
It works for me but that need to be discussed with upstream team.
EDIT: similar code issue: https://github.com/intel/openlldp/issues/23