From nobody Sun Mar 26 16:05:44 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pl1576pjsz42171 for ; Sun, 26 Mar 2023 16:05:47 +0000 (UTC) (envelope-from carlj@peak.org) Received: from mail.nrtc.syn-alias.com (mail.nrtc.syn-alias.com [129.213.214.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pl1564QPRz3L2N for ; Sun, 26 Mar 2023 16:05:46 +0000 (UTC) (envelope-from carlj@peak.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of carlj@peak.org designates 129.213.214.220 as permitted sender) smtp.mailfrom=carlj@peak.org; dmarc=pass (policy=none) header.from=peak.org X-Authed-Username: Y2FybGpAcGVhay5vcmc= Received: from [199.58.99.70] ([199.58.99.70:42317] helo=bay.localnet) by mail.peak.org (envelope-from ) (ecelerity 4.4.0.19839 r(msys-ecelerity:tags/4.4.0.0^0)) with ESMTPA id B6/EF-17916-95D60246; Sun, 26 Mar 2023 12:05:45 -0400 Received: from carlj by bay.localnet with local (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pgSsK-000NgO-BW for freebsd-questions@freebsd.org; Sun, 26 Mar 2023 09:05:44 -0700 From: Carl Johnson To: freebsd-questions@freebsd.org Subject: Re: Security Run Output References: <20230326081128.00005b98@seibercom.net> Date: Sun, 26 Mar 2023 09:05:44 -0700 In-Reply-To: (Odhiambo Washington's message of "Sun, 26 Mar 2023 15:32:57 +0300") Message-ID: <865yancxbb.fsf@bay.localnet> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (berkeley-unix) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Vade-Verdict: clean X-Vade-Analysis-1: gggruggvucftvghtrhhoucdtuddrgedvhedrvdehtddgleejucetufdoteggodetrfdotffvucfrrhho X-Vade-Analysis-2: fhhilhgvmecuufgjpfetvefqtfdppfftvfevpdfgpfggqdfptffvvedpqfgfvfenuceurghilhhouhht X-Vade-Analysis-3: mecufedtudenucenucfjughrpefhvffufhffjgfkfgggtgfgsehtqhdttddtreejnecuhfhrohhmpeev X-Vade-Analysis-4: rghrlhculfhohhhnshhonhcuoegtrghrlhhjsehpvggrkhdrohhrgheqnecuggftrfgrthhtvghrnhep X-Vade-Analysis-5: teekfedvveeiveetkeegleeggfdtvdfhvdekueeffeelkefgffejfeegjeevtedtnecukfhppeduleel X-Vade-Analysis-6: rdehkedrleelrdejtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeduleel X-Vade-Analysis-7: rdehkedrleelrdejtddphhgvlhhopegsrgihrdhlohgtrghlnhgvthdpmhgrihhlfhhrohhmpegtrghr X-Vade-Analysis-8: lhhjsehpvggrkhdrohhrghdprhgtphhtthhopehfrhgvvggsshguqdhquhgvshhtihhonhhssehfrhgv X-Vade-Analysis-9: vggsshgurdhorhhgpdhmthgrhhhoshhtpehsmhhtphdtvddrnhhrthgtrdgvmhgrihhlqdgrshhhuddr X-Vade-Analysis-10: shihnhgtrdhlrghnpdhnsggprhgtphhtthhopedupdhishgpnhgrpehtrhhuvgdprghuthhhpghushgv X-Vade-Analysis-11: rheptggrrhhljhesphgvrghkrdhorhhg X-Vade-Client: NRTC X-Spamd-Result: default: False [-3.63 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.987]; NEURAL_HAM_LONG(-0.98)[-0.982]; NEURAL_HAM_SHORT(-0.86)[-0.865]; DMARC_POLICY_ALLOW(-0.50)[peak.org,none]; R_SPF_ALLOW(-0.20)[+ip4:129.213.214.220]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[129.213.214.220:from]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:31898, ipnet:129.213.208.0/21, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[129.213.214.220:from] X-Rspamd-Queue-Id: 4Pl1564QPRz3L2N X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Odhiambo Washington writes: > On Sun, Mar 26, 2023 at 3:18=E2=80=AFPM Gerard E. Seibert > wrote: > >> For quite some time now, I have been receiving a warning message of >> 1025 packages with mismatched checksums in the daily "Security Run >> Output" email. They are all prefixed with "py39-" >> >> I don't want to wast time posting the entire list here, but it is >> available upon request if someone wants it. My question is, how do I >> correct this problem? This is a FreeBSD 13.1-release-p7 machine. >> >> Thanks >> > > > > pkg check -r or pkg check --recompute recalculates and sets the checksums > of installed packages. This command should only be used when the admi= n- > istrator has made modifications that invalidate a package checksum. > Spontaneous checksum problems can indicate data or security problems. > > I use that when I change config files for packages, but I have also had files show up in that list when I haven't changed them. Those have been very rare, but I have fixed them by re-installing the packages containing those files. You can use pkg check -s to verify which package is the problem. --=20 Carl Johnson carlj@peak.org