Image of XSLT 2.0 and XPath 2.0 Programmer's Reference (Programmer to Programmer)
Image of Operating System Concepts
Image of Advanced Programming in the UNIX Environment, Second Edition (Addison-Wesley Professional Computing Series)
Image of Beginning Google Maps API 3

List UEFI Secure Boot Certificate Contents

Now that consumer versions of Windows 8 have been released and UEFI Secure Boot-enabled systems are becoming more common, how can a user (or a developer) see what keys have been installed on their system to control what applications they can boot on their system? This post explains how to list out the contents of such keys from the UEFI Shell command line. Why UEFI Secure Boot? The answer is simple – because there are an increasing number of real-world exploits where fraudulently modified early boot code has introduced vulnerabilities into an operating system. It has lead to calls for

GNOME Shell 3.6 DBus Support

I have written before about the DBus support in GNOME Shell. In GNOME Shell 3.6, there are significant changes to the DBus interface; hence this post. The file that contains the DBus interface definitions is shellDBus.js. It contains the following two DBus interface definitions: <interface name=”org.gnome.Shell”> <method name=”Eval”> <arg type=”s” name=”script” direction=”in”> </arg> <arg type=”b” name=”success” direction=”out”> </arg> <arg type=”s” name=”result” direction=”out”> </arg> </method> <method name=”ScreenshotArea”> <arg type=”i” name=”x” direction=”in”> </arg> <arg type=”i” name=”y” direction=”in”> </arg> <arg type=”i” name=”width” direction=”in”> </arg> <arg type=”i” name=”height” direction=”in”> </arg> <arg type=”b” name=”flash” direction=”in”> </arg> <arg type=”s” name=”filename” direction=”in”> </arg> <arg type=”b” name=”success” direction=”out”>