[Box Backup-commit] COMMIT r2161 - box/boxbackup-web

Thu May 15 19:14:47 BST 2008

Author: jamesog
Date: 2008-05-15 19:14:44 +0100 (Thu, 15 May 2008)
New Revision: 2161

Added:
   box/boxbackup-web/security.html
Modified:
   box/boxbackup-web/bbstyles.css
   box/boxbackup-web/index.html
Log:
Add a note about the Debian OpenSSL vulnerability.


Modified: box/boxbackup-web/bbstyles.css
===================================================================

--- box/boxbackup-web/bbstyles.css	2008-05-06 22:20:10 UTC (rev 2160)
+++ box/boxbackup-web/bbstyles.css	2008-05-15 18:14:44 UTC (rev 2161)
@@ -27,7 +27,13 @@
 	margin-left: 250px;
 	position: relative;
 	width: auto }
-	
+
+#security-announce {
+	border: 1px solid #c00;
+	color: #c00;
+	padding: 5px;
+}
+
 tr,td {font-size: 1em;
 	line-height: 150%;
 	text-align: left;

Modified: box/boxbackup-web/index.html
===================================================================
--- box/boxbackup-web/index.html	2008-05-06 22:20:10 UTC (rev 2160)
+++ box/boxbackup-web/index.html	2008-05-15 18:14:44 UTC (rev 2161)
@@ -16,6 +16,8 @@
 
 <h1>Box Backup</h1>
 
+<p id="security-announce"><strong>SECURITY ANNOUNCEMENT:</strong> Please click <a href="security.html">here</a> to read more on the recent OpenSSL vulnerability in Debian GNU/Linux and how it affects Box Backup. <em>[2007/05/15]</p>
+
 <p>An open source, completely automatic on-line backup system for UNIX.
 <ul>
 <li>All backed up data is stored on the server in files on a filesystem -- no tape or archive devices are used

Added: box/boxbackup-web/security.html
===================================================================
--- box/boxbackup-web/security.html	                        (rev 0)
+++ box/boxbackup-web/security.html	2008-05-15 18:14:44 UTC (rev 2161)
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta http-equiv="content-type" content="text/html;charset=iso-8859-1" />
+<title>Box Backup Security Announcement</title>
+<link rel="stylesheet" href="bbstyles.css" type="text/css" />
+</head>
+<body>
+<div align="center">
+<div id="header">
+<div id="logo">
+<img src="images/bblogo.png" alt="logo" height="65" width="331" border="0" vspace="5" align="middle" /> <img src="images/stepahead.png" alt="a step ahead in data security" width="182" height="11" hspace="10" vspace="20" border="0" align="middle" /></div>
+</div>
+<div id="page">
+
+<h1>Security Announcement</h1>
+
+<p>On 13th May, 2008, the Debian Project announced a vulnerability in their OpenSSL package. See <a href="http://lists.debian.org/debian-security-announce/2008/msg00152.html">the announcement</a> for more information.</p>
+
+<p>This page attempts to explain how this may affect users of Box Backup using Debian systems.</p>
+
+<p>First and foremost, Box Backup users who generated their certificates/keys on affected Debian systems should consider the security of their backups compromised. The server admin or anyone able to deduce the private key of a server or client certificate could have read your data.</p>
+
+<p>If the <acronym title="Pseudo Random Number Generator">PRNG</acronym> in your OpenSSL was insufficiently random, you need to:
+	<ul>
+		<li>Regenerate all affected certificates, which have been generated or signed on an affected system</li>
+		<li>Regenerate all the data keys (*-FileEncKeys.raw)</li>
+		<li>Destroy the data stored on your server to an appropriate level of security (overwrite with zeros at the least, more if you're paranoid)</li>
+		<li>Upload everything again</li>
+		<li>Take appropriate measures under the assumption that you have been storing your data in plain text on a public server without authentication.</li>
+	</ul>
+(i.e. start from scratch, destroying all trace of the backed up data, and take other measures to mitigate the exposure of your secrets.)</p>
+
+<p>You need only worry about the systems where:
+	<ul>
+		<li>The certificates were generated or signed</li>
+		<li>The .raw keys were generated</li>
+		<li>The client which backed up data</li>
+	</ul>
+</p>
+
+<p>If your server has this flaw, but no key material or signing was done on it, you should be fine.</p>
+
+<p>If your certificates are weak but the .raw keys are fine, assume that your data has not been read, but that an attacker logged in and corrupted your backups. Destroy the data and start again.</p>
+
+<p>If your certificates are fine<sup>[1]</sup> but a client's .raw file isn't <em>OR</em> an affected client backed up data, just destroy data for that client and restart with that client. Assume that client's data has been exposed to the server admin, but not the outside world.</p>
+
+<p><sup>[1]</sup> Meaning that all cryptographic operations were done on an unaffected machine, including the generation of the client certificate keys before signing elsewhere.</p>
+
+</div>
+</div>
+</body>
+</html>


