as in --untrusted=false for all? or does this mean something else?

EDIT: i did not read the original blurb, my b, but maybe this should say that too regardless, for non readers like me

added ;)

Notary is an implementation detail of the trust feature of Docker. Do we want to make it appear all the way up to the UX? Isn't making the name appear here contradictory to the idea of having well spec'ed ingredients that we can substitute with other conforming implementations?

--untrusted=false feels a little like a double negative. E.g it is not un-trusted. Therefore it might be difficult for non-native english speakers to divine the expected behaviour. It's simpler to say it is trusted. I appreciate trusted is a loaded term, so maybe it's not the right word to use. Per icecrime's comment, I agree that we should use something more generic. Perhaps splitting the two workflows (signing and verification) would make sense - e.g DOCKER_IMAGE_VERIFY and DOCKER_IMAGE_SIGN

This is so eventually we can make trusted the default and not have it be counterintuitive.

Otherwise all options sound weird when they are turned on by default. There was a alot of back and forth on this already and I think I am still pro- the current approach.

Agreed --untrusted is a bit weird.

Perhaps --verify-image=true as a default, then the user would pass --verify-image=false?

Ah, I see @dave-tucker said a similar thing below. Just adding a +1 to his suggestions.

The doc should probably mention the default value (=true)

Perhaps --verify=false