Google has brought back a re-incarnation of the old finger protocol, in the form of WebFinger. It strikes me as a simple to implement solution to identity+discovery on the web. OAuth, OpenID and other systems tackle authentication, but suffer from being less than user friendly (from a UI standpoint) in that the average person does not equate a URL with a person (identity). WebFinger on the other hand utilizes the all to familiar email address format, something that is easily understood by even the most basic internet user.
Updated my previous iCal file with the official 2010 PayDays & Holidays, and those who follow the same calendar, well at least according to DOP and WAC. Maybe next year they will actually provide this in a format that someone can use, until then the ics file below should work with just about any calendar application you might use at this point. It is also available as a Google calendar that you may subscribe to, add or sync. Just search public calendars for it.
Luckily, in PC based systems, most applications rely on this information from the underlying operating system. Different OS's handle timezone/daylight savings data differently. Some have a limited ability to allow for differing DST start/stop dates on different years, and therefore are going to have some issues with historical data regardless. Applications may handle this themselves, and the capabilities range widely. I am going to try to address some of the more common OS's, applications & devices and point you toward the fix. Remember that this is coming right quick.
**NOTE: If you are a home/individual user, and you have kept up on your updates for your operating system - you are probably alright. The notable exception is updating your Java, though you probably aren't using any Java apps that will be sensitive to this, but go ahead just to be safe.
Many organizations have a library of documents on their websites available to the public. The types of documents range from legal notices, price lists, forms, contact lists and more. Internally these documents are usually created with Microsoft Word or Excel, or other office suites. What people don't realize the amount of unintended information contained in these files. Office document formats are highly complex data files and have many options for tracking changes, embedding other files, storing metadata about the author.
I have often talked of my liking of proximity cards for access control due to the fact that they aren't a writable format (i.e. you can't buy a writer or blank cards). Well recently a developer (hacker) in Canada (Jonathan Westhues) has built a prox-card emulator. His device is capable of producing similar behavior to an actual prox-card, but is also programmable. He has shown how the signal is encoded, how a clandestine reader and sniffer work and then duplicating that signal with his device.
Since I first heard of Network Admission Control (NAC) I have been unable to fathom a workable scenario for the technology. The concept in NAC is that machines wishing to connect to the network (typically laptops and remote clients) should be checked for compliance with security policy. Most implementations rely upon an agent installed on the client wishing access that reports compliance (up to date signatures, patches, configuration) at which point the machine is granted admission to the network proper.