1<?xml version="1.0" encoding="UTF-8" standalone="no"?> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 3<html xmlns="http://www.w3.org/1999/xhtml"> 4 <head> 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 6 <title>Release 4.2: Queue access method</title> 7 <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> 8 <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> 9 <link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" /> 10 <link rel="up" href="upgrade_4_2_toc.html" title="Chapter��39.��Upgrading Berkeley DB 4.1 applications to Berkeley DB 4.2" /> 11 <link rel="prev" href="upgrade_4_2_java.html" title="Release 4.2: Java" /> 12 <link rel="next" href="upgrade_4_2_cksum.html" title="Release 4.2: DB_CHKSUM_SHA1" /> 13 </head> 14 <body> 15 <div class="navheader"> 16 <table width="100%" summary="Navigation header"> 17 <tr> 18 <th colspan="3" align="center">Release 4.2: Queue access method</th> 19 </tr> 20 <tr> 21 <td width="20%" align="left"><a accesskey="p" href="upgrade_4_2_java.html">Prev</a>��</td> 22 <th width="60%" align="center">Chapter��39.��Upgrading Berkeley DB 4.1 applications to Berkeley DB 4.2</th> 23 <td width="20%" align="right">��<a accesskey="n" href="upgrade_4_2_cksum.html">Next</a></td> 24 </tr> 25 </table> 26 <hr /> 27 </div> 28 <div class="sect1" lang="en" xml:lang="en"> 29 <div class="titlepage"> 30 <div> 31 <div> 32 <h2 class="title" style="clear: both"><a id="upgrade_4_2_queue"></a>Release 4.2: Queue access method</h2> 33 </div> 34 </div> 35 </div> 36 <p>We have discovered a problem where applications that specify Berkeley DB's 37encryption or data checksum features on Queue databases with extent 38files, the database data will not be protected. This is obviously a 39security problem, and we encourage you to upgrade these applications to 40the 4.2 release as soon as possible.</p> 41 <p>The Queue databases must be dumped and reloaded in order to fix this 42problem. First build the Berkeley DB 4.2 release, then use your previous 43release to dump the database, and the 4.2 release to reload the 44database. For example:</p> 45 <pre class="programlisting">db-4.1.25/db_dump -P password -k database | db-4.2.xx/db_load -P password new_database</pre> 46 <p>Note this is <span class="bold"><strong>only</strong></span> necessary for Queue access method databases, 47where extent files were configured along with either encryption or 48checksums.</p> 49 </div> 50 <div class="navfooter"> 51 <hr /> 52 <table width="100%" summary="Navigation footer"> 53 <tr> 54 <td width="40%" align="left"><a accesskey="p" href="upgrade_4_2_java.html">Prev</a>��</td> 55 <td width="20%" align="center"> 56 <a accesskey="u" href="upgrade_4_2_toc.html">Up</a> 57 </td> 58 <td width="40%" align="right">��<a accesskey="n" href="upgrade_4_2_cksum.html">Next</a></td> 59 </tr> 60 <tr> 61 <td width="40%" align="left" valign="top">Release 4.2: Java��</td> 62 <td width="20%" align="center"> 63 <a accesskey="h" href="index.html">Home</a> 64 </td> 65 <td width="40%" align="right" valign="top">��Release 4.2: DB_CHKSUM_SHA1</td> 66 </tr> 67 </table> 68 </div> 69 </body> 70</html> 71