This quote (from the "License to Summon" rulebook for The Laundry role playing game system) may amuse.
Laundry employees can get a license to summon. It’s not that hard. Just complete a few basic Health and Safety and Demonology Courses, do the test, complete the very simple practical exam, and you’re certified. Peter-Francis Young has one, for Yog’s sake! It’s less demanding than getting a Microsoft Certified Professional qualification, and just like an MCP, a license to summon allows you to loose mind-eating horrors on an unsuspecting world.
The games designers are obviously continuing with the anti-Microsoft digs found in the source material, the “Laundry Files” series of novels written by Charles Stross. In his writings, Charles does not come across as a big fan of the Microsoft range of products. In fact, last October he ranted at length on “Why Microsoft Word must Die”. Not a happy man as far as IT goes.
Microsoft has announced that Windows XP will reach end-of-life on April 8th, 2014.
Windows 2000 already reached end-of-life on 13th July, 2010.
PCI-DSS Compliance requires all elements of a Point-Of-Sale (POS) payment application environment to be supported by their vendors with security updates, which includes the operating system the application runs on. Security updates from Microsoft for an operating system come to an end when it is no longer supported. At that time, PCI-SSC will regard any merchant using that operating system as being non-complaint with PCI-DSS. This is covered in the PCI-DSS documentation under “Requirement 6: Develop and maintain secure systems and applications”:
6.1 Ensure that all system components and software are protected from known vulnerabilities by having the latest vendor-supplied security patches installed. Deploy critical patches within a month of release.
It’s therefore a good idea to upgrade any operating system being used for a POS payment system that is no longer supported or will soon reach the end of support. Not doing so may expose merchants to the risk of fines and penalties should their environments be compromised whilst not being compliant with the PCI-DSS.
- Windows XP SP3 and Office 2003 - Support Ends April 8th, 2014
- Extended Support for Windows 2000 Server Ends on July 13, 2010
- Microsoft Support Lifecycle
- PCI DSS Quick Reference Guide
Just had an Adobe update install unwanted applications - Google Chrome and a browser toolbar. Irritating, I know, especially as it means I missed the sneakily hidden opt-out tick box. This just reinforces the knowledge that I could never work in marketing as it would mean discarding my moral code.
But I digress.
I took some screenshots to compose a vitriolic Tweet around and noticed that something weird was going on with the clipboard.
Here’s what the screen looked like to my eyes (or to my SmartPhone):
Here’s what went into the clipboard after I pressed the Print Scrn button on the keyboard:
Where have the tail and the black outline to the box gone?
For many years now I’ve been happily chucking around Windows XP virtual hard disks and loading them with Virtual PC. Sadly I’m going to have to turn to something modern as the virtual processor is no longer up to scratch, as I found when trying to install Windows 8.1 evaluation.
In the past this would have been a Blue Screen but they’re handled differently in Windows 8, usually with a frowning emoticon.
0x0000005D means UNSUPPORTED_PROCESSOR and the solution would be to enable No-Execute Memory Protection in the BIOS.
Virtual PC is ancient so the AMI BIOS has no such setting on any of the menus.
Off now to find a virtualisation product I like.
Back in May, DataCash was a sponsor for one of the biggest networking events for payments developers – Trans-hacktion. The 3-day Hackathon, organised by Birdback, was focused on the latest innovations in the payments and financial technology and held at the London Google Campus.
The event included demos from DataCash and other payments companies followed by hacking sessions. Teams had to hack a product that used partner APIs and present the hack in 3 minutes on the final day. The prizes up for grabs were:
|KingHacker||3D Printer & Champagne|
|1st||Pebble Watch & 1 year of GitHub Silver plan|
|2nd||AIAIAI Headphones & 1 year of GitHub Bronze plan|
|3rd||Raspberry Pi & 6 months of GitHub Bronze plan|
|API||Up Bracelet. Nintendo NES + Super Mario Game|
|AND||Berg Cloud Little Printer & 100$ AWS credit & more...|
By default, Windows will automatically update it’s internal list of trusted root authorities as long as the Update Root Certificates function is installed. This should be enabled by default and takes manual intervention to remove it.
With this component enabled, the following happens:
If you are presented with a certificate issued by an untrusted root authority, your computer will contact the Windows Update Web site to see if Microsoft has added the CA to its list of trusted authorities. If it has been added to the Microsoft list of trusted authorities, its certificate will automatically be added to your trusted certificate store.
If the component is not installed and a certificate from an untrusted CA is encountered then the following text will be seen:
This is an inconvenience for the person browsing the site as they need to click to continue. Applications, though, will be unable to proceed and will throw an exception. Example:
One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server.
If you look at the certificate’s properties, you can see the “Issued by:” value:
This is the name of the server that issued the certificate. It is not the name of the Trusted Root Certificate Authority. To find that instead use the “Certification Path” tab.
Highlight the issuing server and click “View Certificate” button to reveal the issuing CA – in this case “VeriSign Class 3 Public Primary Certification Authority – G5”.
This must match a Trusted Root Certificate Authority certificate in the current user’s certificate store.
So turn on automatic updating of trusted root authority certificates.
For Windows Vista and above, this option is controlled through Group Policy. See the “To Turn Off the Update Root Certificates Feature by Using Group Policy” section of the following Technet article:
Certificate Support and Resulting Internet Communication in Windows Vista
If Windows Update is a blocked site then download and deploy the latest pack of root certificates from Microsoft:
Failing that, find a machine that has the latest root certificates installed and export them from there:
- Open up the Certificates console
- Right-click the required Trusted Root Certificate Authority certificate
- Choose Export from “All Tasks” to open up the Certificate Export Wizard
- Choose an export file format – DER should be fine
- Provide a file name and complete the export.
- Move the file to the machine that’s missing the certificate
- Right-click the file and choose “Install Certificate” to open up the Certificate Import Wizard
- Do not allow the wizard to automatically select the certificate store. Instead choose “Place all certificates in the following store” and click Browse
- On the “Select certificate Store” window, enable “Show physical stores” and highlight “Trusted Root Certification Authorities \ Local computer”
- Complete the import
Thanks to Gurpal Basra for his valuable input.
Daniel Halan has developed an MSMQ Viewer for NServiceBus:
I've lately been working with a scalable cloud solution, and then it's good to use a Service Bus for sending commands, events and messages around the network. Now I tried few MSMQ message viewers that are available, but they all lacked the real-time feedback that would be nice when debugging or just want to know what is happening behind the scenes. So from that a new small application grew, called "ServiceBus MQ Manager". It's a small application that will monitor queues with a set interval, and present the Events, Commands and Messages that are there, but also keeping messages that has been retrieved (deleted) from the Queue.
which you can download through a link on his blog.
I’m frequently impressed by the additions and changes to Windows as I spend more time on the Windows 8 Consumer Preview.
Here, for example, is how a the progress is now shown for a copy across my home network.
I think this is demonstrating to me how the destination is not able to keep up with the flow. I’m now intrigued to see if there is anything I need to do to improve performance.