Came here in search of an answer to a problem, but didn't find it? Visit the forum @, pick a category and ask a question.

Apply the nuke patch to LUKS cryptsetup in Linux Mint 16 and Ubuntu 13.10

This short tutorial shows how to apply the Kali Linux nuke patch to LUKS cryptsetup in Linux Mint 16 and Ubuntu 13.10.

From a physical security and privacy-enhancing perspective, the nuke patch to LUKS cryptsetup is the best news from any distribution so far this year. What the nuke patch gives you, is a cryptsetup command that allows you to render an encrypted disk inaccessible.

It was published by the developers of Kali Linux, a distribution based on Debian and designed for offensive security tasks. You may read about it at A Kali Linux cryptsetup patch that can “nuke” an encrypted disk.

Though this tutorial is targeted at Linux Mint 16 and Ubuntu 13.10 installations, it can be used for any other distribution. Just make sure that all the dependencies are installed. Also, the target system must have full disk encryption configured. Otherwise, what’s the point?

All the steps in this tutorial are accomplished from the command-line, so you need to have a shell terminal open to begin.

1. Install dependencies by typing:
sudo apt-get install libgcrypt11-dev libdevmapper-dev libpopt-dev uuid-dev libtool automake autopoint debhelper xsltproc docbook-xsl dpkg-dev. Note: Without the dependencies installed, the next steps will fail.

2. Get cryptsetup source code: Since the source code for cryptsetup is what we’ll be patching (we can’t patch a binary), get a copy of it by typing sudo apt-get source cryptsetup. After the operation has completed, there should be a directory named cryptsetup-1.4.3. Take note of that.

3. Grab the patch: After getting a copy of cryptsetup, now we need to grab the patch. That’s accomplished by typing git clone There should now be a directory named cryptsetup-nuke-keys in the present directory

4. Apply the patch: To do that, cd into the cryptsetup directory – cd cryptsetup-1.4.3, then type patch -p1 < ../cryptsetup-nuke-keys/cryptsetup_1.4.3+nuke_keys.diff.

5. Build the packages by typing dpkg-buildpackage -b -uc. After the build has completed (successfully), there should be two cryptsetup*.deb and two libcryptsetup*.deb packages that will have to be installed.

6. Install the packages by typing dpkg -i ../libcryptsetup*.deb and dpkg -i ../cryptsetup*.deb. This is what actually gets the nuke option implemented. Now if you type cryptsetup and hit enter, you should see a “luksAddNuke” command.

7. Add a nuke key to the system by typing cryptsetup luksAddNuke /dev/sdaX. Replace “X” with the number of the encrypted partition on your setup. On a default installation of Ubuntu and Linux Mint, that number should be “5,” so the command will be cryptsetup luksAddNuke /dev/sda5. After typing that command, you’ll be prompted to “Enter any existing passphrase.” On a default installation, the passphrase you enter is the one configured during installation. That’s the encryption passphrase. After that, you will be prompted to enter and confirm the nuke passphrase. That should do it.

Now that the nuke patch has been applied to cryptsetup, let’s see what happens when a system that has full disk encryption is booted (I used a test installation of Ubuntu 13.10 in a virtual environment for this).

The encryption passphrase must be entered correctly for the system to boot.
Encrypt disk Ubuntu

If that’s done, the system will boot.
Decrypt encrypt disk Ubuntu 13.10

But if the nuke passphrase is entered instead, the keyslots, where the encryption and nuke passphrases are stored, are wiped clean. So the system returns: cryptsetuo: cryptsetup failed, bad password or options. It is the same message the system returns if the wrong passphrase is specified. However, there’s a catch to this. If you backed up the keyslots, it is possible to restore them, and be able to boot the system using the encryption passphrase. See the tail end of How to nule your Kali Liux installation for how to do this.
Nuke LUKS cryptsetup encrypt disk Ubuntu

