Re: RFC: Unified package metadata format

Hi! On Tue, 2017-04-04 at 07:20:00 +, Niels Thykier wrote: > Guillem Jover: > > I don't think this is correct. Initial whitespace gets ignored (this is > > not clear from mtree(5), but that's what the various implementations do). > > The subset of type of lines I'm intending to support would

Re: RFC: Unified package metadata format

Matthew Garrett wrote: > Debian package unified metadata format In general, this looks like a good idea. Having this in a declarative form would have a variety of good uses. > Format: > > The file shall be stored within the control archive with the name > “mtree” and shall start with the

Re: RFC: Unified package metadata format

On Mon, Apr 3, 2017 at 6:58 PM, Guillem Jover wrote: > On Tue, 2017-03-28 at 16:22:58 -0700, Matthew Garrett wrote: >> Each entry shall be of the form >> >> /path/name key1=foo key2=bar > >> Ie, a leading space, a slash, and the path name of the installed file >> followed by

Re: RFC: Unified package metadata format

Guillem Jover: > Hi! > > On Tue, 2017-03-28 at 16:22:58 -0700, Matthew Garrett wrote: >> I'm looking at implementing support for IMA file signatures inside >> dpkg. The previous patches posted for this >> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850340) did so >> using extended PAX

Re: RFC: Unified package metadata format

Hi! On Tue, 2017-03-28 at 16:22:58 -0700, Matthew Garrett wrote: > I'm looking at implementing support for IMA file signatures inside > dpkg. The previous patches posted for this > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850340) did so > using extended PAX metadata, but people didn't

Re: RFC: Unified package metadata format

Matthew Garrett writes: > * Users auditing their systems can have full kernel-enforced > cryptographic assurance that the files they have on disk match the > files that Debian shipped. Doing that otherwise would involve you > having to take the machine offline. I