gtools

maintainer jose1711 · 0 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged Several concerns here: (1) There are two 'source=' arrays defined, which in bash means the second one silently overrides the first. The first source= line (pointing to sourceforge gnochm) is dead code and likely a copy-paste artifact, but it's suspicious. (2) The actual effective source is a tarball from manty.net which mirrors/archives old geocities content — this is an unofficial, personal/archival host, not an official upstream release mirror. (3) The package compiles and installs a C binary (gtools.c) from this unverified third-party source. The md5sums are present (not SKIP), so there is at least a checksum, but MD5 is weak and the host is non-authoritative. (4) The source is compiled C code that gets installed as a setuid-style multi-call binary with symlinks. The combination of: unofficial archival host + compiled C binary + weak MD5 checksum constitutes a genuine supply-chain concern. This is a real medium-severity issue — not a false positive — because executed compiled code is sourced from a non-official personal/archival host with no way to verify authenticity beyond a weak MD5.

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:12 source=('http://www.manty.net/www.geocities.com/SiliconValley/Lakes/1486/gtools-0_1_0.tgz'

MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): Several concerns here: (1) There are two 'source=' arrays defined, which in bash means the second one silently overrides the first. The first source= line (pointing to sourceforge gnochm) is dead code and likely a copy-paste artifact, but it's suspicious. (2) The actual effective source is a tarball from manty.net which mirrors/archives old geocities content — this is an unofficial, personal/archival host, not an official upstream release mirror. (3) The package compiles and installs a C binary (gtools.c) from this unverified third-party source. The md5sums are present (not SKIP), so there is at least a checksum, but MD5 is weak and the host is non-authoritative. (4) The source is compiled C code that gets installed as a setuid-style multi-call binary with symlinks. The combination of: unofficial archival host + compiled C binary + weak MD5 checksum constitutes a genuine supply-chain concern. This is a real medium-severity issue — not a false positive — because executed compiled code is sourced from a non-official personal/archival host with no way to verify authenticity beyond a weak MD5.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Jozef Riha <jose1711 at gmail dot com>
    
      2
    
      3pkgname=gtools
    
      4pkgver=0.1.0
    
      5pkgrel=1
    
      6pkgdesc="Tool to read 2MGUI disks in Linux"
    
      7arch=('x86_64')
    
      8url="http://www.manty.net/www.geocities.com/SiliconValley/Lakes/1486/smanty.html"
    
      9license=('GPL')
    
      10depends=('glibc')
    
      11source=("http://sourceforge.net/projects/gnochm/files/gnochm/0.9.11/gnochm-0.9.11.tar.gz" "Makefile.patch")
    
      12source=('http://www.manty.net/www.geocities.com/SiliconValley/Lakes/1486/gtools-0_1_0.tgz'
    
      13        'errno.patch')
    
      14
    
      15prepare() {
    
      16  patch -p1 -i errno.patch
    
      17}
    
      18
    
      19build() {
    
      20  gcc gtools.c -o gtools
    
      21}
    
      22
    
      23package() {
    
      24  install -Dm755 $srcdir/gtools $pkgdir/usr/bin/gtools
    
      25  for f in gcopy gdir gimage gtype
    
      26  do
    
      27    ln -sf gtools "$pkgdir/usr/bin/$f"
    
      28  done
    
      29  install -Dm644 $srcdir/COPYING $pkgdir/usr/share/licenses/gtools/COPYING
    
      30  install -Dm644 $srcdir/README $pkgdir/usr/share/doc/gtools/README
    
      31}
    
      32md5sums=('33c7806b35a99fb9dd95738f2017de83'
    
      33         '5636003942f5c0de253b064c983f4f29')
    
      34

Scan history

Scanned at (UTC)	Severity	Rules
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