From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] BlueZ old releases have new checksums
Date: Wed, 04 Jan 2012 17:02:45 -0500 [thread overview]
Message-ID: <20120104220245.GE587@denix.org> (raw)
In-Reply-To: <CAMKF1sqCETomiuAx=9zQf2kLYCO8SMxi5=UUwOQ3LGj4RRJXTg@mail.gmail.com>
On Wed, Jan 04, 2012 at 12:53:25PM -0800, Khem Raj wrote:
> On Wed, Jan 4, 2012 at 12:14 PM, Chris Larson <clarson@kergoth.com> wrote:
> > On Wed, Jan 4, 2012 at 11:14 AM, Denys Dmytriyenko <denis@denix.org> wrote:
> >> The main archive of BlueZ/obexd/hcidump releases on kernel.org[1] finally
> >> re-appeared after missing for long time since kernel.org compromise.
> >> Unfortunately, all previous tarballs have new checksums, breaking builds for
> >> anyone w/o previous copy cached. Old copies were also extensively mirrored,
> >> so you never know which one you fetch next time...
> >
> > Heh, checksums changing after a security compromise, that's worrisome
> > :) should diff their contents to see what's going on, or whether its
> > just a gzip timestamp change or something.
>
> exactly. Make sure the tars are sane
Well, according to BlueZ maintainer[1], he gave the correct tarballs to
kernel.org people, but for some reason they untarred and re-packed them.
There's only 4 bytes difference, presumably timestamp...
[1] http://thread.gmane.org/gmane.linux.bluez.kernel/20040/focus=20041
--
Denys
WARNING: multiple messages have this Message-ID (diff)
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] BlueZ old releases have new checksums
Date: Wed, 04 Jan 2012 17:02:45 -0500 [thread overview]
Message-ID: <20120104220245.GE587@denix.org> (raw)
In-Reply-To: <CAMKF1sqCETomiuAx=9zQf2kLYCO8SMxi5=UUwOQ3LGj4RRJXTg@mail.gmail.com>
On Wed, Jan 04, 2012 at 12:53:25PM -0800, Khem Raj wrote:
> On Wed, Jan 4, 2012 at 12:14 PM, Chris Larson <clarson@kergoth.com> wrote:
> > On Wed, Jan 4, 2012 at 11:14 AM, Denys Dmytriyenko <denis@denix.org> wrote:
> >> The main archive of BlueZ/obexd/hcidump releases on kernel.org[1] finally
> >> re-appeared after missing for long time since kernel.org compromise.
> >> Unfortunately, all previous tarballs have new checksums, breaking builds for
> >> anyone w/o previous copy cached. Old copies were also extensively mirrored,
> >> so you never know which one you fetch next time...
> >
> > Heh, checksums changing after a security compromise, that's worrisome
> > :) should diff their contents to see what's going on, or whether its
> > just a gzip timestamp change or something.
>
> exactly. Make sure the tars are sane
Well, according to BlueZ maintainer[1], he gave the correct tarballs to
kernel.org people, but for some reason they untarred and re-packed them.
There's only 4 bytes difference, presumably timestamp...
[1] http://thread.gmane.org/gmane.linux.bluez.kernel/20040/focus=20041
--
Denys
next prev parent reply other threads:[~2012-01-04 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 18:14 BlueZ old releases have new checksums Denys Dmytriyenko
2012-01-04 20:14 ` Chris Larson
2012-01-04 20:14 ` [OE-core] " Chris Larson
2012-01-04 20:41 ` Adriano Pallavicino
2012-01-04 22:17 ` Denys Dmytriyenko
2012-01-04 20:53 ` Khem Raj
2012-01-04 20:53 ` [OE-core] " Khem Raj
2012-01-04 22:02 ` Denys Dmytriyenko [this message]
2012-01-04 22:02 ` Denys Dmytriyenko
2012-01-05 0:16 ` [oe] " Chris Larson
2012-01-05 0:16 ` [OE-core] " Chris Larson
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=20120104220245.GE587@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.