Package Details: wg_tool 9.2.4-1

Git Clone URL: https://aur.archlinux.org/wg_tool.git (read-only, click to copy)
Package Base: wg_tool
Description: Manage wireguard VPN configurations (servers and users).
Upstream URL: https://github.com/gene-git/wg_tool
Keywords: vpn wireguard
Licenses: GPL-2.0-or-later
Submitter: GeneArch
Maintainer: GeneArch
Last Packager: GeneArch
Votes: 3
Popularity: 0.000001
First Submitted: 2022-10-26 15:19 (UTC)
Last Updated: 2026-01-06 16:50 (UTC)

Pinned Comments

GeneArch commented on 2026-06-14 20:55 (UTC)

As both the packager and upstream author I'd like to encourage all users to activate "git source verification" if not already done. Please see comment in the PKGBUILD file. The recent supply chain issues highlight the importance of validating source code.

All git tags are signed and going forward, every commit will also be signed.

The public signing key is available in a few places, but I recommend getting it either via WKD or directly from the website of the key's email domain. These are sound ways to do this. For additional information please see:

https://sapience.com/tech/blog/git-keys

To get the key via WKD:

gpg --auto-key-locate nodefault,wkd --locate-external-keys arch@sapience.com

Latest Comments

1 2 3 Next › Last »

GeneArch commented on 2026-06-14 20:55 (UTC)

As both the packager and upstream author I'd like to encourage all users to activate "git source verification" if not already done. Please see comment in the PKGBUILD file. The recent supply chain issues highlight the importance of validating source code.

All git tags are signed and going forward, every commit will also be signed.

The public signing key is available in a few places, but I recommend getting it either via WKD or directly from the website of the key's email domain. These are sound ways to do this. For additional information please see:

https://sapience.com/tech/blog/git-keys

To get the key via WKD:

gpg --auto-key-locate nodefault,wkd --locate-external-keys arch@sapience.com

GeneArch commented on 2026-01-12 14:20 (UTC)

great thanks for confirming

simona commented on 2026-01-12 14:18 (UTC)

solved. tnx.

GeneArch commented on 2026-01-12 12:01 (UTC)

Thanks for letting me know @simona - I responded to your comment in py-cidr section. Hopefully that sorts it out for you

simona commented on 2026-01-12 11:46 (UTC)

can't compile py-cidr

GeneArch commented on 2025-01-03 10:30 (UTC)

Note on getting the git signing public key. Any of the following:

1) Get fresh copy of the package (on this page Package Actions Download Snapshot) Unpack tar file and the key will be in keys/pgp:

gpg --import < keys/pgp/*.asc

2) Available on github (same account as the package source): https://github.com/gene-git/blog/tree/master/git-keys

3) From authors website : https://www.sapience.com/tech

4) via WKD curl $(gpg-wks-client --print-wkd-url arch@sapience.com) | gpg --import

GeneArch commented on 2025-01-01 21:10 (UTC)

Terrific!

Let me know if anything else isn't working for you.

simona commented on 2025-01-01 21:08 (UTC)

solved with
curl $(gpg-wks-client --print-wkd-url arch@sapience.com) | gpg --import
thx.

GeneArch commented on 2025-01-01 20:43 (UTC)

Thanks - Expanding a bit on my comment in

https://aur.archlinux.org/packages/ssl-mgr#comment-1004774

the key is not uploaded to any pgp key servers as key servers have been replaced by WKD (web key directory).

There are 3 ways to get the key:

1) The simplest way is simply to import the key directly from the file provided with the package. gpg --import < keys/pgp/*.asc

2) It is also available from the author's website (www.sapience.com/tech). Download and import the key.

3) Using Web Key Directory ( WKD ).

Note that gpg is known to have trouble with some higher security website likely from a bug in gnutls library it uses for TLS negotiation with websites.

You can try it : gpg --auto-key-locate wkd --locate-key arch@sapience.com

If gpg has trouble with WKD then you can instead use:

curl $(gpg-wks-client --print-wkd-url arch@sapience.com) | gpg --import

where gpg-wks-client will simply print the url of the WKD entry for the provided email. Curl fetches it and gpg then imports it.

Let me know if you have any further trouble getting the public key into your keyring.

simona commented on 2025-01-01 20:10 (UTC)

:: PGP keys need importing:
-> 7CCA1BA66669F3273DB52678E5B81343AB9809E1, required by: ssl-mgr kea_config process-mem lockmgr python-pynotify wg_tool
:: Importing keys with gpg...
gpg: ricezione dal keyserver fallita: Dati assenti