Search Criteria
Package Details: yubico-piv-tool 2.3.0-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/yubico-piv-tool.git (read-only, click to copy) |
---|---|
Package Base: | yubico-piv-tool |
Description: | Tool to interact with the PIV applet on a YubiKey NEO |
Upstream URL: | https://developers.yubico.com/yubico-piv-tool/ |
Licenses: | GPL3 |
Submitter: | travisghansen |
Maintainer: | travisghansen |
Last Packager: | travisghansen |
Votes: | 27 |
Popularity: | 0.29 |
First Submitted: | 2014-12-29 06:34 (UTC) |
Last Updated: | 2022-06-30 15:38 (UTC) |
Dependencies (6)
- openssl (openssl-hardened, openssl-static, quictls-openssl, openssl-git)
- pcsclite (pcsclite-nopy, pcsclite-toolbox, pcsclite-git)
- check (check-git) (make)
- cmake (cmake-git) (make)
- gengetopt (gengetopt-git) (make)
- help2man (help2man-git) (make)
Latest Comments
1 2 3 4 Next › Last »
prodrigestivill commented on 2022-07-17 15:55 (UTC)
YubiKeys work using the OpenSC PKCS#11 module, no need to install or use this package.
One just need to follow the instructions from ArchWiki and the YubiKey PIV module will just work.
travisghansen commented on 2022-06-19 20:26 (UTC)
@fuhry great! I'm mostly leaning towards skipping tests altogether for this package. If you make a PKGBUILD with that properly configured send it over.
fuhry commented on 2022-06-16 19:05 (UTC)
@travisghansen My fork is updated with patches that fix the use-after-free warnings in tests: https://github.com/fuhry/yubico-piv-tool.aur
I will also submit this patch upstream to Yubico.
grawity commented on 2022-05-19 06:01 (UTC) (edited on 2022-05-19 06:07 (UTC) by grawity)
For AUR packages, it doesn't really matter if the package runs tests or not – but if it does include tests, then it should actually run them through the
check() {}
function (but not in build(), so that users who have check enabled in their makepkg.conf options would get tests, but others could still opt out). Similarly, you can include test dependencies incheckdepends=()
so they won't be pulled in for non-check builds.But if the tests aren't being run at all, then there's no point in compiling them.
So I guess as a middle ground in this case you could have
build() {}
compile everything with -DSKIP_TESTS, but havecheck() {}
compile everything again with the tests included – and actually run them. (Although I'm not sure if rebuilding in check() is "normal", but if it works, it works.)travisghansen commented on 2022-05-19 03:57 (UTC)
I don't actually know what the policy is revolving around that. If that's the status quo then a patch/diff would certainly be welcome.
Wkennington commented on 2022-05-17 18:58 (UTC)
Just build with -DSKIP_TESTS and remove the test dependencies as we don't use the unit tests for anything.
eimann commented on 2022-05-10 20:23 (UTC) (edited on 2022-05-10 20:24 (UTC) by eimann)
Doesn't build for me at the moment:
travisghansen commented on 2022-03-12 23:51 (UTC)
patch added
koprulusector commented on 2022-03-12 23:37 (UTC) (edited on 2022-03-12 23:42 (UTC) by koprulusector)
This package fails to build for me, the error is:
I was able to fix this by adding this patch (which is also currently reflected in upstream's master branch):
travisghansen commented on 2021-02-11 05:08 (UTC)
The package is signed with an expired eky.
gpg --verify yubico-piv-tool-2.2.0.tar.gz.sig gpg: assuming signed data in 'yubico-piv-tool-2.2.0.tar.gz' gpg: Signature made Thu 17 Dec 2020 06:08:49 AM MST gpg: using RSA key 70D7145F2F35C4745501829A1B21578FC4686BFE gpg: Good signature from "Aveen Ismail aveen.ismail@yubico.com" [expired] gpg: Note: This key has expired! Primary key fingerprint: 1D73 08B0 055F 5AEF 3694 4A8F 27A9 C24D 9588 EA0F Subkey fingerprint: 70D7 145F 2F35 C474 5501 829A 1B21 578F C468 6BFE
The key is in the list for the package...it appears to just be expired. The package installs just fine for me though.
1 2 3 4 Next › Last »