There would be a few problems, such as initial costs, legal liability, creating the initial trust, but nothing I can see that can't be overcome.

That would indeed be the "least" of your problems, albeit still a major undertaking in my opinion.

The big issue in my opinion, is to get the "standard" browser manufacturers to include the certficates signed by the "non-profit consortium" in the list of certificate authorities whose certificates are accepted by default. Without that, the browser will still display the rather unsettling message to the user. As you said yourself: "This damages your site's credibility and will result in a drastic loss of confidence on the part of your potential customers.". So any effort you try in that respect, would need to the full cooperation of Microsoft, it being responsible for +95% of the browsers used in the world (something I'm not happy with, but which is a reality nonetheless). You ponder the likelihood of Microsoft cooperating with such a venture.

I think you need to ask yourself why you would need a certificate. If it's for a webshop, then there are plenty of solutions available where the actual payment is handled by a payment handler where you can piggyback on the certificate of the payment handler. If you're interested in preventing eavesdropping for a particular application, I think you can explain to the users why they will be getting the unsettling message and just sign the certificate yourself.

Wish I could give some more positive comments. But with the current financial interest of the Internet, I don't see a non-profit consortium happening anymore. I think it would be simply too little, too late.

Liz

In reply to Re: (OT) SSL Certificates: Self-Signing and Alternative Solutions by liz
in thread (OT) SSL Certificates: Self-Signing and Alternative Solutions by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.