4 ms·

I agree. The message should be more clear.

• tedivm 12y ago
  Your two messages contradict each other- >So, we've made it pretty clear from the start >I agree. The message should be more clear. It seems like a bit of backpedalling here. Rather than try to blame the author for not understanding or quoting the announcement that most people wouldn't have read anyways I think you should just commit to fixing the underlying problem (first the message that's passed, then the actual feature itself) and thank the author for drawing attention to it and educating your users on the security issue at hand.
  • kstenerud 12y ago
    The first quote is in reference to the announcement. The second quote refers to the CLI messaging. Shykes is acknowledging the problem.
• tuffle 12y ago
  It's good to hear that it will be fixed, but it's also troubling that a front-facing security issue took a #1 HN post, followed by debate in the comments before Docker recognized it.
  • shykes 12y ago
    All the issues in this post are already known and being actively discussed on the mailing lists and repo (including with the blog post author). However nobody so far had noted that the "image verified" message is misleading and should be clarified. I'm simply acknowledging that we should fix that, too.