Happy New Year! Forget all that stuff about the Mayan Calendar. Be Cool!

Latest Reviews & Tutorials

  • How to customize Linux Mint 12 KDE
  • Linux Mint 12 KDE review
  • GhostBSD 2.5 review
  • How to install Takeoff Launcher on Fedora 16 KDE
  • Install Quick Access on Linux Mint 12 KDE or any KDE installation
  • How to install Linux Mint 12 KDE on a btrfs file system
  • Manual disk partitioning guide for Linux Mint 12 KDE
  • How to compile and install Takeoff Launcher on Linux Mint 12 KDE
  • 3 must-have extensions for Fedora 16 and other GNOME 3 installations
  • How to install Razor-qt on Linux Mint 12 KDE
  • How to enable desktop slideshow on Linux Mint 12 KDE
  • KahelOS 111111 review
  • How to install Cinnamon in Ubuntu 11.10
  • How to customize Cinnamon on Fedora 16 and Linux Mint 12
  • How to install Cinnamon on Fedora 16
  • What does Cinnamon bring to the desktop?
  • How to access Microsoft Windows files and folders from Linux
  • How to dual-boot Pear OS Panther 3 and Windows 7
  • How to dual-boot Chakra Linux Edn and Windows 7, part 1
  • Linpus Lite Desktop 1.6 review

Mozilla Debates Whether to Trust Chinese CA


FirefoxSometimes geeky technical details matter only to engineers. But sometimes a seemingly arcane technical decision exposes deep social or political divisions. A classic example is being debated within the Mozilla project now, as designers decide whether the Mozilla Firefox browser should trust a Chinese certification authority by default.

Here’s the technical background: When you browse to a secure website (typically at a URL starting with “https:”), your browser takes two special security precautions: it sets up a private, encrypted “channel” to the server, and it authenticates the server’s identity. The second step, authentication, is necessary because a secure channel is useless if you don’t know who is on the other end. Without authentication, you might be talking to an impostor.

Suppose you’re connecting to https://mail.google.com, to pick up your Gmail. To authenticate itself to you, the server will (1) do some fancy math to prove to you that it knows a certain encryption key, and (2) present you with a digital certificate (or “cert”) attesting that only Google knows that encryption key. The cert is created by a Certification Authority (“CA”), which asserts that it has done the necessary due diligence to establish that the designated encryption key is known only to Google Inc.

If the CA is competent and honest, then you can rely on the cert, and your connection will be secure. But a dishonest CA can trick you into talking to an impostor site, so you need to be cautious about which CAs you trust. Your browser comes preinstalled with a list of CAs whom it will trust. In principle you can change this list, but almost nobody does. So browser vendors effectively decide which CAs their users will trust. Continue reading.

0saves
To have articles like this delivered automatically to your Feed Reader or Inbox, subscribe via RSS or email. For simple comments, use the commenting system, but for more involved assistance, please use the Question & Answer section.

Posts From The Same Category:




Questions & Answers Hola! Looking for an answer to a question but did not find it? Then surf on over to the Questions & Answers section. It's a brand new addition to our site, and we are waiting just to answer your question(s).

Leave a Reply

Trackbacks

Read previous post:
PC-BSD’s graphical firewall manager
Google Buzz Privacy Update
Digital Books and Your Rights: A Checklist for Readers
Close