From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: lzma tarball usage
Date: Thu, 08 May 2008 09:17:08 -0400 [thread overview]
Message-ID: <4822FD54.4000904@gentoo.org> (raw)
In-Reply-To: <20080507185239.541383c9@halo.dirtyepic.sk.ca>
Ryan Hill wrote:
> On Wed, 07 May 2008 16:23:12 +0300
> Mart Raudsepp <leio@gentoo.org> wrote:
>
>
>> Hello,
>>
>> Over the course of this year, a lzma-utils buildtime dependency has
>> been added to a few system packages, to handle .tar.lzma tarballs.
>> This has huge implications on the requirement of the system toolchain,
>> which is highly disturbing from a minimal (lets say embedded) systems
>> concern - lzma-utils depends on the C++ compiler and the libstdc++
>> beast, while a minimal system would like to avoid this at all cost.
>>
>
> The new lzma-utils codebase uses liblzma, written in C. It's at the
> alpha stage but supposedly supports encoding/decoding the current lzma
> format "well enough" (;P). It probably has some fun bugs to find
> and squish.
>
> http://sf.net/mailarchive/forum.php?thread_name=200804251652.58484.lasse.collin%40tukaani.org&forum_name=lzmautils-announce
>
>
According to the mailing list this change was done to fix security holes
in the format and also resulted in a slightly different format that's
incompatible with the previous verion. So lzma 5.x and higher will be a
different on disk format. It's troubling to me that projects are using
lzma when it's on disk format isn't even final and the project has
security issues.
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-05-08 13:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 13:23 [gentoo-dev] RFC: lzma tarball usage Mart Raudsepp
2008-05-07 13:34 ` Fabian Groffen
2008-05-08 18:45 ` Mart Raudsepp
2008-05-08 19:09 ` Fabian Groffen
2008-05-08 19:17 ` Santiago M. Mola
2008-05-08 19:21 ` Mart Raudsepp
2008-05-17 15:55 ` Enrico Weigelt
2008-05-10 7:32 ` Mike Frysinger
2008-05-10 7:36 ` Fabian Groffen
2008-05-10 9:57 ` Mike Frysinger
2008-05-07 14:12 ` Natanael Copa
2008-05-07 14:55 ` Ulrich Mueller
2008-05-08 8:06 ` [gentoo-dev] " Duncan
2008-05-08 10:49 ` Diego 'Flameeyes' Pettenò
2008-05-08 10:59 ` Graham Murray
2008-05-08 11:31 ` Diego 'Flameeyes' Pettenò
2008-05-08 11:41 ` Ulrich Mueller
2008-05-07 14:53 ` [gentoo-dev] " Benedikt Morbach
2008-05-07 15:03 ` Ulrich Mueller
2008-05-07 15:02 ` Benedikt Morbach
2008-05-07 16:06 ` Chris Gianelloni
2008-05-07 18:38 ` Enrico Weigelt
2008-05-07 20:01 ` Richard Freeman
2008-05-07 20:10 ` Doug Goldstein
2008-05-08 0:52 ` [gentoo-dev] " Ryan Hill
2008-05-08 13:17 ` Doug Goldstein [this message]
2008-05-08 13:28 ` Ciaran McCreesh
2008-05-08 13:32 ` Doug Goldstein
2008-05-08 13:36 ` Ciaran McCreesh
2008-05-08 13:43 ` Doug Goldstein
2008-05-09 8:37 ` James Cloos
2008-05-08 14:30 ` Diego 'Flameeyes' Pettenò
2008-05-08 13:41 ` Doug Goldstein
2008-05-08 14:33 ` Robert Buchholz
2008-05-09 1:04 ` Ryan Hill
2008-05-08 11:30 ` [gentoo-dev] " Luca Barbato
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=4822FD54.4000904@gentoo.org \
--to=cardoe@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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