[Slackbuilds-users] dislocker
B. Watson
urchlay at slackware.uk
Mon Jun 22 21:03:31 UTC 2026
On Mon, 22 Jun 2026, Jim via SlackBuilds-users wrote:
> I would miss it if it got removed. Unless there is something else that
> does the same job.
OK, that's 3 votes for keeping it, and none for removal.
Tim Dickson might even be able to take over as maintainer... so it
stays, as an orphaned build.
Which probably means I have to update it to the latest bleeding-edge
git commit of dislocker. So far, that's the only way I've gotten
dislocker to build with mbedtls-3.6.6. So I'll do that, and set the
maintainer to "orphaned", and Tim can take it over when he's ready.
Sound like a plan?
Reading back, I might not have made it clear... the point of the
exercise is to update mbedtls to a version that's still supported by
its upstream. 3.6.6 is a LTS (long-term support) branch of mbedtls,
the 2.x series have all been EOLed. This matters more for mbedtls
than it might for other stuff, because mbedtls is a crypto/security
library.
> 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.
Not all of us have a "'Doze partition" (I don't). When I update
dislocker to the latest git, I won't be able to test whether it
actually works (decrypts BitLocker encrypted partitions); all I can
do is make sure it compiles and basic stuff like "dislocker -h" (show
built-in help) works.
So I'll be relying on you (all of you who responded to the original
mail) to let me know if it works or not.
More information about the SlackBuilds-users
mailing list