From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: dm-crypt@saout.de
Subject: [dm-crypt] Looking for reverse-engineering partner for DiskCryptor
Date: Thu, 3 Jun 2021 12:05:28 +0200 [thread overview]
Message-ID: <7d911d89-aea8-5d2b-65c4-051de6f54955@o2.pl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1274 bytes --]
Hello,
I'm trying to implement support for opening DiskCryptor partitions. DiskCryptor
is licensed under GPLv3, which is incompatible with libcryptsetup's LGPL2+. I'd
therefore prefer not to read DiskCryptor source code. I'm asking for someone to
do this and provide some information - mostly about header encryption ATM.
I tried to reverse-engineer the format from public info:
* https://diskcryptor.org/volume/
* https://security.stackexchange.com/a/83792
and by trial and error, but failed.
I've tried the following (with many variations) on a FAT partition encrypted
with AES:
1. Password is encoded as an ASCII string.
2. This ASCII string is hashed with PBKDF2 with the following parameters:
* hash: sha512
* salt - 64 bytes from start of the volume header,
* output size: 64 or perhaps 192 bytes,
* 1000 iterations.
3. Encryption key consists of the first or perhaps last 64 bytes (512 bits) of
the output of PBKDF2.
4. Bytes 64 - 2048 of the header are encrypted with AES cipher in XTS mode:
* decryption starts from byte 64,
* IV is 16 bytes long.
Code could be found at https://github.com/DavidXanatos/DiskCryptor/ . Thank you
in advance.
Greetings,
Mateusz Jończyk
[-- Attachment #1.2: Type: text/html, Size: 2216 bytes --]
[-- Attachment #2: Type: text/plain, Size: 147 bytes --]
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
next reply other threads:[~2021-06-03 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 10:05 Mateusz Jończyk [this message]
2021-06-03 10:45 ` [dm-crypt] Re: Looking for reverse-engineering partner for DiskCryptor Milan Broz
2021-06-03 13:48 ` Mateusz Jończyk
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=7d911d89-aea8-5d2b-65c4-051de6f54955@o2.pl \
--to=mat.jonczyk@o2.pl \
--cc=dm-crypt@saout.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).