On some of my machines, I've been noticing the following in the nightly security mail: Checking for packages with mismatched checksums: p5-XML-SAX-0.99_2: /usr/local/lib/perl5/site_perl/XML/SAX/ParserDetails.ini python27-2.7.9: /usr/local/lib/python2.7/UserDict.pyc python27-2.7.9: /usr/local/lib/python2.7/_weakrefset.pyc python27-2.7.9: /usr/local/lib/python2.7/abc.pyc python27-2.7.9: /usr/local/lib/python2.7/codecs.pyc python27-2.7.9: /usr/local/lib/python2.7/copy_reg.pyc python27-2.7.9: /usr/local/lib/python2.7/encodings/__init__.pyc [ a bunch of other .pyc files elided ] Does anyone know what causes this? Force-reinstalling the package fixes it, but only temporarily -- by the time the next security mail comes, it's back in this state. -GAWollman
Maybe hardware going bad? If you're using ZFS, it's probably not the hard disk since ZFS would correct it before pkg can notice it. (Unless you have no redundancy, but then you'd still see checksum errors in zpool status) Maybe bad memory that causes corruption? Kind Regards, Robert Sevat On 01/23/2015 05:59 PM, Garrett Wollman wrote:> On some of my machines, I've been noticing the following in the > nightly security mail: > > Checking for packages with mismatched checksums: > p5-XML-SAX-0.99_2: /usr/local/lib/perl5/site_perl/XML/SAX/ParserDetails.ini > python27-2.7.9: /usr/local/lib/python2.7/UserDict.pyc > python27-2.7.9: /usr/local/lib/python2.7/_weakrefset.pyc > python27-2.7.9: /usr/local/lib/python2.7/abc.pyc > python27-2.7.9: /usr/local/lib/python2.7/codecs.pyc > python27-2.7.9: /usr/local/lib/python2.7/copy_reg.pyc > python27-2.7.9: /usr/local/lib/python2.7/encodings/__init__.pyc > [ a bunch of other .pyc files elided ] > > Does anyone know what causes this? Force-reinstalling the package > fixes it, but only temporarily -- by the time the next security mail > comes, it's back in this state. > > -GAWollman-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <http://lists.freebsd.org/pipermail/freebsd-security/attachments/20150123/120322c7/attachment.sig>
On Fri, Jan 23, 2015 at 11:59:12AM -0500, Garrett Wollman wrote:> On some of my machines, I've been noticing the following in the > nightly security mail:The *.pyc are blobs of byte code that Python generates if the interpreter chooses to compile a module. Maybe the package erroneously contains them, and the interpreter is regenerating them, according to whatever logic is would apply. Maybe a timestamp issue? When you do a force reinstall ,what are the timestamps as compared to the corresponding python modules (*.pl)?> > Checking for packages with mismatched checksums: > p5-XML-SAX-0.99_2: /usr/local/lib/perl5/site_perl/XML/SAX/ParserDetails.ini > python27-2.7.9: /usr/local/lib/python2.7/UserDict.pyc > python27-2.7.9: /usr/local/lib/python2.7/_weakrefset.pyc > python27-2.7.9: /usr/local/lib/python2.7/abc.pyc > python27-2.7.9: /usr/local/lib/python2.7/codecs.pyc > python27-2.7.9: /usr/local/lib/python2.7/copy_reg.pyc > python27-2.7.9: /usr/local/lib/python2.7/encodings/__init__.pyc > [ a bunch of other .pyc files elided ] > > Does anyone know what causes this? Force-reinstalling the package > fixes it, but only temporarily -- by the time the next security mail > comes, it's back in this state. > > -GAWollman > > _______________________________________________ > freebsd-security at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe at freebsd.org"-- Brian Reichert <reichert at numachi.com> BSD admin/developer at large
Garrett Wollman <wollman at csail.mit.edu> writes:> Checking for packages with mismatched checksums: > p5-XML-SAX-0.99_2: /usr/local/lib/perl5/site_perl/XML/SAX/ParserDetails.iniThis file is updated whenever you install or remove a SAX parser, so this is expected. There are at least half a dozen different Perl SAX implementations in the ports tree.> python27-2.7.9: /usr/local/lib/python2.7/UserDict.pyc > python27-2.7.9: /usr/local/lib/python2.7/_weakrefset.pyc > python27-2.7.9: /usr/local/lib/python2.7/abc.pyc > python27-2.7.9: /usr/local/lib/python2.7/codecs.pyc > python27-2.7.9: /usr/local/lib/python2.7/copy_reg.pyc > python27-2.7.9: /usr/local/lib/python2.7/encodings/__init__.pyc > [ a bunch of other .pyc files elided ]These are Pyhon bytecode files. They are automatically regenerated if you have write access to them and Python thinks they are stale when it tries to load them. Apparently, Python's definition of "stale" is slightly more complex than just comparing timestamps; they are one of the reasons why Baptiste gave up reproducible package builds. Is your clock synchronized with NTP? Is this a VM? What is the underlying filesystem? DES -- Dag-Erling Sm?rgrav - des at des.no