W. Trevor King

On Sun, Apr 16, 2017 at 03:29:35PM -0700, Aleksa Sarai wrote: > IMO the primary concern should be the semantics of the spec. Does > the spec make distinctions between...

Pointer policy is just about Go, and the Go is non-normative, so this one can get tagged [v1.NEXT-maybe][1]. If we don't address it by 1.0, it makes life a bit...

> * Or should it return an error when it fails to configure the mappings again? This is my preference. I agree that the unmapped case doesn't seem very useful,...

> > > Or should it return an error when it fails to configure the mappings again? > > > > This is my preference. > > Ok. Should it...

> > Re-usability of layer de-duplication among container images. > > I'm a little bit worried about this goal for multiple reasons. > > Deduplication tables act like a form...

> I think you missed the second part of that point, which is that (unrelated to BEAST), taking advantage of deduplication of layers opens you up to fingerprinting attacks... Can...

> Do the 'more public keys' in OpenPGP belong to all the people you want to communicate with? They could. You could also encrypt to a key shared by the...

> Also, how do we pass our one or multiple friends' public key via command line? `docker commit --wrapping-pubkey file:` and allow multiple of those be passed? [`gpg` uses][1] `--symmetric...

> Pretty much everything is following the spirit (if not the letter) of the s/mime spec PKCS#7: https://tools.ietf.org/html/rfc2315 for Enveloped-data... [That section][1] talks about the same random-session-key-encrypted-to-each-recipient approach. Do you...

> ``` > enc.keyid: "0x12345678", > enc.keyid_owner_account: "image-author", > ``` I don't think we need an `enc.keyid_owner_account`. Will the symmetric key-store really need to shard these by author? If you're...