All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 03/12] package/volume-key: new package
Date: Thu, 23 Jul 2020 10:58:57 +0200	[thread overview]
Message-ID: <20200723105857.285d0375@windsurf.home> (raw)
In-Reply-To: <20200723010810.3237608-4-aduskett@gmail.com>

On Wed, 22 Jul 2020 18:08:01 -0700
aduskett at gmail.com wrote:

> From: Adam Duskett <Aduskett@gmail.com>
> 
> The volume-key project provides a library for manipulating storage volume
> encryption keys and storing them separately from volumes, and an associated
> command-line tool, named volume_key.
> 
> The main goal of the software is to allow restoring access to an encrypted
> hard drive if the primary user forgets the passphrase. The encryption key back
> up can also be useful for extracting data after a hardware or software failure
> that corrupts the header of the encrypted volume, or to access the company
> data after an employee leaves abruptly.
> 
> Updated versions of udisks are dependent on this package.
> 
> Signed-off-by: Adam Duskett <Aduskett@gmail.com>

Why is this package introduced ? According to udisks it was at some
point a dependency of libblockdev:

+	depends on BR2_TOOLCHAIN_HAS_SYNC_4 # libblockdev -> volume-key -> cryptsetup

But I don't see where it is used in the libblockdev package.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-07-23  8:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  1:07 [Buildroot] [PATCH 00/12] package/udisks: bump version to 2.9.0 aduskett at gmail.com
2020-07-23  1:07 ` [Buildroot] [PATCH 01/12] package/gcr: fix gpg path aduskett at gmail.com
2020-07-23  7:44   ` Thomas Petazzoni
2020-07-23  1:08 ` [Buildroot] [PATCH 02/12] package/libbytesize: new package aduskett at gmail.com
2020-07-23  7:54   ` Thomas Petazzoni
2020-07-23  1:08 ` [Buildroot] [PATCH 03/12] package/volume-key: " aduskett at gmail.com
2020-07-23  8:58   ` Thomas Petazzoni [this message]
2020-07-23  1:08 ` [Buildroot] [PATCH 04/12] package/libblockdev: " aduskett at gmail.com
2020-07-23  8:57   ` Thomas Petazzoni
2020-07-23  1:08 ` [Buildroot] [PATCH 05/12] package/libblockdev: add cryptography support aduskett at gmail.com
2020-07-23 12:06   ` Thomas Petazzoni
2020-07-23  1:08 ` [Buildroot] [PATCH 06/12] package/libblockdev: add fs plugin support aduskett at gmail.com
2020-07-23  1:08 ` [Buildroot] [PATCH 07/12] package/spidermonkey: add host variant aduskett at gmail.com
2020-07-23  1:08 ` [Buildroot] [PATCH 08/12] package/polkit: " aduskett at gmail.com
2020-07-23  1:08 ` [Buildroot] [PATCH 09/12] package/udisks/Config.in: alphabatize package selection aduskett at gmail.com
2020-07-23  1:08 ` [Buildroot] [PATCH 10/12] package/udisks: bump version to 2.9.0 aduskett at gmail.com
2020-07-23  1:08 ` [Buildroot] [PATCH 11/12] package/libblockdev: add gobject-introspection support aduskett at gmail.com
2020-07-23 12:08   ` Thomas Petazzoni
2020-07-23  1:08 ` [Buildroot] [PATCH 12/12] package/udisks: " aduskett at gmail.com
2020-07-23  7:47 ` [Buildroot] [PATCH 00/12] package/udisks: bump version to 2.9.0 Thomas Petazzoni
2020-07-23 14:31 ` Thomas Petazzoni
2020-07-23 16:54   ` Adam Duskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200723105857.285d0375@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.