[Slackbuilds-users] dislocker

[Jim]

Hi all,

I would miss it if it got removed.  Unless there is something else that
does the same job.

I'm surprised by the low number of responses to this.  I don't expect
Slackware users to be looking at their 'Doze partition often, but every now
and then it might be necessary.

                                Jim

On Mon, Jun 22, 2026 at 13:00 (-0400), Barry J. Grundy wrote:

> On 26/06/21 03:11AM, B. Watson wrote:

>> Does anyone use dislocker?

>> It's been effectively abandoned for years. We're updating mbedtls,
>> which dislocker depends on... and it's going to need some serious work
>> to get dislocker to work with mbedtls-3.6.6.

>> We have two choices: fix/patch/update dislocker to work with the new
>> mbedtls, or remove dislocker (since it has no active maintainer).

>> So if anyone on this mailing list uses dislocker, *please* take
>> over as maintainer. You won't have to patch it for the new mbedtls
>> yourself, I'll do that job, and then hand the script over to you.

>> But if nobody cares about dislocker enough to want to maintain it, I'm
>> going to remove it from the repo with the next update. No need to do
>> all that work if it's unused/unloved.

>> So anyone?

> I prefer libbde.  But that might not work for those who want something
> less restrictive.  I have students that I know have used dislocker in
> the past, but that's most likely because it's the first Bitlocker
> solution they come across rather than a real preference.  So I do know
> that it is being used, but I cannot say for sure that it would be missed
> if removed.

> Barry
> bgrundy at linuxleo.com
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/