Slashdot Mirror


Free SSL Certificate Project

An anonymous reader writes "Do you have a website or run even a web server and want to secure the traffic between your visitors browser and the web site? Did you find out, that in order to make your site SSL aware, you'll need a SSL (Secure Sockets Layer) certificate? Are you also surprised to find out that such a certificate can cost you up to a few hundred dollars, valid for one year only? For what, you might ask yourself? Linuxlookup.com is running a small article on free SSL certificates."

106 of 374 comments (clear)

  1. sweet by lakerdonald · · Score: 2, Interesting

    Sweet! I've never liked the idea of forking over money so that your site is deemed secure.

    1. Re:sweet by tim256 · · Score: 2, Insightful
      Certificate companies are also providing a service. Their servers must be involved in each and every SSL connection.

      Although, it seems that many of these server certificates are at least a little overpriced. I guess there's a price to pay for that extra compatibility you get because the client certificate is already installed on popular web browsers.

    2. Re:sweet by Abalamahalamatandra · · Score: 2, Informative

      Um, what?

      You seem a bit uninformed. There's no connection made between end-user software and Certificate Authority's systems when an SSL site is accessed - the browser software has the CA's certificate loaded, and the web site's certificate is signed by that certificate.

      There is occasional Certificate Revocation List (CRL) processing on occasion, but certainly not with "each and every SSL connection".

      The CA provides a service in (supposedly, see Verisign) doing due diligence to ensure that a given certificate is only provided to the site that's detailed in the certificate, so you can trust that they're who they say they are. They also maintain CRL distribution points in case they screw that up. That's about it.

    3. Re:sweet by flakac · · Score: 4, Informative

      If you don't feel like forking over money, download OpenSSL and generate your own certs. Here's a good how-to if you're interested. But if you go this route, your users will either have to install your root certificate into their browser's trusted store (I don't recommend this, but hey, it's your computer), or they'll have to click through an annoying dialog warning that the certificate is not trusted.

      What you're paying for when you buy a certificate is not so much the certificate itself, but for the processes surrounding the issuing of said certificate. When getting a certificate, you must prove to the registration authority that you are who you are, and that you have the legal right to obtain a certificate for your organization. Only after this verification has taken place will you be issued a certificate from a trusted authority. But your users can examine the certificate's chain of trust, and verify who they're talking to. Impossible to do with a self-signed or otherwise untrusted certificate.

    4. Re:sweet by Himring · · Score: 2

      What you're paying for when you buy a certificate is not so much the certificate itself, but for the processes surrounding the issuing of said certificate.

      Which, apparently, was crappy as of 2001 where they issued a cert (a Microsoft cert no less) that turned out to be fraudulent. That is, they first gave the cert and then did this "process" you're speaking of wherein they found the person to have been a fraud -- should have been the other way around....

      So much for process. Hopefully, they've 'fixed' that by now....

      Link to the incident: http://www.pkiforum.com/resources/alert_verisignce rts.html/

      --
      "All great things are simple & expressed in a single word: freedom, justice, honor, duty, mercy, hope." --Churchill
  2. Well.... by Tyler+Eaves · · Score: 2, Insightful

    I thought the whole point of SSL is that not just anyone could get a cert...

    --
    TODO: Something witty here...
    1. Re:Well.... by glwtta · · Score: 4, Informative
      How does that make sense? Anyone can get one, the point is that you should be able to match up the certificate to its owner, with some degree of certainty.

      And getting one isn't the issue at all - you can generate as many as you want yourself - it's getting one that means something that's the issue.

      --
      sic transit gloria mundi
    2. Re:Well.... by MyIS · · Score: 2, Insightful

      I agree. I believe the whole point of Verisign's and others' existence is to make sure that the name/organization that shows up on the cert is actually corresponding to the person they're handing it to. And such verification costs money, or at least should take more than a simple Web form.

      The post on linuxlookup seems like a pretty corny ad for some hosting company anyway. Pfft!

      --
      http://zero-to-enterprise.blogspot.com/
    3. Re:Well.... by bendelo · · Score: 2, Informative

      Windows in 6 Bytes (IA-32) : 90 90 90 90 CD 19

      Your sig caught my eye, and my brain translated it as NOP, NOP, NOP, NOP, INT 19. From what I remember, interrupt 19 is the disk I/O interrupt. Doesn't it just call the bootstrap loader on drive DL?

    4. Re:Well.... by Best+ID+Ever! · · Score: 5, Insightful

      Well, the point of SSL is to encrypt communications. But the point of a signed certificate is to prevent impersonation. If a trusted authority allows anyone to get a certificate for any domain name, then it becomes easy to impersonate someone's site.

      I'm not sure what the point of this is, if the browsers don't have these folks listed as trusted authorities. You can already sign your own certificate and get the same effect. But if you are asking your customers/users to accept a certificate that is not signed by a trusted authority, you are leaving yourself open to being impersonated.

    5. Re:Well.... by vwjeff · · Score: 2, Interesting

      I thought the whole point of SSL is that not just anyone could get a cert...

      Exactly.

      I would only support a system that had many levels of validation.

      1. You create an account and submit your site.
      2. There would be a required waiting period of 30 days.
      3. You would login to your account and request that your site be reviewed.
      4. You must submit a deposit of $10 which will be returned when your site has been approved. If your site was not approved you must login to your account and request a refund.
      5. Your site would be reviewed by PAID employees. The funds will come from site advertisements and deposits from sites that were not approved and returned.
      6. Profit?

      A free system can exist but it must be HARD to get the certificate.

    6. Re:Well.... by cbreaker · · Score: 2, Insightful

      But it doesn't work like that. When verisign is signing certs for companies that call themselves "Click YES to view this web page!!!" in order to get people to install spyware, then what good is it?

      I think the SSL encryption part itself should be good enough, and all this trusted CA crap just needs to go away.

      --
      - It's not the Macs I hate. It's Digg users. -
    7. Re:Well.... by ljhiller · · Score: 4, Informative
      I suspect you would have a hard time getting a certificate from Verisign with the name "Microsoft" or "National Security Agency".

      I can't begin to imagine why why you would say this.

  3. erg by relluf · · Score: 3, Insightful

    Just explain to your customers why you cert isnt registered.

  4. cacert.org by TypoNAM · · Score: 5, Informative

    I've always used cacert.org for free SSL certificate s. :)

    --
    This space is not for rent.
    1. Re:cacert.org by cookd · · Score: 2, Informative

      Or you can roll your own. The only problem is that the cert is signed by you, so your customer's browser can't be certain that you are who you say you are, and will therefore issue a warning to the user.

      For installing a cert on a Windows IIS server:
      Find a recent copy of the makecert tool.
      makecert -r -pe -n "CN=www.yourserver.com" -b 01/01/2000 -e 01/01/2036 -eku 1.3.6.1.5.5.7.3.1 -ss my -sr localMachine -sky exchange -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12
      Then use the IIS management tool to "assign an existing certificate" to the site. The certificate created before should show up as available.

      For installing a cert on Apache:
      ssleay req -out certificate.pem -nodes -new -x509 -days 2000
      Now you have a pair of certificate files you can put in whatever directory your Apache install expects them to be in.

      --
      Time flies like an arrow. Fruit flies like a banana.
    2. Re:cacert.org by IchBinEinPenguin · · Score: 4, Informative

      This mob will run into the same problems as CaCERT: convincing browser distributeers to include their root certificate.
      (Hello Microsoft, We're a communist OpenSource project trying to educate netizens that they don't have to fork out gazzillions of dollars to big corporations use the Web. Would you mind helping us by including our root certificate with IE? Hello? Did we get cut off?)
      Without that, the cert is not much better than a self-signed one.

    3. Re:cacert.org by Trejkaz · · Score: 2, Informative

      Let's see... With a CAcert certificate, a user only has to add a certificate to their browser once. With a self-signed certificate, they have to add it to their browser once for every single server, and once again every single time the server changes their certificate.

      I'd say that pays off pretty quickly.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    4. Re:cacert.org by jmt(tm) · · Score: 2, Informative

      StartCom cerificates are much worse than self-signed SnakeOil certificates.

      There is no verification of the user applying for a certificate, so I could easily get a certificate stating I'm PayPal. Would make the job of people trying to make money of the recently discussed IDN weakness even easier, wouldn't it?

      Additionally, the private key is generated on their servers, meaning that it's not private at all. Makes eavesdropping and man in the middle attacks so much easier.

      Nothing to see here. Move on. I don't think the Mozilla Foundation will deliver the StartCom root certificate in their default builds, and if they do, their folks should get spanked and have to write "I will not generate private keys on other machines than my own" a hundred times.

      Import the root certificate yourself, and you are screwed. Use CAcert or FreeSSL instead. Or self-signed certificates if it does not matter.

  5. Secure certs are a ripoff by Scareduck · · Score: 2, Insightful

    Secure certs are one of the biggest ripoffs known to man. The sad fact is that they really only prove that money was able to change hands. This is way, way overdue.

    --

    Dog is my co-pilot.

  6. And if you call now...... by aussie_a · · Score: 3, Insightful

    Are steak-knives included in the article? Here's a tip for the AC. Don't make your post sound like a cheap advert. This is a news aggregator (well, it claims to be anyway). Articles should have summaries in a manner that most respected news-sources use. Not like some used car salesman. And if this is off-topic. Sorry, but I'm discussing all that I can, the article summary. The site's down so I can't read the article itself.

  7. Well.. by Anonymous Coward · · Score: 5, Insightful

    Anyone CAN get one! All you have to do is pay X amount of money.

    Besides, do you really trust people such as Verisign to actively control certs?

    1. Re:Well.. by bigberk · · Score: 3, Insightful

      mod this AC up. That is the reality. Anybody can get a certificate... it might take a simple forged document. These companies are about making money, so they will happily sell a certificate.

    2. Re:Well.. by rxmd · · Score: 4, Insightful
      Anyone CAN get one! All you have to do is pay X amount of money.

      Besides, do you really trust people such as Verisign to actively control certs?
      Dead on. After all, Verisign even issued a certificate for a "company" named CLICK YES TO CONTINUE. I don't see how it could get any worse than this with free SSL certificates.
      --
      As a state gets corrupt, its laws multiply; the most corrupt states have the most numerous laws. (Tacitus, Annales 3:27)
  8. Separate by scrotch · · Score: 4, Interesting

    It has always seemed strange to me that encryption via SSL and verification of your business identity were rolled into the same system.

    I've had a few situations where I wanted to encrypt html and had no need of guaranteeing my server's identity to anyone. It seems like I should be able to encrypt traffic without having to jump through hoops and spend a lot of cash. Or without having a second class certificate.

    I hope this new project succeeds.

    1. Re:Separate by pchan- · · Score: 4, Informative

      Any web browser will warn strongly that the certificate is not issued by a trusted organization, but you said you don't need to prove your identity, so this should perfectly suit your needs.

      You do realize that if you can't prove your identity, your clients are vulnerable to man-in-the-middle attacks, right? How's the browser to know if it's your server they're talking to, or to someone else who signed their own cert and is impersonating you (and proxying its transactions to you, logging or modifying them along the way)? Authority signed certificates give you this ability. Self-signed certificates do not provide complete transport-layer security.

      This is not to say that the signing authority can't be free. It's about time someone did it.

    2. Re:Separate by R.Caley · · Score: 2, Insightful
      It has always seemed strange to me that encryption via SSL and verification of your business identity were rolled into the same system.

      If you are worried enough to want encryption, then you should be worried about man in the middle attacks. No point telling people their credit card details or email will be encrypted if it just gets sent to a random criminal who can read it, re-encrypt it and send it on to you.

      If users can verify the identity of the far end point some other way, perhaps because they have previously connected to it, or because they are within a trusted environment, you don't need the signing, or can self-sign. This is how ssh works, you're supposed to check the server ID the first time you use it and then at least simple MITM attacks result in a warning.

      But HTTPS is more about reassuring end users than any significant security concern in most situations, and knowing who they are talking to is part of that.

      [imaginge Dilbert cartoon with credit card, waitress and fur coat here]
      --
      _O_
      .|<
      The named which can be named is not the true named
  9. So? by winterdrake · · Score: 5, Insightful

    Like being able to self-issue a certif is new? Used some random tool that came with MS Office to do it last time I had a use for one, of course that was Office 2K or thereabouts but it's probably still there, and there are probably alot of other ways to self-issue one. The entire point of the big expensive ones is that you have a "trusted" authority validating the transaction.

    1. Re:So? by Anonymous Coward · · Score: 2, Informative

      Straight out of the help file for Office XP

      locate and double-click SelfCert.exe (usually found in the C:\Program Files\Microsoft Office\Office10 folder).

  10. Free.. Free.. FREE! by humankind · · Score: 4, Informative

    Get OpenSSL and roll your own, any time, any platform... always been that way... and this is news? Some script-kiddy-turned-public-relations-director figured this out? Good for j00. As for everyone else, nothing to see here that we don't already know.

    1. Re:Free.. Free.. FREE! by adrianbaugh · · Score: 2, Informative

      Just like what these guys are offering - a certificate, but not a certified one, according to what the article said. You'll get the same warning dialogue from their certificate as from the OpenSSL one, but you can make an OpenSSL one at home.

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
  11. Text of linked article from ... linked article... by Anonymous Coward · · Score: 5, Informative

    Since the linked article is dying, who knows if you'll be able to even get the link to the real article. So here's your text, AC to keep the whoring in Vegas.

    StartCom Free SSL Certificate Project

    StartCom Free SSL Certificate Project The Idea:

    Do you have a website or run even a web server and want to secure the traffic between your visitors browser and the web site? Did you find out, that in order to make your site SSL aware, you'll need a SSL (Secure Sockets Layer) certificate? Are you also surprised to find out that such a certificate can cost you up to a few hundred dollars, valid for one year only? For what, you might ask yourself?

    StartCom Ltd., the vendor and distributor of StartCom Linux Operating Systems, operates also MediaHost(TM), a hosting company specialized in DB and Java web application hosting and offers its clients SSL secured web sites with certificates signed by StartCom Ltd already for years. Here is, where the idea for this project originated: Free SSL certificates!

    How?

    Most web servers, such as Apache, IIS and others are capable of running the 128-bit secured and encrypted SSL protocol. All you need, in most cases, is a SSL certificate to make it work. StartCom is going to provide you with this certificate through a simple web based interface wizard and sign up process free of charge. Together with the installation instructions, you'll have your secured web site running within a few minutes.

    Why?

    Because we believe, that companies like Verisign, Thawte and others, just rip you off your money! Simply as that! Even the so called "Free SSL certificates" offered by some companies aren't free, but can cost you up to a US $ 100 or even more.

    More than that, lets think about, what SSL is supposed to do: Encrypt and secure the traffic between a browser and the server! Point! It is not supposed to give you the impression, that a website is trustworthy or even say anything about its identity...for this you should use your brain and common sence.* Anybody can get a SSL certificate and as such does not give any type of warranty about the intensions, or quality of products, of the website or its owners! We'll prove here, that SSL certificates can cost much less or may be even free of charge! If enough people are using our certificates and stop buying them, well, than the existence of these companies will vanish and we'll all win another piece of freedom!

    * We'll offer in the future, some sort of verified SSL certificates, but on this later...

    Where, when?

    Convinced? We build and tested this web site during February 2005, so you'll be able to get a SSL certificate for free. Use the links below to get your free certificate now! Please spread the word about this project to your friends (by having a link to our web site?). Contact us, if you want to contribute. And....spend your money on better things! There are enough good causes to support!

  12. The problem with free SSL certs... by cortana · · Score: 4, Insightful
    More than that, lets think about, what SSL is supposed to do: Encrypt and secure the traffic between a browser and the server! Point! It is not supposed to give you the impression, that a website is trustworthy or even say anything about its identity...for this you should use your brain and common sence.

    Common sense says, make sure the StartCom CA Certificate is not on any of my machines!

    The entire point of using certificates is so that you know that there is a certified binding between a public key and an identity. If you don't know who will recieve your encrypted information then there's no point encrypting it in the first place!

  13. comodo.com by Neil+Blender · · Score: 5, Informative

    $50 per year per certificate. I've had no problems getting them to work with all browsers. Since I can't read the article, are they giving out real authority certs? Ones that your browser won't pop up the window saying it's untrusted?

    If not, here is a recipe for free signed certificates:
    openssl genrsa -des3 -out server.key 1024
    openssl req -new -key server.key -out server.csr
    openssl genrsa -des3 -out ca.key 1024
    openssl req -new -x509 -days 365 -key ca.key -out ca.crt

    ./sign.sh server.csr

  14. Self signing by Anonymous Coward · · Score: 2, Informative


    you can do it yourself if you want, but the user will be prompted with a scary dialog because your self-signed cert doesnt come built into the browser
    for encryption this doesnt matter but on an ecommerce site transparent http>https is essential, if a user becomes accustomed to warning dialogs they will learn to ignore them (witness activeX spyware installs)

    so signing certs is easy, signing non-prompting certs is why people pay the money

  15. Most tutorials with apache + mod_ssl have had this by Kip+Winger · · Score: 3, Insightful
    Every tutorial I've seen on the internet with apache + mod_ssl has had tutorials on how to generate your own SSL certificate. Most newbies who have followed those step by step tutorials have even done this, since many regular apache tutorials also include mod_ssl as part of it.

    In fact, even mod_ssl has information on how to do so on the site:

    http://www.modssl.org/docs/2.6/ssl_faq.html#ToC27

    --
    - - - - - Fear not the reaper, but my shiny white teeth.
  16. I sometimes worry about these free services. by the+talented+rmg · · Score: 3, Interesting

    It's nice to be able to get free stuff online. I've been known to grab my share of free movies and music from time to time myself, but when it comes to things that are so critical to the security of my servers, I'm a little more careful.

    That is not to say that the particular people in the article are crooked -- I'm sure they're on the level. I'm just saying that as this kind of thing becomes popular, you can be sure some computer hackers out there will try to co-opt the good name of services like these so they can give out compromised certificates and steal information from you and your customers.

    The bottom line is: When it's free, you just never know. A thousand eyes only get you so far. This is why I tend to stick to software backed by a solid corporate history on my own production servers. It's just not worth the risk to skimp on costs when the fact is your entire business is on the line there.

    You just have to know who you're dealing with when you get into this kind of thing. Are you dealing with someone honest or are you dealing with some sort of shady basement operation that moved to Canada to avoid cryptography laws? When mission critical information is at stake, this stuff counts.

    --


    A Proud Member of the Reality Oriented Community.

  17. Woweee by TheVidiot · · Score: 5, Informative


    When you finally get to the site that is offering the certs (http://cert.startcom.org/) all you find is bad grammar and certs that aren't recognized by any browser (i.e. warnings pop up). It's admirable that the site wants to issue free certificates, but you won't find many surfers willing to trust them. Also, you can create your own certs with minimal effort, and you'll end up with the same thing.

    1. Re:Woweee by BokLM · · Score: 2, Insightful

      So to sum up, this article is completly useless. Anyone can do this at home, without them.

  18. Why not just... by imemyself · · Score: 3, Interesting

    Personally I think the government would be well suited to do this sort of thing. Maybe provide them when you get a drivers license or a business license. Its not like it takes massive amounts of money to see if you really are who you say you are. And why the expiration dates(well, of course, they're another way to screw people out of $$, but what's the certificate providers excuse/reason for them?)

    --
    Every time you post an article on Slashdot, I kill a server. Think of the servers!
    1. Re:Why not just... by Fjornir · · Score: 2, Insightful
      And why the expiration dates(well, of course, they're another way to screw people out of $$, but what's the certificate providers excuse/reason for them?)

      Take the obvious Fight Club quote ...over a long enough time line the survival rate for everyone drops to zero... and apply the same logic to the chances of a certificate being compromised: over a long enough time line the chances of a certificate being compromised approach one....

      Good CAs deal with this in two ways: expiration dates and revocation lists. An expiration date protects your customers from getting something which might've been signed three years ago on the sly, and thinking it's a legitimate offering from the company. A revocation list protects your customers by letting them contact the CA's site to see if your certificate is known to have been compromised.

      --
      I want a new world. I think this one is broken.
    2. Re:Why not just... by bigberk · · Score: 2, Insightful

      I agree with this. Ensuring economic reliability for citizens is the government's job, not the private sector's. There is a major conflict of interest when private companies (e.g. Verisign) are making a business out of selling certificates -- i.e. selling trust. Verisign wants your money; what's their motivation to make sure your paperwork is legit? Verisign regularly accepts forged business reg documents, from what I have heard.

      Let the government issue crypto certificates, I say.

    3. Re:Why not just... by starfishsystems · · Score: 2, Insightful
      I agree completely with your reasoning.

      As you imply, various levels of government are already responsible for issuing the various forms of primary identification which will subsequently be used, by third parties, to sign your certificates.

      It makes perfect sense to issue a companion certificate to each of these primary forms of identification. There are good reasons for expiring many forms of identity, and certificates are no different in this regard. Just make the expiry date of the certificate correspond to the expiry date of the identity document or license. The authority and all of the related procedural infrastructure is already in place. So how hard could it be?

      By the way, Canada Post was registered a few years ago as a Certificate Authority, but no longer. I'd be interested in knowing the politics behind its disappearance.

      --
      Parity: What to do when the weekend comes.
  19. In theory maybe by Chuck+Chunder · · Score: 5, Informative

    In practice the ID checks that I've seen done are fairly flimsy. And with "hundreds" of dollars being charged by big name certifying authorites there is strong motivation for them to just give you the cert (and take your money) once you've faxed them a couple of vaguely official looking signed bits of paper.

    Anyone paying "hundreds" of bucks for a certificate is being scammed though. Much cheaper ones are available from people like GoDaddy. I can't see why anyone wouldn't just go for the $29 one, your users won't notice any difference between them unless they are particularly inquisitive and enjoy poking around obscure browser dialogues.

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
    1. Re:In theory maybe by tetranitrate · · Score: 2, Funny

      Much cheaper ones are available from people like GoDaddy.

      Thanks for the mental image.

    2. Re:In theory maybe by mlyle · · Score: 2, Informative

      A wildcard certificate still costs $449 at InstantSSL. Read the parent's post more carefully mmkay? thx.

    3. Re:In theory maybe by Anonymous Coward · · Score: 2, Informative

      Perhaps even more appropriate (since we are talking about godaddy anyways) is the fact that godaddy is providing FREE (as in beer) ssl certificates to FREE (as in speech) projects...

      https://www.godaddy.com/gdshop/ssl/ssl_opensource. asp

    4. Re:In theory maybe by XorNand · · Score: 2

      As another poster already mentioned, their wildcart certs aren't $50, but I too will vouch for InstantSSL. But it's also much easier to get a cert from them than it is Verisign. (I haven't used Verisign in years, so myabe they've changed, but it used to be a PITA to get cert). To that end, I place more value in Verisign certs: Their certs cost more, in part, because they are in fact more secure. As much as a I detest that company, they would be smart to market this aspect of their product.

      --
      Entrepreneur : (noun), French for "unemployed"
    5. Re:In theory maybe by just_von · · Score: 2, Informative

      We had to do more than just fax documents. They actually called the phone number we gave them, and there were code numbers involved. :)

    6. Re:In theory maybe by xWakawaka · · Score: 5, Informative

      Speaking of theory... let's clarify how this works.

      Generating a certificate/key-pair is trivial. You can do it yourself for free or have a 3rd party do it free or at mild to great expense.

      In theory, a certificate is only useful in verifying the identity of a resource (server authentication of a web server in this case) so long as you trust the issuing authority, and therefore you take it on the issuing authority's word (cert is signed with the authority's private key) that the server at the end of https://companyA.com really belongs to companyA. You trust the issuing authority to have verified this fact for you. That's all server authentication consists of.

      In theory, then, the critical question is 'what certificate authorities do you trust to make that kind of verification on your behalf?'

      In general practice, however, all this boils down to is 'what certificate authorities are shipped as "trusted" on an out of the box install of the dominant platform/browser?' This, of course, includes Verisign, Thawte, and serveral others that have gone through both a PKI practices certification process and what must surely be an expensive business relationship with Microsoft.

      So, as a server administrator, you either pay up for a cert from one of these widely "trusted" authorities, or explain to your users wy they should either import your CA as a trusted root, or otherwise deal with the warning messages that the browser will issue if your cert comes from anyone "untrusted", including yourself.

      And, as has been alluded to, one you are past the server authentication usage of the PKI, the session key exchange for bulk encryption (SSL) can be handled equally well by any technically correct certificate/key-pair, regardless of the trust chain.

    7. Re:In theory maybe by CmdrWass · · Score: 2, Informative

      I'm glad somebody said this. Oooh wow! Free Certificates... I'll give anybody all the free certificates they want... as you pointed out... while it is true that the certificate is required for Apache's SSL to work, all it is used for is to validate identity. If a person's only concern is encryption, just create your own certificate. It isn't hard.

      Sometimes I wonder about this "technical community" I'm forced to be a part of.

    8. Re:In theory maybe by Poverty+P'uh · · Score: 2, Insightful

      How is one cert more secure than another? Does VeriSign use magic bits that are harder to crack?

      --
      "Never underestimate the power of stupid people in large groups."
    9. Re:In theory maybe by nacturation · · Score: 3, Interesting

      I'm a reseller for InstantSSL. If you purchase credits on their system and act as a reseller (not just an affiliate), you get certificate requests coming to you. All you do is go online, approve the request, and it's issued. Customers have done this and apparently they don't go through any extra screening, even for a code signing cert.

      Anyone have a different experience?

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  20. Maybe they should have written about... by turnstyle · · Score: 3, Funny

    hmm, it seems maybe they should have written about MySQL Connections... ;)

    --
    Here's what I do: Bitty Browser & Andromeda
    1. Re:Maybe they should have written about... by lakerdonald · · Score: 2, Funny

      "Secure" MySQL connections of course.

  21. Re:If you want a "real" one by jonfelder · · Score: 5, Informative

    Didn't these people buy SCO linux licenses? Why on earth would I give them money?

  22. Why shouldn't certification be free? by Mr.+Underbridge · · Score: 4, Interesting
    I thought the whole point of SSL is that not just anyone could get a cert...

    Having an internet presence is critical to running a successful business venture. Also, the creation of a truly international digital economy necessitates the development of a trusted method of identity establishment. Especially in these days of questionable computer security and the impossibility of ascertaining identity from IP. Reliable certification is vital to the development of the internet economy.

    However, the centralization of certification among a few organizations and their cost is shutting out smaller enterprises that don't have access to the fees or technology required. In effect, this institutes a kind of "information segregation" or isolationism that has the effect of a barrier to poorer nations - such as Nigeria or Rwanda - to the internet commerce that is so critical to the economy of the future.

    As such, I believe the best scenario is free certification provided by ICANN that can certify pages from poorer nations, so they can compete on an even playing field with the wealthier nations. Giving out free certifications - one per IP address at least - is the best way to accomplish this, and will allow for confident and secure transmission of funds and information.

    1. Re:Why shouldn't certification be free? by lukewarmfusion · · Score: 5, Insightful

      1. Getting an SSL certificate can require that you fax a copy of your articles of incorporation, public contact information, etc. Someone ends up doing some legwork to ensure that you are who you say you are and that you can be tracked down in the event that there is a complaint.

      2. Virtual hosts often share a single IP among many websites. You can't just authorize a name; SSL requires (from my understanding) a unique IP. That would make the IPv4 system even more strained.

      3. Certification pricing is partly based on trust. Anyone can generate a free certificate. But it won't work with every system because it wasn't created by a "trusted provider."

      If you can't afford a $200US/year fee for conducting "secure" business online, I probably wouldn't want to do business with you anyway.

    2. Re:Why shouldn't certification be free? by lordkuri · · Score: 2, Informative

      $200 a year my ass...

      $35/year, 99% installed browser base

    3. Re:Why shouldn't certification be free? by bigberk · · Score: 3, Funny
      Having an internet presence is critical to running a successful business venture...creation of a truly international digital economy necessitates the development... Especially in these days of questionable computer security and the impossibility of ascertaining...
      Dude, wash your mouth out with soap, the marketing speak is vile.
    4. Re:Why shouldn't certification be free? by XorNand · · Score: 4, Informative
      2. Virtual hosts often share a single IP among many websites. You can't just authorize a name; SSL requires (from my understanding) a unique IP. That would make the IPv4 system even more strained.
      SSL doesn't require a unique IP. The problem is that you can't use SSL with host headers, which is the trick that allows multiple websites to resolve to the same IP. Normally HTTP just serves back whatever content is on port 80 when a browser requests a connection. With HTTP/1.1 host headers were introduced which allowed the client to request a specfic hostname at that IP addresses, in effect allowing you to run multiple domains on a single IP address. This is was is incompatible with SSL.
      --
      Entrepreneur : (noun), French for "unemployed"
    5. Re:Why shouldn't certification be free? by ip_fired · · Score: 4, Informative

      2. Virtual hosts often share a single IP among many websites. You can't just authorize a name; SSL requires (from my understanding) a unique IP. That would make the IPv4 system even more strained.

      This is the case if you want to use the default HTTPS port (443) since the hostname is encrypted. However, you can use your certificate on other ports. Just have your webserver listen to port 4443, and then in your links, just put https://yourhost.com:4443/ and it works great.

      When I was running a small webhost business, instead of getting a new IP for each cert, I'd just put them on different ports.

      Also, the IPv4 system isn't as strained as it used to be. With NAT, and creative netmasks, they have been able to spread out the IPs more efficiently. I wish it *were* more strained, because then they might be forced to actually switch over to IPv6.

      --
      Don't count your messages before they ACK.
    6. Re:Why shouldn't certification be free? by ckaminski · · Score: 2, Interesting

      Which is why I think the post office should get into the SSL cert business.

    7. Re:Why shouldn't certification be free? by Sentry21 · · Score: 2, Interesting

      I work as a sysadmin for an unnamed credit-card processor, and when I first interviewed for the job, one of the things my boss mentioned is that people will look for the Verisign logo. Yes, the same people that don't see the 'Help' link right in front of their faces get antsy if the processing website (i.e. us) doesn't have a verisign logo, regardless of whether the connection is encrypted or not (and it is - even going to our homepage redirects to an HTTPS URL, we encrypt everything).

    8. Re:Why shouldn't certification be free? by Leebert · · Score: 2, Informative

      True, but seeing :8443, :8444, :8080, :8081, etc looks a bit un-professional.

      Yes, and you also run into those of us who do heavy egress filtering.

    9. Re:Why shouldn't certification be free? by RupW · · Score: 2, Insightful

      This is the case if you want to use the default HTTPS port (443) since the hostname is encrypted.

      More to the point, the certificate exchange identifying the server happens before you ever get to send the HTTP headers. You can only serve one SSL certificate on each port.

      The protocol could be extended to support this, e.g.:

      Client: connect SSL
      Server: hi, I'm www.site1.com
      Client: OK, that cert checks out, but I wanted www.site2.com
      Server: OK, here's the www.site2.com cert
      Client: OK

      but it doesn't currently.

    10. Re:Why shouldn't certification be free? by TheRaven64 · · Score: 2, Interesting
      The UK post office had plans a few years back to issue everyone in the UK with a digital signature. Not sure what happened to that idea.

      I would rather see encryption integrated into the DNS network. The root DNS servers are already trusted - their IP addresses are distributed with any DNS cache software. It wouldn't be too hard to also distribute their public key. Each DNS lookup could then request a signature as well as an address. Every time authority was delegated to another server, the SOA record and the delegated server's public key would have an accompanying signature, ensuring that the delegated server was returning valid information. Once the final record was returned, the returning server could also request a public key from that DNS and use that for communicating with the server. Since the signatures are static, they could be cached by DNS caches resulting in very little strain on the system. 99% of SSL certificates are used to verify that the remote machine is actually the machine it claims to be, not that it is owned by the company that claims to own it, so this would be a reasonable solution, and would not cost more than a domain registration.

      I believe DNSSEC works something like this, but I've not actually looked at it.

      --
      I am TheRaven on Soylent News
    11. Re:Why shouldn't certification be free? by mwood · · Score: 2, Interesting

      Actually I think that the banks ought to go into the cert. business, at least for their depositors, and demand client cert.s when establishing secure sessions for online banking. They have an interest in establishing identity and keeping things secure.

  23. Ummmm... Why??? by James+Wells · · Score: 4, Informative

    cacert.org is doing everything these guys are, and then some. cacert.org is free, but with a much higher level of personal confidence than Verisign, Thawt, or any others that I know of.
    Additionally, with cacert.org, you are able to get more than just server certs and keys.

    --
    "Individuals are smart, people are stupid" -- Tommy Lee Jones as "K" from Men In Black
  24. WTF?? by fatboy · · Score: 2

    Did you find out, that in order to make your site SSL aware, you'll need a SSL (Secure Sockets Layer) certificate?

    WTF is "SSL aware"?

    I have had no problem creating and using self signed certs with SSL.

    --
    --fatboy
  25. Re:If you want a "real" one by codepunk · · Score: 3, Insightful

    Oh and he was protecting his customers by parading around to the press with his lips attached to Daryl's buttocks right? You do remember him traveling around with Daryl spewing their BS to everyone right? Give me a frigging break I won't buy crap from them, I also refuse to help anyone hosting stuff on their servers.

    --


    Got Code?
  26. This is just plain stupid by galvanash · · Score: 4, Insightful

    Think about this for a minute... The purpose of SSL is not to secure data during transport, it is to secure data during transport AND to verify to the sender that the reciever is who they claim to be.

    Without identity verification there is NO POINT in encryption for most usages.

    The point is to make the person who is submitting their credit card number resonably secure in the knowledge that they are sending it to who they think they are. This cannot happen without identity verification.

    --
    - sigs are stupid
  27. Re:Well.... [OT] by FalconZero · · Score: 4, Interesting

    I'm using it as (loosly) 'reboot'
    So thats rougly:
    Windows in 6 Bytes (IA-32): Do nothing then reboot.

    --
    Windows in 6 Bytes (IA-32) : 90 90 90 90 CD 19
  28. Re:Price on certs are for the reason ... by WolfWithoutAClause · · Score: 2, Interesting

    And have these insurers ever actually paid out? If not, then what's the point? If yes, how come there's no relation between what they charge to get a certificate and the value of the transaction?

    --

    -WolfWithoutAClause

    "Gravity is only a theory, not a fact!"
  29. Blatant ignorance by QuantumG · · Score: 5, Interesting

    Does anyone even know what a man in the middle attack is anymore? Without certificates (or with easy to aquire certificates) we don't have a way to ensure that someone isn't spying on the encrypted traffic. This service will allow me to register a certificate that looks "just like" the one you expect to get from www.usemycreditcard.com and intercept your confidential details by presenting a key signed with that certificate to your browser. This is already happening with Verisign certificates, a case of them not doing their job, and now StartCom want to make it easier? I guess it doesn't really matter as the vast majority of people are too damn stupid to examine a certificate to ensure it is correct anyways.

    --
    How we know is more important than what we know.
  30. Re:Well.... [OT] by bendelo · · Score: 2, Funny

    Ahhh yes, not the preferred method of rebooting =D

  31. Re:If you want a "real" one by jonfelder · · Score: 2, Insightful

    They should've told SCO to stuff it. Their money (ev1's) went to help SCO perpetuate this crap on others. By extension, so did their customers' money. I know if I were an ev1 customer I would've gone balistic and dropped them immediately. I imagine many people did. If everyone stands up to SCO, what they going to do?

    I'm not so certain I believe their excuse that they were protecting customers. Let the customers decide if they want to purchase SCO licenses. EV1 has the resources to fight and that's what they should've done.

    I certainly see no reason to give them more money. I'd choose a different SSL provider that is not verisign (they suck too) that didn't give money to SCO, even if that provider cost more.

  32. breaking the monopoly on certs by wayne · · Score: 3, Informative
    Ok, I've seen lots of posts from people saying that certs are a rip off. Getting a cert from someone means that they trust you enough to accept money from you, and that is about it.

    I've also seen a lots of posts from people saying that you can generate a self-signed cert for free. The problem with these self-signed certs is that you get a pop-up from your browser warning you that the cert isn't trusted.

    It appears to me that cert.startcom.org is trying to do something different: They are handing out certs with them as the root authority and giving information about how to install their cert as acceptable by your browser. If enough people do this, then major browsers will "have" to start including startcom.org's certs in their distributions. Until that happens, you still get a reduced number of cert pop-ups because many different websites will be using the same "non standard" cert authority.

    You will get all the cheapness of self-signed certs with all the security of a cert from verislime or thawte. After all, the only real security with regular certs is that the traffic between your broswer and the website is encryptied.

    --
    SPF support for most open source mail servers can be found at libspf2.
    1. Re:breaking the monopoly on certs by js3 · · Score: 2, Insightful

      yes but unless your clients install their root certs they will still get the pop cert warning. Installing their root cert as trusted also compromises you since you have no idea what kind of unscrupulos people they are giving certs to. The trust is not in the certificate, but who is signing the certificate. If I trust verisign, then I trust anyone verisign trusts. Do you trust anyone startcom.org trusts?

      --
      did you forget to take your meds?
  33. Re:The problem with all SSL certs... by Beryllium+Sphere(tm) · · Score: 4, Informative
    The entire point of using certificates is so that you know that there is a certified binding between a public key and an identity. If you don't know who will recieve your encrypted information then there's no point encrypting it in the first place!
    Yes, the cheapest and easiest attack against a public-key crypto system is to trick someone into encrypting to the wrong public key. That is the problem that certificates are supposed to solve. Nor is it just a theoretical problem, because already one "Internet marketing" company has been intercepting SSL transactions.

    For a (partial) list of the design and implementation problems that interfere with certificates actually solving the problem, check out Peter Gutman's scathing critique of X.509-based PKI.

  34. It's about trust by js3 · · Score: 3, Informative

    Anyone can make a certificate, hell you can make one yourself. The whole point of a issuing certificates is about delegating trust. Verisign, Thawte, etc are trusted. Some company that gives it out for free without any sort of checking is not.

    --
    did you forget to take your meds?
    1. Re:It's about trust by Sloppy · · Score: 3, Interesting
      Verisign, Thawte, etc are trusted. Some company that gives it out for free without any sort of checking is not.
      The catch is that they aren't really trusted, or more importantly, trustable. What do you know about Verisign's internal security procedures? Do you have any idea how well they check people's ids? How many people have access to their signing key?

      Unless you work there, Verisign is just a faceless enigma. You know more about your father's brother's nephew's cousin's former roommate, than you know about Verisign.

      If a cert is signed only by Verisign (and the nature of X.509 certs is that they only have one CA) then you have to decide to either trust it completely, or trust it not at all. And if, like 99.999999% of the population, you simply have no clue as to whether or not Verisign can be trusted, best practices are to assume the worst, and the certs are effectively meaningless, whether they are signed by Verisign or by some kid in his basement.

      As it turns out, there's a better way: PGP. PGP uids can be signed by multiple entities, so if you have a clue about some signers and no clue about others, you can throw out the info that means nothing to you, and still take advantage of the info which has meaning. And even for the signatures that you're uncertain about, if you're willing to quantify how uncertain you are, then you can multiply uncertainties, based on the idea that conspiracies are hard to pull off.

      The only problem with PGP, is that use of it in concert with secure connections, hasn't really caught on. But surprisingly, the idea isn't unheard of or completely dead, either. If people ever start to take internet security really seriously, there are projects like GnuTLS. It's a long way off from the mainstream, but just about everything we take for granted these days, was like that at one time. :-)

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    2. Re:It's about trust by storem · · Score: 2, Interesting

      Thawte and CAcert have a Web Of Trust (WOT) to deal with the trust issue. I'm a notary myself for both Thawte and CAcert and an ID of a person is not trsuted until mutiple! notaries have physically verified a person with photo ID. I take my notary job very seriously, and I think all notaries do.

    3. Re:It's about trust by jrumney · · Score: 4, Interesting
      The catch is that they aren't really trusted, or more importantly, trustable. What do you know about Verisign's internal security procedures?

      CA's are supposed to make their issuing policies publically available. One day a few years ago when I had too much time on my hands I went through and checked them all. Of the 100 odd root certificates that were originally installed in my browser, I threw out about half for not having their policy publically available in human readable form. I threw out most of the rest (including Verisign and Thawte's low-end certs) because their policy was too lax, but maybe I just have high standards.

  35. Free SSL Certificates by sp3d2orbit · · Score: 2, Informative

    Warning: Too many connections in /var/www/pnadodb/drivers/adodb-mysql.inc.php on line 108

    Really great article...

    Go Daddy.com recently annouced they were offering free SSL certificates for Open Source Projects:

    Go Daddy.com

  36. DomainKeys by Anonymous Coward · · Score: 5, Interesting
    I liked the idea behind Domain Keys:
    Domain Keys

    You post your public key in your DNS record. DNS already maintains an identity system.

    The trick with DK is to get the browser's to fetch the site's public key from the DNS record (it has to do the DNS query anyway) and use that in the handshaking.

    Yes, there is the potential for someone to hijack the site, but that is getting more difficult. And, DK would be a free add-on to the DNS stuff you have to do anyway.

  37. Re:How do you figure? by enosys · · Score: 2, Informative
    Sure, people don't usually click the padlock but they might notice a warning saying that the certificate doesn't come from a recognized authority or that it doesn't match the name of the site.

    The problem happens if a "trusted" authority issues certificates for sites like these. Then people go to to the site, think everything is okay, and securely give out information to the phishers. This is why automatically trusting these free certs is stupid and why you might as well just make your own certificate.

  38. Re:Well.... [OT] by jeffy210 · · Score: 4, Funny

    Reminds me of one time back in HS. We didn't like our CS teacher and for our final project in C every student put a call to INT 19 at the end of their code, so when she was through running and grading our program it'd reset her computer. I don't think she ever figured it out.

    --
    ------
    "And may your days be long upon the earth."
  39. Re:nice ... but to be useful by bigberk · · Score: 2, Insightful
    [Verisign] Why there's a charge like that I don't know, but yet we give into them because "they're trusted".
    Verisign sells trust. If someone came to me with a $1000 bill in their hand, and asked me "do you trust me?" I'd be pretty tempted to just stamp them TRUSTED and take the cash. That's a fundamental problem. I think only the government or government supported nonprofit organization can be an ideal certificate authority.
  40. GoDaddy will give you a *real* free SSL cert... by bigtangringo · · Score: 5, Informative

    ...If you are doing it for an OpenSource project:
    https://www.godaddy.com/gdshop/ssl/ssl_o pensource. asp

    Not to mention, it's the cheapest SSL cert I know of at $30/year.

    --
    Yes, I am a smart ass; it's better than the alternative.
  41. Re:but it prompts the user by Ice+Station+Zebra · · Score: 3, Interesting

    You don't get it. It is like the Linux vs Windows battle. If everyone starts using cacert and the free browsers (firefox,safari,opera,konqurer) include it as a trusted CA then those prompts GO AWAY. Suddenly the SSL cert market doesn't look so good, prices drop.

    I think cacert has a very good program. You want a real cert then someone local has to verify your ID. It takes the money out and puts the trust back into SSL.

  42. Do we really want free SSL certificates? by freelock · · Score: 3, Insightful

    Many fine, relevant comments have already been made in this thread. But I didn't see anyone point out the downside of free SSL certificates: free phishing sites!

    Yes, it's possible to freely self-sign certificates to get encryption. I run my own certificate authority for encrypting traffic among my clients, if they aren't conducting e-commerce. These self-signed certificates work fine without triggering a browser warning--if you import the certificate authority certificate.

    For my public/e-commerce sites, I use FreeSSL, at $35/year. This buys me a blessing from a CA that is pre-installed in over 95% of all browsers in use. What's not covered? Konqueror. Curl. I think Safari, though I haven't checked recently. For my clients who want those to work, I suggest spending the ~$120 or so for a Geotrust cert.

    Now, imagine if every spammer in the world could get an SSL certificate for free... Already domains are cheap enough that they can set them up to easily spoof real web sites--banks, etc. Imagine if every one of those had an SSL certificate, and didn't trigger a browser warning? Most people I know look for the lock. If the lock is there, they trust the site. They don't actually look at the certificate, or even the URL much.

    For this reason alone, I'm glad certs aren't free. You can do encryption for free, but I'd prefer my browser to at least let me know the site I'm visiting is too cheap to buy a real cert. (that's not meant as a slam, since I'm too cheap to buy one for most of my sites...).

    Cheers,
    Freelock Computing

    --
    Open Source Solutions for Small Business Problems
    Freelock Computing
  43. "Certified" by kg4gyt · · Score: 2, Insightful

    You can create your own SSL Certificate, however whoever visits your server must chose to accept it. Just because it isn't "Certified" doesn't mean that your site is insecure.

  44. "much better" - pfft. by Chuck+Chunder · · Score: 2, Informative

    The GoDaddy certs are compatible with pretty much every browser in use today....

    Internet Explorer 5.01 and higher
    AOL 5 and higher
    Netscape 4.7 and higher
    Opera 7.5 and higher.
    Safari on Mac OS X 10.3.4 or higher
    Mozilla (all versions)
    Firefox (all versions)

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  45. Try that in Oracle, with their Jinitiator by papaia · · Score: 2, Interesting

    Are people really so childish to believe that there is no relationship between big software manufacturers, and the big profit-producing cert authorities? Try to use even a mid-tier (I am not even getting to the free ones) authority, like Thawte, and let me know if you will ever get the Jinitiator client in Oracle 9i working, without manually redistibuting a new cert file to all clients ... what you end up doing is paying Verisign a few more thousands, for all the servers, to avoid paying the admins tens of thousands, to customize clients, distributions and updates ...

    --
    == With enough Will Power, one could move mountains. With enough Brains, one would just leave them where they are ==
  46. SSL Certificates can be had quite a bit cheaper by ddent · · Score: 3, Informative

    We issue SSL Certificates with prices a good deal less than hundreds upon hundreds of dollars. Our certificates are issued with a root that already exists in browsers, and we do ID verification (but remain flexible - we will issue certificates to both corporations and natural persons, i.e. people). In terms of keeping the encryption meaningful, using a self-signed certificate doesn't cut it - it makes it trivial for the right person to perform a man-in-the-middle attack.

    As much as I'd love to say otherwise, the SSL business is actually quite competitive these days -- the days of a 128-bit certificate costing at least $895 are long gone.

  47. The Meaning Of All This For Mere Mortals... by smug_lisp_weenie · · Score: 5, Informative

    Let's suppose you take your PC to a coffee shop and want to read your stock-r-us.com stock portfolio...

    ...even though there are already PLENTY of free certificate providers out there today, stocks-r-us has to pay big big bucks to one of a few certificate agencies- There's absolutely, positively, no way around this currently, for complex reasons that are hard to explain briefly, but I'll give it a shot...

    First of all, there are two things, at the minimum, you need to talk to stocks-r-us over the internet securely from a coffee shop:

    1. An encrypted communication channel (this is handled by public key and symmetric key encryption protocols)
    2. A guarantee that the person you are talking to over the 'net really is stocks-r-us and not an impostor.

    All this fancy talk in this slashdot story involves this second step in this process... so how can you get this no-impostor guarantee? Well, the most basic way would be to ask stocks-r-us a secret question only they could answer, sort of like a "secret handshake". An SSL certificate is simply a "secret handshake". (well, not so simply, but just accept this idea for now...) So in order to make sure the company you're talking to over the 'net is your stocks-r-us, you check to see if they know the stocks-r-us secret handshake. Problem solved...

    ...or not: This works fine if YOU know how to recognize the stocks-r-us secret handshake, but, for technical reasons, this is only possible if your computer and stocks-r-us have chatted in the past (i.e. you've used your computer before to sheck your stocks) if not, there's no way you can get the jimmy on how to tell a genuine stocks-r-us secret handshake.

    This is where a certificate authority comes in: You can get a third person (whose handshake you do know) to give you stocks-r-us' secret handshake. There are many many organizations that offer free (or not free) services to act as this third person (i.e. as a "CA") So stocks-r-us can just sign up with one of these companies to give them the secret handshake info- Problem solved...

    ...or not: The user of their has to already know the handshake of the CA for this to work ahead of time, or the proverbial "house of cards" will just fall apart anyway... How can they be sure you already have the "secret hanshake" of this third person/CA?

    Well, the answer is pretty goofy... the "handshake" of the CA has to be "hardwired" into every copy of Firefox/Internetexplorer/Safari/etc when it is installed. If you go to the settings of your browser, you'll see a list of CAs already placed in by Microsoft/Apple/Mozilla/etc right out of the box! That's the only way this could work...

    ...so you might be wondering: Don't the CA companies in this initial list of built-in handshakes have some kind of monopoly/oligopoly? The answer, of course, is YES: These special CAs charge monopoly-style prices for their services for this very reason. The point of this slashdot article is that an non-profit group wants to somehow make Microsoft/Apple/Mozilla/etc to put it in this super-duper "handshake" list, but it promises it won't charge everyone big bucks who wants to use them as their third party.

    (I'm no expert on this, so any experts are welcome to reply to my post to make any corrections if there are any errors of substance...)

    1. Re:The Meaning Of All This For Mere Mortals... by DarkRecluse · · Score: 2, Funny

      I don't know, but if I walk into a retail store and the salesperson expects me to complete "the secret handshake" I think I will either call the cops, or wait for the store's walls to fold up around me and be quickly loaded into a black van.

      --
      --"It's Bradford Company, slash your last name, dot your first name"
  48. Issuing authorities by initialE · · Score: 2, Informative

    Speaking on behalf of a company forced to purchase a certificate from a recognized issuing authority, I can say that the main issue involved was the need to have the certificate automatically trusted w/o needing to install additional trusted roots. Sure, in a windows domain we can deploy our own root to our clients, but we were looking at problems outside our organization.
    1) Exchange RPC over HTTPS - outlook 2003 does have this support, but it won't work if it does not trust the certificate of the server. And if you don't have admin rights, you can't add that trust. Specifically, RPC over HTTP was designed for use outside of the organization, so it does make things harder if you need admin access over a box in a partners organization (it's either that or use OWA, which we all hate in general).
    2) Mobile devices and Handhelds. Windows isn't the only system that comes preconfigured with certain trusted root authorities. Mobile devices are a pain in that some of them can't even be configured with additional trusted roots.
    3) We experience a significant slowdown when we require our users to temporarily accept certificates for a web session. I'm not sure why myself, actually.
    In the end, we just bit the bullet and bought ourselves one from Entrust.

    --
    Starbucks, Harbuckle of Breath.
  49. Re:Man in the Middle Attack only works first time by asdfghjklqwertyuiop · · Score: 2, Insightful

    The whole point of certificates is to associate other pieces of information with a private key, like a legal name, an official company name, an address and location, the domain name... the CA isn't just supposed to sign certs that associates those types of information at random, they're supposed to make sure that the information in the certificate they sign reflects the actual entity which holds the private key. Well that's what a CA is supposed to do in theory at least....

    If the CA is just signing everything that gets sent to them or simply not including enough identifying information as in your idea then there is no point in the CA's existance... I can't use the certificates they sign to help get an idea of who I'm talking to...

  50. The 1 place government is useful and..... by AKosygin · · Score: 2, Insightful

    they do nothing. For once, if the government had a CA authority and actually issue SSLs to companies that are registered with them, it would help. When you register for DBA (Doing Business As) or file articles of incorporation, they should be the ones to issue the certificates as they are the most qualified to judge authenticity and do ID checks. Isn't that the reason why we file these things with the government and NOT Verisign?

    This is the one place the government DOES need to be a part of, and yet they do not. Government in all the wrong places.... go figures.

    Or when people WANT to be verified online, then the government should be the ones issuing the certificates. When a person say they are Joe Smith, which type of ID do you believe more? An ID issued by some company or a government issued driver's license/ID?

    The government actually should have a Certification Authority freely (or some nominal fee) available to its citizens.

    See, proper government involvement: http://www.hongkongpost.gov.hk/product/ecert/type/ personal/index.html

  51. Re:I Need Help with Free SSL Cert -- by pe1chl · · Score: 2, Informative

    SSL is not working with shared hosting.
    You need a dedicated server with a separate IP address to realistically use SSL.

    Why? With shared hosting, the virtual host is selected based on the Host: header of the HTTP request. But the request is sent over the SSL connection!
    So the sequence is:
    1. establish secure connection based on certificate (which is attached to sitename)
    2. send request over secure connection

    But in shared hosting the situation is:
    1. connect to shared host
    2. decide which site to serve based on hostname sent with request

    Unfortunately, those two sequences are conflicting.

  52. This is old news on this side of the pond by Dasch · · Score: 2, Interesting

    We've had free certificates (OCES, SSL, whatever) here in Denmark for years. It's a project initiated by the government and the largest telecom here, TDC.

    We can even use it to pay our taxes! Yay!

  53. Certificate generation by mikrorechner · · Score: 2, Interesting

    According to this article on heise.de, StartCom generates the SSL certificate you order on their server, sign it, and send it to you.

    How do I know that they don't keep a copy of the cert for their own use? They could impersonate my server any time with this.

    --
    "Oh, a lesson in not changing history from Mr I'm-my-own-Grandpa." - Dr Hubert Farnsworth
  54. Re:Yes, but is their root known? by The+Cisco+Kid · · Score: 3, Informative

    To answer my own post, after reading thru their site, it apepars that no, they are an unknown root. Chicken-and-egg. Until they get their CA auth in the major browsers, no one will be able to use certs from them for anything the public will be accessing. And until lots of people are using them, they wont be able to get in the browsers.

    Also, they don't seem to permit you to provide your own CSR, which as someone else noted somewhat vaguley, is a MAJOR security problem. A cert signer should *never* have access to your private key - you make the key on your system, use it to make a CSR, then they sign the CSR. The resulting signed cert is only then usable if you have both it and the private key.

  55. What nobody realizes is this by CastrTroy · · Score: 2, Insightful

    What nobody realizes is that certificates only actually solve a very small problem. They prove that a person is who they say they are. It's like picking up a hitchhiker because they've shown you their driver's license. The fact that they can prove who the are says nothing about the safety of actually letting the person into your car. Certificates provide a false sense of security, but making people think it's ok to install such-and-such active-x control, because it's signed. It doesn't matter if you can track down the person who created it once your data is all gone. Tracking the person down isn't going to get your data back.

    --

    Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.