ifd-rutokens

maintainer vashvampir · 0 votes · scanned 2026-08-03 00:08:14.047287
MEDIUM
View on AUR ↗
Why flagged The PKGBUILD downloads a prebuilt binary .deb from download.rutoken.ru, which is the official vendor download host for Aktiv Co (the Russian hardware token manufacturer). The sha512sum is present and pins the artifact, which mitigates opportunistic substitution. However, the binary is a closed-source prebuilt shared library/driver that will be loaded by pcsc-lite into privileged processes, and there is no way to verify it against a reproducible build or an independently signed release. The host is the official vendor domain (rutoken.ru), not a personal or third-party mirror, so this is a standard 'binary blob from vendor' pattern common in AUR driver packages. The risk is real but typical for proprietary hardware drivers: if the vendor's download server were compromised the sha512 check would catch a substitution, but the binary itself is opaque. This is a borderline medium/clean case; the medium rating is defensible because it is an executed binary (a PCSC driver loaded into pcscd) from a closed-source vendor with no source available, but it is not clearly more dangerous than other vendor binary driver packages in the AUR.

Triggered rules

MEDIUM source=() URL on a non-standard host source_untrusted_domain

One or more source=() URLs point to a host outside the trusted allowlist (github.com, gitlab.com, codeberg.org, pypi.org, …).

  • PKGBUILD:14 source_x86_64=("https://download.rutoken.ru/Rutoken/Drivers_Unix/${pkgver}/Linux/x64/${pkgname}_${pkgver}_amd64.deb")
MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD downloads a prebuilt binary .deb from download.rutoken.ru, which is the official vendor download host for Aktiv Co (the Russian hardware token manufacturer). The sha512sum is present and pins the artifact, which mitigates opportunistic substitution. However, the binary is a closed-source prebuilt shared library/driver that will be loaded by pcsc-lite into privileged processes, and there is no way to verify it against a reproducible build or an independently signed release. The host is the official vendor domain (rutoken.ru), not a personal or third-party mirror, so this is a standard 'binary blob from vendor' pattern common in AUR driver packages. The risk is real but typical for proprietary hardware drivers: if the vendor's download server were compromised the sha512 check would catch a substitution, but the binary itself is opaque. This is a borderline medium/clean case; the medium rating is defensible because it is an executed binary (a PCSC driver loaded into pcscd) from a closed-source vendor with no source available, but it is not clearly more dangerous than other vendor binary driver packages in the AUR.

PKGBUILD

1 offending line(s) highlighted
1# Author Aktov Co <info@rutoken.ru>
2# Maintainer: Mikhail Isaev <admin@ismv.ru>
3pkgname=ifd-rutokens
4pkgver=1.0.4
5pkgrel=1
6pkgdesc="Aktiv Co Rutoken S driver. Allows users to access Rutoken S through pcsc-lite."
7arch=('x86_64')
8url="https://www.rutoken.ru/support/download/nix/"
9license=('custom')
10groups=('')
11depends=('glibc>=2.3.2' 'libusb-compat>=0.1.8')
12options=('!strip' '!emptydirs')
13install=${pkgname}.install
14source_x86_64=("https://download.rutoken.ru/Rutoken/Drivers_Unix/${pkgver}/Linux/x64/${pkgname}_${pkgver}_amd64.deb")
15sha512sums_x86_64=('7e7733bfa16838a69d9361366a73062231f31feca0f8ea3ae155b78f08014c2fe4ea2d147dcfc58ae2ba4afaaa14be55e6efd34b87586d1ded488d4267dba984')
16
17package() {
18
19 # Extract package data
20 tar -xz -f data.tar.gz -C "${pkgdir}"
21
22}
23

Scan history

Scanned at (UTC)SeverityRules
2026-08-03 00:08:14 MEDIUM 2
2026-08-02 00:16:08 MEDIUM 2
2026-08-01 00:11:18 MEDIUM 2
2026-07-31 00:14:10 MEDIUM 2
2026-07-30 00:17:23 MEDIUM 2
2026-07-29 00:25:53 MEDIUM 2
2026-07-28 00:07:28 MEDIUM 2
2026-07-27 00:24:32 MEDIUM 2
2026-07-26 00:07:32 MEDIUM 2
2026-07-25 00:13:44 MEDIUM 2
2026-07-24 00:02:28 MEDIUM 2
2026-07-23 00:14:47 MEDIUM 2
2026-07-22 00:29:32 MEDIUM 2
2026-07-21 00:24:15 MEDIUM 2
2026-07-20 00:19:49 MEDIUM 2
2026-07-19 00:17:08 MEDIUM 2
2026-07-18 00:14:48 MEDIUM 2
2026-07-17 00:06:16 MEDIUM 2
2026-07-16 00:05:41 MEDIUM 2
2026-07-15 00:09:25 MEDIUM 2

Report a package

Reports go to the AURWatch maintainer (one person) and are read by hand. No login required.

0 / 4000
Your suggestion