Symantec, in previous blog posts on their site, has indicated that they will support their customers [1].
That said, it is fair point that the plan should spell out what happens if symantec does not cooperate. It seems appropriate to have the plan do what it says -- scheduled phase out of the old roots -- with the same timescale. If symantec does not step up to fill their customer needs, I am sure one or more of their competitors will [and remember all this only applies to symantec customers who need publicly trusted certs... one big appeal of the proposal is that non-public uses can remain unaffected]. As the recent Wosign/Startcom experiences teaches, though, if the CA is not cooperative, it is very important for the browsers to step in with messaging. Not sure what form this would take, since most developers I know do not use beta/nightly versions of browsers, so it would need to be something in actual releases. Perhaps a single line with orange background just below URL box that says "in one month, this site will cease to be trusted by major browsers [click here for why]", or somesuch. With the link being very clear: it is the owner of the website that needs to update their certificate. Just a thought. 1. https://www.symantec.com/connect/blogs/message-our-ca-customers "In the event Google implements its proposal, Symantec will ensure your websites, webservers or web applications continue to work across browsers." On Wednesday, May 10, 2017 at 4:11:59 PM UTC-4, [email protected] wrote: > On Wednesday, 10 May 2017 17:52:40 UTC+2, Gervase Markham wrote: > > On 09/05/17 16:51, Gervase Markham wrote: > > > * Editing the proposal to withdraw the "alternative" option, leaving > > > only the "new PKI" option. > > > > This has now been done: > > > > https://docs.google.com/document/d/1RhDcwbMeqgE2Cb5e6xaPq-lUPmatQZwx3Sn2NPz9jF8/edit# > > > > > * Engagement here in m.d.s.p. with the community to refine and flesh out > > > the "new PKI" proposal, based on the Google outline but examining it and > > > enhancing it to make sure it is practical, both from an implementation > > > perspective and to reduce disruption to sites as far as possible. > > > > I would appreciate people's comments on the details of the current draft. > > Makes sense to me. > > But it does seem to assume that Symantec will cooperate with this. What > happens if they decide not to is less clear. Perhaps it would be a good idea > to indicate which steps will be taken in any case? _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy

