Nothing a patch can’t fix

Historically, when we’ve had to make updates to SecureDoc we’ve issued Service Releases (SRs) to address minor bug fixes, software update and feature additions. SRs enabled us to ensure continued compatibility with things such as Mac OS X updates. And like all software companies, we aren’t perfect, but we do understand the need to quickly issue ‘fixes’ for customer-identified issues as it is critical to everyone’s success.

With SecureDoc 6.1 we introduced the ability to apply patches to fix known issues identified by customers. Patches are a much cleaner and less-complicated way to address required fixes for customers. They require very little heavy-lifting on the part of the administrator and can be done in a matter of minutes.

Last week we issued our first-ever patch for SecureDoc 6.1 SR1. This patch addressed a number of customer-reported issues that we’ve worked hard and fast to resolve. The good news is, with this enhancement to our software, it means we can help customers faster and more effectively.

In terms of what this patch addresses, all that information can be found in our patch announcement. Generally speaking it’s an isolated fix that applies specifically to SecureDoc Enterprise Server (SES) 6.1 SR1, so if you’ve recently upgraded to SR1 we strongly recommend you apply the patch mentioned above.

Previous Post
Hot Topics from the RSA 2013 Security Conference
Next Post
All or nothing ? Removable Media Container Encryption is the Answer

Related Posts

Enterprise Encryption for Linux

Enterprise Encryption for Linux

Linux has built in encryption for several years now, yet enterprises still struggle with encryption on Linux laptops.  Why is that? To answer this question, let’s first review the disk encryption capabilities that are built into Linux: (more…)

BASH – Shellshock

BASH Shellshock has been all over the news lately, and has come to the attention of our security conscious customers (which is pretty much all of them.) There are lots and lots of blogs out there on it, a Wikipedia…

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.

Menu