Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - nitrokey-app

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: nitrokey-app 0.6.3-1

Git Clone URL: https://aur-dev.archlinux.org/nitrokey-app.git (read-only)
Package Base: nitrokey-app
Description: Nitrokey management application
Upstream URL: https://www.nitrokey.com
Keywords: crypto smartcard
Licenses: GPL3
Submitter: cjsthompson
Maintainer: milouse
Last Packager: milouse
Votes: 10
Popularity: 1.189840
First Submitted: 2015-02-12 07:56
Last Updated: 2017-01-27 09:00

Required by (0)

Sources (1)

Latest Comments

shieldwed commented on 2016-11-15 22:30

@mis thank you very much for this update

mis commented on 2016-11-14 15:18

This was orphaned so I applied your suggestions.
I don't use it and orphaned it again.

milouse commented on 2016-08-10 07:45


In fact, there is a problem with the naming of this package. As it fetch the last git revision, it must be called nitrokey-app-git [1]. Thus this package should either be renamed or build nitrokey-app from the last known release, in this case the v0.4 tag.

Also, you should remove the icon cache related lines from the nitrokey-app.install file as this is a process managed by hooks now.


[1] https://wiki.archlinux.org/index.php/VCS_package_guidelines

zapper commented on 2016-08-10 01:10

When is this going to be updated?

LittleAlex commented on 2016-05-28 08:40


there is a HOTP-Bug in this version of Nitrokey-App.


Would be great if you update the package.

PS: Thanks for the package. :-)

cjsthompson commented on 2015-11-09 20:50

Thanks for the report. I've corrected it here. The fix is coming as soon as I get around to updating it.

millson249 commented on 2015-09-25 00:51

I'd recommend adding the cmake packages as a build dependency for this. For whatever reason I didn't have that installed and, naturally, the package failed to build. Fortunately it was an easy fix! But it might be wise to add it as a build dependency for anyone else who may not realize the issue.