public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: lynis-3.0.6.tar.gz file on source.ipfire.org differs from Lynis upstream
Date: Sat, 04 Sep 2021 11:26:42 +0200	[thread overview]
Message-ID: <7a208c9f-720b-3706-7c70-349c19111599@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1758 bytes --]

Hello Marcel,

trying to update Lynis to 3.0.6 (from 3.0.3), I just noticed there already a lynis-3.0.6.tar.gz file
on https://source.ipfire.org/ with a different MD5 checksum and file size than the .tar.gz provided
by Lynis upstream (hosted on GitHub):

> pmueller(a)people01:/pub/sources/source-2.x$ ls -lah lynis-3.0.6.tar.gz 
> -rw-r--r-- 1 mlorenz people 329K Aug  1 11:45 lynis-3.0.6.tar.gz
> pmueller(a)people01:/pub/sources/source-2.x$ md5sum lynis-3.0.6.tar.gz
> 23cc369984d564e4a8232473b1ace137  lynis-3.0.6.tar.gz

Fetching the upstream's URL (https://github.com/CISOfy/lynis/archive/refs/tags/3.0.6.tar.gz) via
three different Tor circuits, using exit nodes in three different countries, always return a file
having these characteristics:

> $ ls -lah lynis-3.0.6.tar.gz
> -rw-r--r-- 1 pmu users 335K  4. Sep 10:56 lynis-3.0.6.tar.gz
> $ md5sum lynis-3.0.6.tar.gz
> c5429c532653a762a55a994d565372aa  lynis-3.0.6.tar.gz

Oddly enough, searching VirusTotal for 23cc369984d564e4a8232473b1ace137 gains a hit
(https://www.virustotal.com/gui/file/3005346e90339c18a4c626169c6f1d9fb8643bb0d0a049bcaf64b7ccb4fd272c/detection),
while a search for c5429c532653a762a55a994d565372aa returns nothing.

Looking at the contents of both .tar.gz's, your version is missing these files:

> ~/.github
> ~/.gitignore
> ~/plugins/plugin_pam_phase1
> ~/plugins/plugin_systemd_phase1
> ~/README.md
> ~/.travis.yml

Unfortunately, the maintainer of Lynis does not seem to provide a GPG signature or any other method
to verify the integrity of a downloaded source code. Therefore: Where did you fetch the lynis-3.0.6.tar.gz
file currently present on IPFire's source code server from? GitHub?

Thanks, and best regards,
Peter Müller

             reply	other threads:[~2021-09-04  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04  9:26 Peter Müller [this message]
2021-09-04 10:29 ` Adolf Belka
2021-09-06  6:29   ` Adolf Belka
2021-09-06  9:44     ` Michael Tremer
2021-09-06  9:56       ` Adolf Belka
2021-09-07 14:28         ` Michael Tremer
2021-10-23 16:36 ` State of affairs at lynis 3.0.6 (was: Re: lynis-3.0.6.tar.gz file on source.ipfire.org differs from Lynis upstream) Peter Müller
2021-10-23 17:06   ` Adolf Belka
2021-10-23 17:31     ` Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7a208c9f-720b-3706-7c70-349c19111599@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox