On Fri, Aug 14, 2009 at 01:47:26PM -0500, Shawn Walker wrote: > 1) store the serialized signature data in the same file as the catalog > part / update log, but wrap the contents in a container format using > something like MIME > * advantage: allows signature to be stored with data the signature is for > * disadvantage: while not as bad from a performance standpoint as double > writes, possibly not nearly as fast as just loading straight-up JSON > > 2) Given that the catalog.attrs file also contains a copy of the > signatures for each catalog part/updatelogs, just rely on the signature > data there since that file is 'self-signed'. > > 3) Store signature data in a separate file. > > What's the preferred direction?
I vote for #2. If you can live with catalog.attrs having its own signature inside, it seems fine to keep the signatures for the other catalog pieces with their metadata. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
