Accountability

Is what your $1000/yr buys you from VeriSign. That is to say that if they screw up(and it can be demonstrably assigned to them), allowing credit card info to be hacked, your idenity to be 'spoofed' by someone else, etc, that they have resources to PAY.

Let's not forget that the core statement of most Open Source licenses says: NO WARRANTY. In other words, if something goes wrong, you suffer damage to your systems, your reputation, your business you're out of luck.

Hopefully, some of the 1K also goes to things like R&D, testing on systems, infrastructure maintenance, and internal and external security. Things like background checks on the employees who actually handle the secured servers; bonded security guards on their data centers; good locks on the doors; good salaries to attract talented, if mercenary, people.

A 'non-profit' or 'open-source' sounds nice, but you're dependent on the 'good will' of the people maintaining and contributing to the system. What happens when a 'fund-raiser' falls short one year? Cheaper locks, no background checks on the guards, cheaper or fewer CPU's, thinner pipes?

Eventually a non-profit is going to have to charge fees anyway to maintain a secure system, or to validate people perhaps contributing their systems.

Profit my be an evil motive to some, but it is at its core an incentive to do things right. The Soviet Union spent 70 years learning that the hard way. Profit also supplies a pool of 'cash' to get things done without having the worry about a fundraiser. A track record of profits can also get banks to loan you money to upgrade your infrastructure.

In reply to Re: (OT) SSL Certificates: Self-Signing and Alternative Solutions by ptkdb
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.