Date: Fri, 23 Jan 2015 17:13:32 -0600 From: Leif Pedersen <bilbo@hobbiton.org> To: Garrett Wollman <wollman@csail.mit.edu> Cc: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org> Subject: Re: Strange package checksum report Message-ID: <CAK-wPOhwMkoGbvvpeZoZUWYbisfM2cQHgA=tEs6ZD2FwcZvK1g@mail.gmail.com> In-Reply-To: <20150123215738.GT80181@numachi.com> References: <21698.32224.747971.146491@khavrinen.csail.mit.edu> <20150123215738.GT80181@numachi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I wonder if your computer's clock is off by a lot. Python might insist on rebuilding .pyc files if their timestamps are in the future. On Fri, Jan 23, 2015 at 3:57 PM, Brian Reichert <reichert@numachi.com> wrote: > 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@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-security > > To unsubscribe, send any mail to " > freebsd-security-unsubscribe@freebsd.org" > > -- > Brian Reichert <reichert@numachi.com> > BSD admin/developer at large > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org > " > -- As implied by email protocols, the information in this message is not confidential. Any middle-man or recipient may inspect, modify, copy, forward, reply to, delete, or filter email for any purpose unless said parties are otherwise obligated. As the sender, I acknowledge that I have a lower expectation of the control and privacy of this message than I would a post-card. Further, nothing in this message is legally binding without cryptographic evidence of its integrity. http://bilbo.hobbiton.org/wiki/Eat_My_Sig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAK-wPOhwMkoGbvvpeZoZUWYbisfM2cQHgA=tEs6ZD2FwcZvK1g>