Cryptsetup development
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Mark Foley <mfoley@novatec-inc.com>, cryptsetup@lists.linux.dev
Subject: Re: Using Windows and bitlocker
Date: Fri, 20 Jun 2025 15:09:35 +0200	[thread overview]
Message-ID: <758b021e-bf8a-4785-a29e-cbec16fbdb34@gmail.com> (raw)
In-Reply-To: <202506192255.55JMt0n4027293@server.novatec-inc.com>

On 6/20/25 12:55 AM, Mark Foley wrote:
> On Thu, 19 Jun 2025 21:45:30 Michael Kjörling <152cc69a347e@ewoof.net>wrote:
>>
>> On 19 Jun 2025 11:57 -0400, from mfoley@novatec-inc.com (Mark Foley):
>>> [...] I've downloaded and installed cryptsetup 2.7.5. [...]
>>
>> Most Linux distributions include cryptsetup in their repositories; you
>> should not need to download and install it manually through
>> out-of-band means. Using the distribution's packaged version is
>> generally better unless you are working on the cryptsetup code; you
>> get updates through the distribution's normal update process, and you
>> don't risk unknowingly introducing incompatibilities between for
>> example the kernel, libcryptsetup, and cryptsetup.
> 
> Michael, thanks for your prompt response. My distro (Slackware) does not ship
> with cryptsetup

AFAIK Slackware packages cryptsetup, at least in recent versions.
While it is one of the oldest distros I know, it is not so generic :)

Milan


  parent reply	other threads:[~2025-06-20 13:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 15:57 Using Windows and bitlocker Mark Foley
2025-06-19 21:45 ` Michael Kjörling
2025-06-19 22:55   ` Mark Foley
2025-06-20 12:49     ` Michael Kjörling
2025-06-20 13:09     ` Milan Broz [this message]
2025-06-20 15:41       ` Mark Foley
2025-06-20 20:39     ` Brian J. Murrell
2025-06-20 20:58   ` Brian J. Murrell

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=758b021e-bf8a-4785-a29e-cbec16fbdb34@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=cryptsetup@lists.linux.dev \
    --cc=mfoley@novatec-inc.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox