RE: A vision of an entirely different WebPKI of the future...

2018-08-20 Thread Tim Hollebeek via dev-security-policy
The only thing I'm going to say in this thread is that ICANN, registrars, and registries had two years to figure out how to handle GDPR and email addresses in WHOIS, and we all know how that turned out. Maybe we should let them figure out how to handle their existing responsibilities before we

Re: A vision of an entirely different WebPKI of the future...

2018-08-19 Thread Peter Gutmann via dev-security-policy
Matthew Hardeman via dev-security-policy writes: >That's very interesting. I would be curious to know the timing of this. Was >this before or after massive deployment of DNSSEC by the registries? Some time before. To the best of my knowledge DNSSEC considerations had nothing to do with this

Re: A vision of an entirely different WebPKI of the future...

2018-08-17 Thread Matthew Hardeman via dev-security-policy
On Friday, August 17, 2018 at 2:01:55 AM UTC-5, Peter Gutmann wrote: > That was actually debated by one country, that whenever anyone bought a domain > they'd automatically get a certificate for it included. Makes perfect sense, > owning the domain is a pretty good proof of ownership of the

Re: A vision of an entirely different WebPKI of the future...

2018-08-17 Thread Matthew Hardeman via dev-security-policy
On Thursday, August 16, 2018 at 6:18:47 PM UTC-5, Jakob Bohm wrote: > The main cause of this seems to be that CT has allowed much more > vigorous prosecution of even the smallest mistake. Your argument > is a sensationalist attack on an thoroughly honest industry. I certainly didn't mean it as

Re: A vision of an entirely different WebPKI of the future...

2018-08-17 Thread Peter Gutmann via dev-security-policy
Matthew Hardeman via dev-security-policy writes: >What if the various user agents' root programs all lobbied ICANN to impose a >new technical requirement upon TLD REGISTRY operators? That was actually debated by one country, that whenever anyone bought a domain they'd automatically get a

Re: A vision of an entirely different WebPKI of the future...

2018-08-16 Thread Jakob Bohm via dev-security-policy
On 16/08/2018 21:51, Matthew Hardeman wrote: Of late, there seems to be an ever increasing number of misissuances of various forms arising. Despite certificate transparency, increased use of linters, etc, it's virtually impossible to find any CA issuing in volume that hasn't committed some

Re: A vision of an entirely different WebPKI of the future...

2018-08-16 Thread Matthew Hardeman via dev-security-policy
On Thursday, August 16, 2018 at 3:34:01 PM UTC-5, Paul Wouters wrote: > Why would people not in the business of being a CA do a better job than > those currently in the CA business? I certainly do not assert that there would be no learning curve. However, these same registries for the generic

Re: A vision of an entirely different WebPKI of the future...

2018-08-16 Thread Matthew Hardeman via dev-security-policy
On Thursday, August 16, 2018 at 3:18:38 PM UTC-5, Wayne Thayer wrote: > What problem(s) are you trying to solve with this concept? If it's > misissuance as broadly defined, then I'm highly skeptical that Registry > Operators - the number of which is on the same order of magnitude as CAs > [1] -

Re: A vision of an entirely different WebPKI of the future...

2018-08-16 Thread Paul Wouters via dev-security-policy
On Thu, 16 Aug 2018, Matthew Hardeman via dev-security-policy wrote: 1. Run one or more root CAs Why would people not in the business of being a CA do a better job than those currently in the CA business? I recognize it's a radical departure from what is. I'm interested in understanding

Re: A vision of an entirely different WebPKI of the future...

2018-08-16 Thread Wayne Thayer via dev-security-policy
What problem(s) are you trying to solve with this concept? If it's misissuance as broadly defined, then I'm highly skeptical that Registry Operators - the number of which is on the same order of magnitude as CAs [1] - would perform better than existing CAs in this regard. You also need to consider