To have articles like this delivered automatically to your Feed Reader or Inbox, subscribe via RSS or email.
Digital Ocean SSD VPS Cloud Server droplets

Digital Ocean is a VPS/Cloud hosting provider. For just $5 per month, you can get yourself a Cloud server with 512 MB of RAM, 20 GB super-fast SSD, free snapshots, plus backups for a minimal fee. All via a simple graphical interface.

And by signing up with this referral link, you can help support this website.

If you are reading this, your ad could also be occupying this space. Contact us to make it happen.

If commenting on this article is closed, please post your comments at


  1. JIm says:

    Thanks!! I need some help though! I am running Kali and want this feature, but my disk is currently not encrypted. I found the below syntax, but this formats the drive.

    cryptsetup -c aes-xts-plain -s 512 -h sha256 -y luksFormat /dev/sda1

    What syntax can I use to encrypt the drive with the nuke password without formatting my current install?

    Thanks for any help!

    • finid says:

      If the hard drive was not encrypted during installation, I don’t think you can use cryptsetup to encrypt afterwards. That, of course, means that you can’t set a nuke password.

  2. Stiri says:

    Hello can you write a tutorial on how to apply this on linux mint 17 it will be great to have this feature on mint 17 :)

  3. Webmaster says:

    Hello i have some troble apply this to linux mint 16 x^4 Cianamon

    After step 1 i apply thr step 2 and i get this

    sudo apt-get source cryptsetup
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done

    You must put some ‘source’ URIs in your sources.list

    What should i do next or what is wrong

    • finid says:

      By default, Mint does not have source repository entries in its sources.list file. That’s likely the error. To get around it, add source URI’s to the /etc/apt/sources.list.d/official-package-repositories.list file.

      Open the file for editing by typing sudoedit /etc/apt/sources.list.d/official-package-repositories.list. Then for every deb entry in that file, add its deb-src complement.

      Here’s an example taken from that file. The first two lines of that file begin with.

      deb petra main upstream import
      deb petra main

      After you edit it, it should read:

      deb petra main upstream import
      deb-src petra main upstream import
      deb petra main
      deb-src petra main

      Just do the same with each line.

      • Webmaster says:

        Thank you finid that workt but now on the Build package step dpkg-buildpackage -b -uc

        It apear

        dpkg-buildpackage: source package cryptsetup
        dpkg-buildpackage: source version 2:1.4.3-4ubuntu4
        dpkg-buildpackage: source changed by Dmitrijs Ledkovs
        dpkg-buildpackage: host architecture amd64
        dpkg-source –before-build cryptsetup-1.4.3
        dpkg-checkbuilddeps: Unmet build dependencies: build-essential:native
        dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
        dpkg-buildpackage: warning: (Use -d flag to override.)

        And i can’t go ther next step

        dpkg -i ../libcryptsetup*.deb

        As i get this

        dpkg: error processing ../libcryptsetup*.deb (–install):
        cannot access archive: No such file or directory
        Errors were encountered while processing:

        Can you please help me out with this to

        • finid says:

          cannot access archive: No such file or directory

          That likely indicates that you are not in the proper directory when you issued the command, or you did not include the proper number of “..“.

          Check the command again and be sure that you are executing it from the right directory.

  4. crzydg says:

    found a small error (or typo?). Patching command should of course patch the correct version. If you source cryptsetup-1.4.3 you will have to patch patch -p1 < ../cryptsetup-nuke-keys/cryptsetup_1.4.3+nuke_keys.diff


  5. toobuntu says:

    This could instead be set up with apt-build to ensure the nuke patch is applied to all future upgrades to cryptsetup with little effort. Script the upgrade to something like:
    #! /bin/bash
    set -e
    set -u
    pushd /usr/local/src/
    git clone
    apt-build –patch /usr/local/src/cryptsetup-nuke-keys/cryptsetup_*+nuke_keys.diff -p1 install cryptsetup
    exit 0

Leave a Comment