<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - cryptsetup can not handle passwordless truecrypt volumes"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=75816">75816</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>cryptsetup can not handle passwordless truecrypt volumes
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>fergofrog@fergofrog.com
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>general
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>systemd
          </td>
        </tr></table>
      <p>
        <div>
        <pre>From commit 66a5dbdf282435403f947c2caadd04bb0cdec752 which introduced
requirements for /dev/* keyfiles to have .device services added, the
documentation for handling passwordless truecrypt volumes is now incorrect. The
suggested behaviour from `man crypttab` is to use /dev/null in the password
field. After the above commit, a dev-null.device service is added as a
requirement to mount the crypttab devices. This is incorrect as there is no
need for a /dev/null device, nor does it exist (causing the boot to hang as it
waits for the mount to timeout).

A temporary work around is to create a blank file and specify it in the
password column and continue using the tcrypt-keyfile option. 

As an aside, the example at the bottom of `man crypttab` uses `/null' in the
password column, I suspect this is incorrect too (and did not work for me).</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>