Package Details: dislocker 0.7.3-5

Git Clone URL: https://aur.archlinux.org/dislocker.git (read-only, click to copy)
Package Base: dislocker
Description: Read/write BitLocker-encrypted volumes
Upstream URL: https://github.com/Aorimn/dislocker
Licenses: GPL2
Conflicts: dislocker-git
Submitter: mrxx
Maintainer: mrxx
Last Packager: mrxx
Votes: 34
Popularity: 1.05
First Submitted: 2014-06-02 17:25 (UTC)
Last Updated: 2024-09-02 11:35 (UTC)

Dependencies (6)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

mrxx commented on 2019-06-06 01:01 (UTC)

Thanks, BoneTone. Dislocker was not able to write to all types of Bitlocker volumes for some time after I created the package. This has changed over time, nowadays the upstream description states it is able to write to most versions of Bitlocker volumes.

As both the package description and upstream url were outdated, I've updated the PKGBUILD to reflect these changes.

BoneTone commented on 2019-06-05 18:32 (UTC)

Thanks mrxx. One other quick question, the description for this package states that it is to create a read only mount of dislocker encrypted volumes (there is even another package on the AUR for read/write capabilities). However, using this (your) package I am able to write to the encrypted volume once I've decrypted & mounted it. Should the description be updated, or is there a bug? Personally, I am pleased that it is able to write to the volume, and would prefer to keep it that way.

mrxx commented on 2019-06-04 13:19 (UTC)

Indeed, the upstream URL is no longer valid. I'll update it when there is a new upstream release.

The source is available at https://github.com/Aorimn/dislocker

BoneTone commented on 2019-06-04 03:16 (UTC)

Is the upstream URL correct? It seems to be redirecting me to an unrelated page. Was hoping to take a look at the code and see if I can improve some error handling when the user submits the wrong user password for a volume.

mrxx commented on 2019-03-11 10:21 (UTC)

GI_Jack, no problems here compiling dislocker on multiple production machines as well as on fresh test VMs.

GI_Jack commented on 2019-03-10 22:43 (UTC)

Looks like it fails compile trying to find ruby.h. Have some kludge:

https://pastebin.com/bfEsdqpp

mrxx commented on 2019-01-23 01:48 (UTC)

pacman calls ldconfig when updating libraries, so most probably it recreated the cache for you.

auroq commented on 2019-01-22 20:23 (UTC)

Hmm. I haven't had a chance to look at this for a while, but today I updated again and re-built and reinstalled dislocker. Now I have no issues. Didn't even have to recreate the linker cache...

mrxx commented on 2019-01-17 15:38 (UTC)

auroq, no problems here with ruby 2.6. Maybe your linker cache is broken. Try to recreate it (as root: ldconfig) Then rebuild the package.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »