Tag Archives: private

UK Data Analysts Demand Improvements to Privacy and Security Standards

This year’s Fine Balance conference was quite an exciting event, as representatives as different as Oracle, a computing company, and the NHS sought to figure out how they could protect people’s privacy in such a connected society.

The even has been a staple for a long time. There have been years that it focused on overlarge government databases and breaches of those databases, but this year the debate was all on the private sector. There was discussion about the government, but mainly to say that it did not have enough power. Privacy advocates applauded the decision of the government earlier this year to get rid of the identity card scheme and the planned sharepoint database, cut also said that the new powers that the Information Commissioner’s Office (ICO) has are not enough.

Especially after the fiasco earlier this year in which Google allegedly accidentally collected the public wifi signals of millions of people, and as more and more vulnerabilities are allowing malicious parties to steal information right off of private computers the impetus was on the technology companies to better protect their customers. Many at the conference called for a lawsuit against Google over the data theft and for the ICO to take a much tougher stand against companies that make this sort of egregious error.

Some also said that it should be consumers who learn how to protect their own data. Many consumers, for example, do not even know about the risks of identity theft online and fill out forms whenever it is asked of them. These people argued that the onus for data protection was on the people, and that it was the ICO’s job to ensure that the people were properly educated about the risks of giving out information.

A final argument was that the UK just simply has not gotten into the privacy debate enough, and that there needs to be a call for more debate. The German constitution, for example, was framed with privacy in mind. In contrast, the UK has not even properly adopted article 22 of the Human Rights Act, declaring privacy to be a civil liberty. The current law in the UK says that financial damage must be proven before a privacy-related complaint can be heard in court. Experts say that it is this sort of attitude that makes privacy such a problem in the UK. A coordinated government response is needed to ensure that citizens can be protected as privacy becomes an ever-larger problem.

UK Data Analysts Demand Improvements to Privacy and Security Standards

This year’s Fine Balance conference was quite an exciting event, as representatives as different as Oracle, a computing company, and the NHS sought to figure out how they could protect people’s privacy in such a connected society.

The even has been a staple for a long time. There have been years that it focused on overlarge government databases and breaches of those databases, but this year the debate was all on the private sector. There was discussion about the government, but mainly to say that it did not have enough power. Privacy advocates applauded the decision of the government earlier this year to get rid of the identity card scheme and the planned sharepoint database, cut also said that the new powers that the Information Commissioner’s Office (ICO) has are not enough.

Especially after the fiasco earlier this year in which Google allegedly accidentally collected the public wifi signals of millions of people, and as more and more vulnerabilities are allowing malicious parties to steal information right off of private computers the impetus was on the technology companies to better protect their customers. Many at the conference called for a lawsuit against Google over the data theft and for the ICO to take a much tougher stand against companies that make this sort of egregious error.

Some also said that it should be consumers who learn how to protect their own data. Many consumers, for example, do not even know about the risks of identity theft online and fill out forms whenever it is asked of them. These people argued that the onus for data protection was on the people, and that it was the ICO’s job to ensure that the people were properly educated about the risks of giving out information.

A final argument was that the UK just simply has not gotten into the privacy debate enough, and that there needs to be a call for more debate. The German constitution, for example, was framed with privacy in mind. In contrast, the UK has not even properly adopted article 22 of the Human Rights Act, declaring privacy to be a civil liberty. The current law in the UK says that financial damage must be proven before a privacy-related complaint can be heard in court. Experts say that it is this sort of attitude that makes privacy such a problem in the UK. A coordinated government response is needed to ensure that citizens can be protected as privacy becomes an ever-larger problem.

How to get a self signed certificate?

SSL makes use of what is known as asymmetric cryptography, commonly referred to as public key cryptography (PKI). With public key cryptography, two keys are created, one public, one private. Anything encrypted with either key can only be decrypted with its corresponding key. Thus if a message or data stream were encrypted with the server’s private key, it can be decrypted only using its corresponding public key, ensuring that the data only could have come from the server.

If SSL utilizes public key cryptography to encrypt the data stream traveling over the Internet, why is a certificate necessary? The technical answer to that question is that a certificate is not really necessary – the data is secure and cannot easily be decrypted by a third party. However, certificates do serve a crucial role in the communication process. The certificate, signed by a trusted Certificate Authority (CA), ensures that the certificate holder is really who he claims to be. Without a trusted signed certificate, your data may be encrypted; however, the party you are communicating with may not be whom you think. Without certificates, impersonation attacks would be much more common.

Step 1: Generate a Private Key

The openssl toolkit is used to generate an RSA Private Key and CSR (Certificate Signing Request). It can also be used to generate self-signed certificates which can be used for testing purposes or internal usage.

The first step is to create your RSA Private Key. This key is a 1024 bit RSA key which is encrypted using Triple-DES and stored in a PEM format so that it is readable as ASCII text.

Step 2: Generate a CSR (Certificate Signing Request)

Once the private key is generated a Certificate Signing Request can be generated. The CSR is then used in one of two ways. Ideally, the CSR will be sent to a Certificate Authority, such as Thawte or Verisign who will verify the identity of the requestor and issue a signed certificate. The second option is to self-sign the CSR, which will be demonstrated in the next section.

During the generation of the CSR, you will be prompted for several pieces of information. These are the X.509 attributes of the certificate. One of the prompts will be for “Common Name (e.g., YOUR name)”. It is important that this field be filled in with the fully qualified domain name of the server to be protected by SSL. If the website to be protected will be https://public.akadia.com, then enter public.akadia.com at this prompt.

Step 3: Remove Passphrase from Key

One unfortunate side-effect of the pass-phrased private key is that Apache will ask for the pass-phrase each time the web server is started. Obviously this is not necessarily convenient as someone will not always be around to type in the pass-phrase, such as after a reboot or crash. mod_ssl includes the ability to use an external program in place of the built-in pass-phrase dialog, however, this is not necessarily the most secure option either. It is possible to remove the Triple-DES encryption from the key, thereby no longer needing to type in a pass-phrase. If the private key is no longer encrypted, it is critical that this file only be readable by the root user! If your system is ever compromised and a third party obtains your unencrypted private key, the corresponding certificate will need to be revoked.

Step 4: Generating a Self-Signed Certificate

At this point you will need to generate a self-signed certificate because you either don’t plan on having your certificate signed by a CA, or you wish to test your new SSL implementation while the CA is signing your certificate. This temporary certificate will generate an error in the client browser to the effect that the signing certificate authority is unknown and not trusted.

Step 5: Installing the Private Key and Certificate

When Apache with mod_ssl is installed, it creates several directories in the Apache config directory. The location of this directory will differ depending on how Apache was compiled.

Step 6: Configuring SSL Enabled Virtual Hosts

Step 7: Restart Apache and Test