News for hackers. Stuff that matters.
Re:Docker Image Insecurity by thu on Tuesday December 23, 2014 @12:05PM (#8788933)
I think this is because they regard the tar'd layers as a transport mechanism, not as the signed payload itself.
Re:Docker Image Insecurity by justincormack on Tuesday December 23, 2014 @12:25PM (#8789029)
Yes that makes sense, as tar is not fully deterministic, so untar and retar might give a different checksum on the same files (eg ordering). However it is generally better to keep the same bits people signed regardless.
Re:Docker Image Insecurity by thu on Tuesday December 23, 2014 @02:36PM (#8789786)
Maybe you could use the Git packfile format; this is a self-contained compressed Merkle-tree. If you ever need to reconstruct deterministically the tar from that, you can use something like pristine-tar[0].

[0]: https://joeyh.name/code/pristine-tar/

Re:Docker Image Insecurity by thaJeztah on Tuesday December 23, 2014 @06:04PM (#8790724)
Sounds interesting. Perhaps you should create a proposal for that on the docker issue tracker, so that it can be discussed as a possible alternative?