Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault with Windows 10 Pro 19.03 #185

Open
Tom9876 opened this issue Jul 5, 2019 · 21 comments

Comments

@Tom9876
Copy link

@Tom9876 Tom9876 commented Jul 5, 2019

Hello,
I updated my dual-boot systems to Windows 10 19.03. Since then dislocker stopped working with "segmentation fault". I use Arch Linux as well as Ubuntu 18.04 LTS. I also tried a Live Ubuntu (desinfec't 2019) with the same result.
To make sure that Win 19.03 is the problem I have set up an test environment with VirtualBox, I installed a fresh maschine with Win 10 18.09 (Build 17763.rs5_release.180914-1434) and an other one with Win 10 19.03 (Build 18362.11h1_release.190318-1202). Then I tried accessing the bitlocker encrypted partitions from a Mint 19.1 installation. No problem with Win 18.09 but segementation fault with Win 19.03 encrypted partition.
I attached the debug output of dislocker (verbosity level 4) for both.
BDE-1903.txt
BDE-1809.txt

I also tried to mount (ro) the partitions with "bdemount", which works without issues.
If further information is needed I'm happy to provide it.
I'm somehow surprised that I haven't found any other issue report about that, I'm sure that also a lot of other dislocker users have upgraded to Win 19.03. Thats why I have set up the test environment.

Hopefully someone can solve the issue
Regards
Tom

Here the detail of the Win 18.09 partition
manage-bde -status
BitLocker Drive Encryption: Configuration Tool version 10.0.17763
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Disk volumes that can be protected with
BitLocker Drive Encryption:
Volume C: []
[OS Volume]
Size: 39.46 GB
BitLocker Version: 2.0
Conversion Status: Used Space Only Encrypted
Percentage Encrypted: 100.0%
Encryption Method: AES 128
Protection Status: Protection On
Lock Status: Unlocked
Identification Field: Unknown
Key Protectors:
Password
Numerical Password

sudo bdeinfo /dev/sdb2
	bdeinfo 20170902
	BitLocker Drive Encryption information:
		Encryption method		: AES-CBC 128-bit
		Volume identifier		: a0db8306-6fbc-4654-82fb-deee855e104b
		Creation time			: Jul 03, 2019 09:22:10.574463800 UTC
		Description			: DESKTOP-3RP2825 C: 03.07.2019
		Number of key protectors	: 2
	Key protector 0:
		Identifier			: 4191c10a-b095-44e9-9de4-9e8eab2d5444
		Type				: Password
	Key protector 1:
		Identifier			: 6a9c0fa7-be21-44fc-82ef-2754d059376a
		Type				: Recovery password

and here the Information of the Win 19.03 partition:
manage-bde -status
BitLocker Drive Encryption: Configuration Tool version 10.0.18362
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Disk volumes that can be protected with
BitLocker Drive Encryption:
Volume C: []
[OS Volume]
Size: 39.43 GB
BitLocker Version: 2.0
Conversion Status: Used Space Only Encrypted
Percentage Encrypted: 100.0%
Encryption Method: AES 128
Protection Status: Protection On
Lock Status: Unlocked
Identification Field: Unknown
Key Protectors:
Password
Numerical Password

sudo bdeinfo /dev/sdc2
	bdeinfo 20170902
	BitLocker Drive Encryption information:
		Encryption method		: AES-CBC 128-bit
		Volume identifier		: 3aeb59f7-4177-43ac-97b0-ea426a579e9c
		Creation time			: Jul 03, 2019 13:32:04.483078200 UTC
		Description			: DESKTOP-POQVMMB C: 03.07.2019
		Number of key protectors	: 2
	Key protector 0:
		Identifier			: 1f4bec2d-9684-4a94-a40d-967ce36755ae
		Type				: Password
	Key protector 1:
		Identifier			: 34ed0288-8bb6-4f65-9855-03dcbe2fde1d
		Type				: Recovery password
@RaviKavaiya

This comment has been minimized.

Copy link

@RaviKavaiya RaviKavaiya commented Jul 6, 2019

Same here

@CaptainTimothy

This comment has been minimized.

Copy link

@CaptainTimothy CaptainTimothy commented Jul 6, 2019

Same here, any solution?

@benmacdermott

This comment has been minimized.

Copy link

@benmacdermott benmacdermott commented Jul 8, 2019

I'm seeing the same issue - has there been a change in encryption method or something in the latest Win 10 release?

OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18362 N/A Build 18362

BDE status for the drive:

BitLocker Drive Encryption:
Volume D: [Data]
[Data Volume]

Size:                 583.37 GB
BitLocker Version:    2.0
Conversion Status:    Fully Encrypted
Percentage Encrypted: 100.0%
Encryption Method:    XTS-AES 128
Protection Status:    Protection On
Lock Status:          Unlocked
Identification Field: Unknown
Automatic Unlock:     Disabled
Key Protectors:
    External Key
    Numerical Password
    Password

Dislocker debug:

Mon Jul  8 15:01:37 2019 [DEBUG] Verbosity level to DEBUG (4) into 'stdout'
Mon Jul  8 15:01:37 2019 [INFO] dislocker by Romain Coltel, v0.7.1 (compiled for Linux/x86_64)
Mon Jul  8 15:01:37 2019 [DEBUG] --- Config...
Mon Jul  8 15:01:37 2019 [DEBUG]    Verbosity: 4
Mon Jul  8 15:01:37 2019 [DEBUG]    Trying to decrypt '/dev/sda1'
Mon Jul  8 15:01:37 2019 [DEBUG]    	using the recovery password method
Mon Jul  8 15:01:37 2019 [DEBUG]    	-> <redacted>
Mon Jul  8 15:01:37 2019 [DEBUG]    Using the first valid metadata block
Mon Jul  8 15:01:37 2019 [DEBUG] ... End config ---
Mon Jul  8 15:01:37 2019 [DEBUG] Trying to open '/dev/sda1'...
Mon Jul  8 15:01:37 2019 [DEBUG] Trying to open '/dev/sda1'...
Mon Jul  8 15:01:37 2019 [DEBUG] Opened (fd #3).
Mon Jul  8 15:01:37 2019 [DEBUG] Opened (fd #3).
Mon Jul  8 15:01:37 2019 [DEBUG] New memory allocation at 0x55894260e390 (0x18 bytes allocated)
Mon Jul  8 15:01:37 2019 [DEBUG] New memory allocation at 0x55894260e3b0 (0x90 bytes allocated)
Mon Jul  8 15:01:37 2019 [DEBUG] New memory allocation at 0x55894260b340 (0x200 bytes allocated)
Mon Jul  8 15:01:37 2019 [DEBUG] Positioning #3 at offset 0 from 0
Mon Jul  8 15:01:37 2019 [DEBUG] Reading volume header...
Mon Jul  8 15:01:37 2019 [DEBUG] Reading 0x200 bytes from #3 into 0x55894260b340
Mon Jul  8 15:01:37 2019 [DEBUG] Volume header read
Mon Jul  8 15:01:37 2019 [DEBUG] =====[ Volume header informations ]=====
Mon Jul  8 15:01:37 2019 [DEBUG]   Signature: '-FVE-FS-'
Mon Jul  8 15:01:37 2019 [DEBUG]   Sector size: 0x0200 (512) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Sector per cluster: 0x08 (8) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Reserved clusters: 0x0000 (0) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Fat count: 0x00 (0) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Root entries: 0x0000 (0) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Number of sectors (16 bits): 0x0000 (0) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Media descriptor: 0xf8 (248) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Sectors per fat: 0x0000 (0) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Hidden sectors: 0x0000003f (63) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Number of sectors (32 bits): 0x00000000 (0) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Number of sectors (64 bits): 0x0000000000000000 (0) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   MFT start cluster: 0x0000000000060001 (393217) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Metadata Lcn: 0x0000000000000000 (0) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]   Volume GUID: '4967D63B-2E29-4AD8-8399-F6A339E3D001'
Mon Jul  8 15:01:37 2019 [DEBUG]   First metadata header offset:  0x0000000006900000
Mon Jul  8 15:01:37 2019 [DEBUG]   Second metadata header offset: 0x0000000046900000
Mon Jul  8 15:01:37 2019 [DEBUG]   Third metadata header offset:  0x0000000086900000
Mon Jul  8 15:01:37 2019 [DEBUG]   Boot Partition Identifier: '0xaa55'
Mon Jul  8 15:01:37 2019 [DEBUG] ========================================
Mon Jul  8 15:01:37 2019 [INFO] Volume GUID (INFORMATION OFFSET) supported
Mon Jul  8 15:01:37 2019 [DEBUG] Entering get_metadata_lazy_checked
Mon Jul  8 15:01:37 2019 [DEBUG] Positioning #3 at offset 110100480 from 0
Mon Jul  8 15:01:37 2019 [DEBUG] Reading bitlocker header at 0x6900000...
Mon Jul  8 15:01:37 2019 [DEBUG] Reading 0x70 bytes from #3 into 0x7ffddcd312f0
Mon Jul  8 15:01:37 2019 [DEBUG] New memory allocation at 0x55894260e450 (0x460 bytes allocated)
Mon Jul  8 15:01:37 2019 [DEBUG] Reading data...
Mon Jul  8 15:01:37 2019 [DEBUG] Reading 0x3f0 bytes from #3 into 0x55894260e4c0
Mon Jul  8 15:01:37 2019 [DEBUG] End get_metadata.
Mon Jul  8 15:01:37 2019 [DEBUG] Reading validations data at offset 0x6900460.
Mon Jul  8 15:01:37 2019 [DEBUG] Positioning #3 at offset 110101600 from 0
Mon Jul  8 15:01:37 2019 [DEBUG] Reading 0x8 bytes from #3 into 0x7ffddcd313c8
Mon Jul  8 15:01:37 2019 [DEBUG] Looking if 0xc34e7f57 == 0xc34e7f57 for metadata validation
Mon Jul  8 15:01:37 2019 [DEBUG] We have a winner (n°1)!
Mon Jul  8 15:01:37 2019 [INFO] BitLocker metadata found and parsed.
Mon Jul  8 15:01:37 2019 [DEBUG] =====================[ BitLocker information structure ]=====================
Mon Jul  8 15:01:37 2019 [DEBUG]   Signature: '-FVE-FS-'
Mon Jul  8 15:01:37 2019 [DEBUG]   Total Size: 0x0460 (1120) bytes (including signature and data)
Mon Jul  8 15:01:37 2019 [DEBUG]   Version: 2
Mon Jul  8 15:01:37 2019 [DEBUG]   Current state: ENCRYPTED (4)
Mon Jul  8 15:01:37 2019 [DEBUG]   Next state: ENCRYPTED (4)
Mon Jul  8 15:01:37 2019 [DEBUG]   Encrypted volume size: 626387940864 bytes (0x91d7a17600), ~597370 MB
Mon Jul  8 15:01:37 2019 [DEBUG]   Size of convertion region: 0 (0)
Mon Jul  8 15:01:37 2019 [DEBUG]   Number of boot sectors backuped: 16 sectors (0x10)
Mon Jul  8 15:01:37 2019 [DEBUG]   First metadata header offset:  0x6900000
Mon Jul  8 15:01:37 2019 [DEBUG]   Second metadata header offset: 0x46900000
Mon Jul  8 15:01:37 2019 [DEBUG]   Third metadata header offset:  0x86900000
Mon Jul  8 15:01:37 2019 [DEBUG]   Boot sectors backup address:   0x6910000
Mon Jul  8 15:01:37 2019 [DEBUG] New memory allocation at 0x55894260e8c0 (0xc bytes allocated)
Mon Jul  8 15:01:37 2019 [DEBUG]   ----------------------------{ Dataset header }----------------------------
Mon Jul  8 15:01:37 2019 [DEBUG]     Dataset size: 0x00000418 (1048) bytes (including data)
Mon Jul  8 15:01:37 2019 [DEBUG]     Unknown data: 0x00000001 (always 0x00000001)
Mon Jul  8 15:01:37 2019 [DEBUG]     Dataset header size: 0x00000030 (always 0x00000030)
Mon Jul  8 15:01:37 2019 [DEBUG]     Dataset copy size: 0x00000418 (1048) bytes
Mon Jul  8 15:01:37 2019 [DEBUG]     Dataset GUID: 'F7EEC279-35A5-4702-8824-8F650251FB84'
Mon Jul  8 15:01:37 2019 [DEBUG]     Next counter: 15
Mon Jul  8 15:01:37 2019 [DEBUG]     Encryption Type: AES-XTS-128 (0x8004)
Mon Jul  8 15:01:37 2019 [DEBUG]     Epoch Timestamp: 1560867437 sec, that to say Tue Jun 18 14:17:17 2019
Mon Jul  8 15:01:37 2019 [DEBUG]   --------------------------------------------------------------------------
Mon Jul  8 15:01:37 2019 [DEBUG] Freeing pointer at address 0x55894260e8c0
Mon Jul  8 15:01:37 2019 [DEBUG] =============================================================================
Mon Jul  8 15:01:37 2019 [DEBUG] Header safe: 0x48, 0x7, 0x2, 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] 
Mon Jul  8 15:01:37 2019 [DEBUG] =======[ Datum n°1 informations ]=======
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x0048 (72) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 7
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> ENTRY TYPE UNKNOWN
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 2
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> UNICODE -- Total size header: 8 -- Nested datum: no
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] New memory allocation at 0x55894260e910 (0x80 bytes allocated)
Mon Jul  8 15:01:37 2019 [DEBUG] UTF-16 string: 'DESKTOP-38AGPAE Data 18/06/2019'
Mon Jul  8 15:01:37 2019 [DEBUG] Freeing pointer at address 0x55894260e910
Mon Jul  8 15:01:37 2019 [DEBUG] =========================================
Mon Jul  8 15:01:37 2019 [DEBUG] Header safe: 0xd0, 0x2, 0x8, 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] 
Mon Jul  8 15:01:37 2019 [DEBUG] =======[ Datum n°2 informations ]=======
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x00d0 (208) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 2
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> ENTRY TYPE VMK
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 8
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> VMK -- Total size header: 36 -- Nested datum: yes
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] Recovery Key GUID: 'DC25C333-3020-4791-AEF3-394FC511D805'
Mon Jul  8 15:01:37 2019 [DEBUG] Nonce: 
Mon Jul  8 15:01:37 2019 [DEBUG] 50 1f b0 94 e0 25 d5 01 00 00 00 02 
Mon Jul  8 15:01:37 2019 [DEBUG]    ------ Nested datum(s) ------
Mon Jul  8 15:01:37 2019 [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x005c (92) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 0
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> ENTRY TYPE UNKNOWN 1
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 4
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> USE -- Total size header: 12 -- Nested datum: yes
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] Algo: 0x2002
Mon Jul  8 15:01:37 2019 [DEBUG] Unknown: 
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000000 00 00 
Mon Jul  8 15:01:37 2019 [DEBUG]    ------ Nested datum ------
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x0050 (80) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 0
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> ENTRY TYPE UNKNOWN 1
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 5
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> AES-CCM -- Total size header: 36 -- Nested datum: no
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] Nonce: 
Mon Jul  8 15:01:37 2019 [DEBUG] 00 d6 0c 90 e0 25 d5 01 04 00 00 00 
Mon Jul  8 15:01:37 2019 [DEBUG] MAC: 
Mon Jul  8 15:01:37 2019 [DEBUG] fb 8c 96 98 98 37 ca c7 30 39 bf b4 31 63 ed ce 
Mon Jul  8 15:01:37 2019 [DEBUG] Payload:
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000000 68 09 29 a3 5b d7 3e a7-7c 43 99 d0 d1 29 eb fa 
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000010 b4 b4 a5 d2 a1 22 68 55-9b 7f a6 7d 75 b6 ec c1 
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000020 71 25 05 22 58 9c 85 18-ba 69 8b c7 
Mon Jul  8 15:01:37 2019 [DEBUG]    ---------------------------
Mon Jul  8 15:01:37 2019 [DEBUG] Header safe: 0x5c, 0, 0x4, 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mon Jul  8 15:01:37 2019 [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x0050 (80) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 0
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> ENTRY TYPE UNKNOWN 1
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 5
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> AES-CCM -- Total size header: 36 -- Nested datum: no
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] Nonce: 
Mon Jul  8 15:01:37 2019 [DEBUG] 00 d6 0c 90 e0 25 d5 01 05 00 00 00 
Mon Jul  8 15:01:37 2019 [DEBUG] MAC: 
Mon Jul  8 15:01:37 2019 [DEBUG] 61 8c 8b 8d 8b 9a 8d db 43 19 41 10 70 e0 92 08 
Mon Jul  8 15:01:37 2019 [DEBUG] Payload:
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000000 7f 10 53 b9 3d 1b ca 52-2f de df 6c b0 45 16 2e 
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000010 7f ea 11 e4 bf a3 f8 8f-1b 7c b0 0b 97 aa ae 89 
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000020 9a e4 c1 d6 02 e2 53 2a-75 c8 32 c0 
Mon Jul  8 15:01:37 2019 [DEBUG] Header safe: 0x50, 0, 0x5, 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mon Jul  8 15:01:37 2019 [DEBUG]    ------------------------------
Mon Jul  8 15:01:37 2019 [DEBUG] =========================================
Mon Jul  8 15:01:37 2019 [DEBUG] Header safe: 0x13c, 0x2, 0x8, 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] 
Mon Jul  8 15:01:37 2019 [DEBUG] =======[ Datum n°3 informations ]=======
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x013c (316) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 2
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> ENTRY TYPE VMK
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 8
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> VMK -- Total size header: 36 -- Nested datum: yes
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] Recovery Key GUID: '85B49295-E4F8-4DD6-9690-F7492AC4F2A2'
Mon Jul  8 15:01:37 2019 [DEBUG] Nonce: 
Mon Jul  8 15:01:37 2019 [DEBUG] e0 64 5c 95 e0 25 d5 01 00 00 00 08 
Mon Jul  8 15:01:37 2019 [DEBUG]    ------ Nested datum(s) ------
Mon Jul  8 15:01:37 2019 [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x00ac (172) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 0
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> ENTRY TYPE UNKNOWN 1
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 3
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> STRETCH KEY -- Total size header: 28 -- Nested datum: yes
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] Unkown: 
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000000 00 00 
Mon Jul  8 15:01:37 2019 [DEBUG] Algo: 0x1000
Mon Jul  8 15:01:37 2019 [DEBUG] Salt: 
Mon Jul  8 15:01:37 2019 [DEBUG] 21 b1 23 40 05 1e 4f 38 51 94 8d b8 4e f3 05 18 
Mon Jul  8 15:01:37 2019 [DEBUG]    ------ Nested datum ------
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x0040 (64) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 18
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 5
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> AES-CCM -- Total size header: 36 -- Nested datum: no
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] Nonce: 
Mon Jul  8 15:01:37 2019 [DEBUG] 00 d6 0c 90 e0 25 d5 01 06 00 00 00 
Mon Jul  8 15:01:37 2019 [DEBUG] MAC: 
Mon Jul  8 15:01:37 2019 [DEBUG] 4c 0a 94 6c ba 2f b6 e1 fb c3 22 8d b1 ef 4f b1 
Mon Jul  8 15:01:37 2019 [DEBUG] Payload:
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000000 c8 01 29 43 62 76 b0 9b-22 68 a6 35 b5 11 62 36 
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000010 73 b9 5b 6d 84 17 4e 42-7c fb 25 8d 
Mon Jul  8 15:01:37 2019 [DEBUG]    ---------------------------
Mon Jul  8 15:01:37 2019 [DEBUG] Header safe: 0xac, 0, 0x3, 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mon Jul  8 15:01:37 2019 [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x0050 (80) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 0
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> ENTRY TYPE UNKNOWN 1
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 5
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> AES-CCM -- Total size header: 36 -- Nested datum: no
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] Nonce: 
Mon Jul  8 15:01:37 2019 [DEBUG] 00 d6 0c 90 e0 25 d5 01 08 00 00 00 
Mon Jul  8 15:01:37 2019 [DEBUG] MAC: 
Mon Jul  8 15:01:37 2019 [DEBUG] 97 d9 5d a9 e8 88 93 60 8f be 05 17 9b ae fb 10 
Mon Jul  8 15:01:37 2019 [DEBUG] Payload:
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000000 f7 70 f7 b6 1b 78 f5 64-b0 23 31 32 7c de 80 a7 
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000010 d1 68 84 47 17 4d c4 8f-79 4e 84 73 77 66 f1 4f 
Mon Jul  8 15:01:37 2019 [DEBUG] 0x00000020 74 40 2b 10 97 54 57 b7-7b a3 e5 33 
Mon Jul  8 15:01:37 2019 [DEBUG] Header safe: 0x50, 0, 0x5, 0x1
Mon Jul  8 15:01:37 2019 [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mon Jul  8 15:01:37 2019 [DEBUG] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mon Jul  8 15:01:37 2019 [DEBUG] Total datum size: 0x001c (28) bytes
Mon Jul  8 15:01:37 2019 [DEBUG] Datum entry type: 0
Mon Jul  8 15:01:37 2019 [DEBUG]    `--> ENTRY TYPE UNKNOWN 1
Mon Jul  8 15:01:37 2019 [DEBUG] Datum value type: 21
Mon Jul  8 15:01:37 2019 [DEBUG] Status: 0x1
Segmentation fault
@RaviKavaiya

This comment has been minimized.

Copy link

@RaviKavaiya RaviKavaiya commented Jul 8, 2019

@benmacdermott as far as I know, there is no change in encryption mechanism of BitLocker in v1903(18362).

Because, from v1511, they introduced the new XTS mechanism. After that, I haven't experienced any change till now.

But, looking at @Tom9876 's comment, he says he is able to work with dislocker in v1809, but not in v1903.
So yes, your guess seems legitimate...

(One more thing : Wrap your Error log in 'code', so that the dev. can see it properly)

@benmacdermott

This comment has been minimized.

Copy link

@benmacdermott benmacdermott commented Jul 8, 2019

Thanks Ravi. So can I take it to mean that you're not on 1903? I'm just trying to establish whether this is a general issue or specific to a subset of users.

Thanks for the formatting tip - I had hoped it was sufficiently legible but I've updated now.

@Tom9876

This comment has been minimized.

Copy link
Author

@Tom9876 Tom9876 commented Jul 8, 2019

@RaviKavaiya I don't think that the encryption mechanism has changed. As I mentioned in my original post I have no problems mounting the 1903 partition with bdemount (of course ro). It must be something different. Perhaps in the "configuration table" of the bitlocker partition?

@RaviKavaiya

This comment has been minimized.

Copy link

@RaviKavaiya RaviKavaiya commented Jul 9, 2019

@benmacdermott I am on Windows 10 v1903.
@Tom9876 , same to you. In 1903, I can also mount with bdemount (readonly)

@RaviKavaiya

This comment has been minimized.

Copy link

@RaviKavaiya RaviKavaiya commented Jul 11, 2019

Any update on this?

@mrezqi

This comment has been minimized.

Copy link

@mrezqi mrezqi commented Jul 16, 2019

Hi, the same thing occured to me. Any update on this?
dislocker_segmentation_fault.txt

@soumyamahunt

This comment has been minimized.

Copy link

@soumyamahunt soumyamahunt commented Jul 23, 2019

Same issue on 1903, any update will be appreciated.

@haobinnan

This comment has been minimized.

Copy link
Contributor

@haobinnan haobinnan commented Jul 24, 2019

@Tom9876
The issue is fixed, please refer to: https://github.com/haobinnan/dislocker

@haobinnan

This comment has been minimized.

Copy link
Contributor

@haobinnan haobinnan commented Jul 24, 2019

@soumyamahunt
The issue is fixed, please refer to: https://github.com/haobinnan/dislocker

@h-vetinari

This comment has been minimized.

Copy link

@h-vetinari h-vetinari commented Jul 24, 2019

@haobinnan
Thanks for fixing this. Can you please turn that commit into a pull request against this repo, so that @Aorimn @mhogomchungu @entetex @ageis can review it and merge it into the main repo?

@haobinnan

This comment has been minimized.

Copy link
Contributor

@haobinnan haobinnan commented Jul 24, 2019

already pulled the request. Waiting for merging it to the main.

@h-vetinari

This comment has been minimized.

Copy link

@h-vetinari h-vetinari commented Jul 24, 2019

OK, cool. Xref #187

@Tom9876

This comment has been minimized.

Copy link
Author

@Tom9876 Tom9876 commented Jul 27, 2019

@haobinnan,
thanks for the patch. Works fine on my systems. Kudos
@Aorimn,
thanks including it in the develop branch

@soumyamahunt

This comment has been minimized.

Copy link

@soumyamahunt soumyamahunt commented Aug 16, 2019

Thanks for fixing it. Any comment on when it will be available in Debian repos, so i can use it in Tails.

@matinwd

This comment has been minimized.

Copy link

@matinwd matinwd commented Oct 13, 2019

still does not work....

@matinwd

This comment has been minimized.

Copy link

@matinwd matinwd commented Oct 13, 2019

@haobinnan did u fix this? how can i know my dislocker version is your's?

@Tom9876

This comment has been minimized.

Copy link
Author

@Tom9876 Tom9876 commented Oct 13, 2019

@matinwd
you have to checkout the "develop" version. For me it works fine on my different systems. E.g. "dislocker --help" shows the version you use.

@Marvo2011

This comment has been minimized.

Copy link

@Marvo2011 Marvo2011 commented Nov 11, 2019

Please update official apt and brew repos... Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.