CRLs are revocation lists which used to be published by CAs and clients were able to periodically download.

As a concept they were replaced with OCSP (online certificate status protocol). Here the client requests the current status of a certificate each time they are presented with it. The idea was that it would be more timely and up to date and meant CAs didn't need to publish a complete list of revoked certificates.

Now it seems Chrome wants to go back to a bodged version of the old way of doing things where Chrome periodically requests the CRL from the browser vendor or Chrome is periodically updated with the latest CRL?

The CAs never see the private key material. When you apply for a certificate, you generate the private key and a certificate signing request (CSR). It's the CSR which gets sent to the CA to sign, not the private key. All the CA has a copy of is the CSR and certificate, which is public knowledge anyway.

One of Dilbert creator Scott Adam's books covers market segmentation. The market segment every business should aim for is the "stupid rich". The poor rich don't have enough money, and smart people aren't going to buy your company's product anyway. The stupid rich is where the money is made.

What surprises me is the number of people who use caps-lock instead of shift to type a single capital letter, i.e.
caps-lock on
type letter
caps-lock off
every single time.

Virtualisation is, in many ways, trying to do what the OS should already be doing, namely isolation between processes (though protected memory), providing an abstraction layer for the hardware (though drivers) and allocating resources (through the CPU/IO schedulers).

Unfortunately, a certain OS has been so bad at doing this (historically) that people turn to virtualisation and you end up with a form of inner-platform effect. We have Linux implementing the virtio drivers to interface with the hypervisor which implements real drivers to talk to the real hardware. We have the guest's scheduler trying to manage "virtual CPUs" without any real information about what resources are actually available. We have hypervisors trying to re-implement copy-on-write for memory pages that the OS already does out-of-the-box.

Virtualisation is used as a "one size fits all" sledgehammer, often where it isn't the appropriate solution.

The "poor guy" is believed to have been part of the gang that came up with the plan in the first place. He wasn't, however, expecting it to be a real bomb.

Brian Douglas Wells

In the UK you require a license to watch or record TV as it is being broadcast, or to install TV receiving equipment for the purpose of watching/records TV as it is broadcast.

The requirement is worded to be independent of the technology used - terrestrial, satellite broadcasts, cable, internet etc

You don't require a license to watch recordings, so if you only ever watch DVDs, BBC iPlayer and 4OD you don't require a license. Copyright is a different issue - the TV license is a license to install/use equipment and is nothing to do with copyright.

Wikipedia links to this DEF CON presentation(PDF) from 2003 which has some details.

And, not for nothing, the example you provided of it failing, isn't.

It's difficult to claim to be an "independent country" when you have to rely on the British RAF and British RNLI to rescue when you entire "country" catches fire.

I found it funny back when they tried to launch Sealand as a datacentre about ten years ago (HavenCo). 100% of their bandwidth came courtesy of the UK. How long would that bandwidth have lasted if they had hosted anything that had upset the UK authorities?

Indeed, how long would Sealand last if they were to upset anyone of any importance?

James Doohan (Scotty) William Shatner (Kirk),

I really hope you don't have to explain who Doohan and Shatner are to people on Slashdot.

Mobile reception on the tube isn't a popular idea. Tube mobile network opposed by 76% of Londoners

A similar amount of folks were in opposition due to the fact that the underground is currently blissfully free of Dom Joly type berks barking at top volume into their mobile phones about what station they're at and what's for dinner.

This is a fundamental problem. Instructions and data are intermingled in memory and on disk. Buffer overflows exploit this by tricking computers into executing data as code. Most interpreted languages support an eval() like procedure that takes data and interprets it as code. On the topic of interpreted languages - is a Perl script data or code?

Things like the NX bit in newer CPUs help but don't solve the problem.

Triple DES is, for practical purposes, as secure as 128 bit AES and 256 bit AES. 256 bit AES has flaws in its key schedule routines, which at the moment make it slightly easier to brute force than 128 bit AES, but still impractical.

The problem that drove the development of AES is that the performance of Triple DES sucks.

Saying the hockey game caused the riot is like saying the assassination of Archduke Franz Ferdinand caused World War I.

I heard it was some bloke called Archie Duke, who shot an ostrich because he was hungry?

I'm not sure when it happened, but a lot of sites like NetFlix started doing these side-ways scrolling interfaces and it's just annoying and difficult to navigate.

It happened about the same time everyone started buying widescreen monitors, laptops and tablets. Widescreen might be great for watching films, but it's dreadful for reading text.