I got a new red V5C vehicle log book in the post.  The attached note made me smile. 

Q. Why have you sent me a new V5C(NI)?
A. We are replacing all existing blue V5C(NI)s. The new certificate is being introduced following the theft of a number of blank blue V5Cs. The aim is to reduce the risks to motorists of buying a stolen or cloned vehicle.
For tips and advice go to

WTF, you don’t keep them under lock and key?

Some more links

Elevation of privilege vulnerability for the BlackBerry PlayBook

#BlackBerry #PlayBook


This vulnerability has a Common Vulnerability Scoring System (CVSS) score of 7.2/10.

12-06-2011: A vulnerability that could allow elevation of access privilege on a BlackBerry PlayBook tablet exists in the BlackBerry PlayBook service used to share files over a USB connection between the tablet and a computer running BlackBerry Desktop Software. This vulnerability cannot be exploited by a remote attacker and it presents a low security risk of elevation of privilege attacks against BlackBerry PlayBook tablet users. RIM is not currently aware of this issue being used in attacks against BlackBerry customers.

A user could execute specially crafted code to use this vulnerability to manipulate a BlackBerry PlayBook backup archive file and alter a specific configuration file in order to gain root user privileges (access to system administration-level functionality) on the BlackBerry PlayBook tablet. An individual attempting to use this vulnerability to gain root privileges to the BlackBerry PlayBook tablet requires local access to both the tablet and to the connected computer running BlackBerry Desktop Software, including knowledge of any security passwords that are set.


Exchange 2010 whitespace reclamation


Sanjay sent me this from a Symantec blog by Alex Brown  .. interesting, very interesting.  The Microsoft hotfix listed in the KB doesn’t seem to be available (The KB article has no public hotfixes.)? Wonder if it’s included in SP2?

Some of you may be aware of a scenario in which the reclamation of Exchange 2010 database whitespace during item deletion or truncation is not as great as expected. So why is this a problem for Enterprise Vault customers?

Archiving data from a mailbox will frequently invoke either a deletion or truncation request to the Exchange server. If Exchange is not fully honouring this request then the database from which a customer is archiving will continue to grow as pending whitespace reclamation requests are not processed fully and available whitespace is not recognised.

The good news is that Microsoft have recognised and now resolved the issue:

So what was the problem?

In summary the primary complaint was that in some cases Exchange 2010 customers were noticing that their mailbox databases were continuing to grow even though archiving was taking place and items were being archived as normal. The root cause of this was actually down to how Exchange reclaims whitespace and specifically the changes to this process in Exchange 2010. Modifications to the Online Defragmentation process caused, in some cases, whitespace to not be reclaimed for re-use essentially making that space unusable.

MS have now issued a fix which corrects the action of Online Defragmentation allowing customers to reclaim the excessive whitespace that has been building up in their databases.

Also check out