mirror of
https://gitlab.com/cryptsetup/cryptsetup.git
synced 2025-12-06 00:10:04 +01:00
Update URLs (->gitlab.com).
The code.google is going to be abandoned. Thank you you for all the fish.
This commit is contained in:
11
FAQ
11
FAQ
@@ -23,7 +23,7 @@ A. Contributors
|
|||||||
with one master key, anti-forensic features, metadata block at
|
with one master key, anti-forensic features, metadata block at
|
||||||
start of device, ...). The latest version of this FAQ should
|
start of device, ...). The latest version of this FAQ should
|
||||||
usually be available at
|
usually be available at
|
||||||
http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions
|
https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions
|
||||||
|
|
||||||
|
|
||||||
* 1.2 WARNINGS
|
* 1.2 WARNINGS
|
||||||
@@ -173,7 +173,7 @@ A. Contributors
|
|||||||
|
|
||||||
* 1.6 Where is the project website?
|
* 1.6 Where is the project website?
|
||||||
|
|
||||||
There is the project website at http://code.google.com/p/cryptsetup/
|
There is the project website at https://gitlab.com/cryptsetup/cryptsetup/
|
||||||
Please do not post questions there, nobody will read them. Use
|
Please do not post questions there, nobody will read them. Use
|
||||||
the mailing-list instead.
|
the mailing-list instead.
|
||||||
|
|
||||||
@@ -1993,7 +1993,7 @@ A. Contributors
|
|||||||
process, except generating a new LUKS header with the old master
|
process, except generating a new LUKS header with the old master
|
||||||
key (it prints the command for that though):
|
key (it prints the command for that though):
|
||||||
|
|
||||||
http://code.google.com/p/cryptsetup/source/browse/misc/luks-header-from-active
|
https://gitlab.com/cryptsetup/cryptsetup/blob/master/misc/luks-header-from-active
|
||||||
|
|
||||||
You can also do this manually. Here is how:
|
You can also do this manually. Here is how:
|
||||||
|
|
||||||
@@ -2091,7 +2091,7 @@ http://code.google.com/p/cryptsetup/source/browse/misc/luks-header-from-active
|
|||||||
bulk data at 0x200000.
|
bulk data at 0x200000.
|
||||||
|
|
||||||
The exact specification of the format is here:
|
The exact specification of the format is here:
|
||||||
http://code.google.com/p/cryptsetup/wiki/Specification
|
https://gitlab.com/cryptsetup/cryptsetup/wikis/Specification
|
||||||
|
|
||||||
For your convenience, here is the LUKS header with hex offsets.
|
For your convenience, here is the LUKS header with hex offsets.
|
||||||
NOTE: The spec counts key-slots from 1 to 8, but the cryptsetup
|
NOTE: The spec counts key-slots from 1 to 8, but the cryptsetup
|
||||||
@@ -2458,8 +2458,7 @@ offset length name data type description
|
|||||||
* Specifications
|
* Specifications
|
||||||
|
|
||||||
- LUKS on-disk format spec:
|
- LUKS on-disk format spec:
|
||||||
http://code.google.com/p/cryptsetup/wiki/Specification
|
https://gitlab.com/cryptsetup/cryptsetup/wikis/Specification
|
||||||
|
|
||||||
|
|
||||||
* Code Examples
|
* Code Examples
|
||||||
|
|
||||||
|
|||||||
8
README
8
README
@@ -5,11 +5,11 @@ setup cryptographic volumes for dm-crypt (including LUKS extension)
|
|||||||
|
|
||||||
WEB PAGE:
|
WEB PAGE:
|
||||||
|
|
||||||
http://code.google.com/p/cryptsetup/
|
https://gitlab.com/cryptsetup/cryptsetup/
|
||||||
|
|
||||||
FAQ:
|
FAQ:
|
||||||
|
|
||||||
http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions
|
https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions
|
||||||
|
|
||||||
MAILING LIST:
|
MAILING LIST:
|
||||||
|
|
||||||
@@ -22,8 +22,8 @@ DOWNLOAD:
|
|||||||
|
|
||||||
SOURCE CODE:
|
SOURCE CODE:
|
||||||
|
|
||||||
URL: http://code.google.com/p/cryptsetup/source/browse/
|
URL: https://gitlab.com/cryptsetup/cryptsetup/tree/master
|
||||||
Checkout: git clone https://code.google.com/p/cryptsetup/
|
Checkout: git clone https://gitlab.com/cryptsetup/cryptsetup.git
|
||||||
|
|
||||||
NLS (PO TRANSLATIONS):
|
NLS (PO TRANSLATIONS):
|
||||||
|
|
||||||
|
|||||||
@@ -56,7 +56,7 @@
|
|||||||
* in a persistent way on the device. Keyslot area is an array beyond LUKS header, where
|
* in a persistent way on the device. Keyslot area is an array beyond LUKS header, where
|
||||||
* volume key is stored in the encrypted form using user input passphrase. For more info about
|
* volume key is stored in the encrypted form using user input passphrase. For more info about
|
||||||
* LUKS keyslots and how it's actually protected, please look at
|
* LUKS keyslots and how it's actually protected, please look at
|
||||||
* <A HREF="http://code.google.com/p/cryptsetup/wiki/Specification">LUKS specification</A>.
|
* <A HREF="https://gitlab.com/cryptsetup/cryptsetup/wikis/Specification">LUKS specification</A>.
|
||||||
* There are two basic methods to create a new keyslot:
|
* There are two basic methods to create a new keyslot:
|
||||||
*
|
*
|
||||||
* @subsection ckeyslot_vol crypt_keyslot_add_by_volume_key()
|
* @subsection ckeyslot_vol crypt_keyslot_add_by_volume_key()
|
||||||
|
|||||||
@@ -29,7 +29,7 @@
|
|||||||
|
|
||||||
/*
|
/*
|
||||||
* Internal IV helper
|
* Internal IV helper
|
||||||
* IV documentation: https://code.google.com/p/cryptsetup/wiki/DMCrypt
|
* IV documentation: https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt
|
||||||
*/
|
*/
|
||||||
struct crypt_sector_iv {
|
struct crypt_sector_iv {
|
||||||
enum { IV_NONE, IV_NULL, IV_PLAIN, IV_PLAIN64, IV_ESSIV, IV_BENBI } type;
|
enum { IV_NONE, IV_NULL, IV_PLAIN, IV_PLAIN64, IV_ESSIV, IV_BENBI } type;
|
||||||
|
|||||||
@@ -297,7 +297,7 @@ static void hex_key(char *hexkey, size_t key_size, const char *key)
|
|||||||
sprintf(&hexkey[i * 2], "%02x", (unsigned char)key[i]);
|
sprintf(&hexkey[i * 2], "%02x", (unsigned char)key[i]);
|
||||||
}
|
}
|
||||||
|
|
||||||
/* http://code.google.com/p/cryptsetup/wiki/DMCrypt */
|
/* https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt */
|
||||||
static char *get_dm_crypt_params(struct crypt_dm_active_device *dmd, uint32_t flags)
|
static char *get_dm_crypt_params(struct crypt_dm_active_device *dmd, uint32_t flags)
|
||||||
{
|
{
|
||||||
int r, max_size, null_cipher = 0, num_options = 0;
|
int r, max_size, null_cipher = 0, num_options = 0;
|
||||||
@@ -354,7 +354,7 @@ out:
|
|||||||
return params;
|
return params;
|
||||||
}
|
}
|
||||||
|
|
||||||
/* http://code.google.com/p/cryptsetup/wiki/DMVerity */
|
/* https://gitlab.com/cryptsetup/cryptsetup/wikis/DMVerity */
|
||||||
static char *get_dm_verity_params(struct crypt_params_verity *vp,
|
static char *get_dm_verity_params(struct crypt_params_verity *vp,
|
||||||
struct crypt_dm_active_device *dmd)
|
struct crypt_dm_active_device *dmd)
|
||||||
{
|
{
|
||||||
|
|||||||
@@ -35,7 +35,7 @@
|
|||||||
|
|
||||||
#define VERITY_SIGNATURE "verity\0\0"
|
#define VERITY_SIGNATURE "verity\0\0"
|
||||||
|
|
||||||
/* http://code.google.com/p/cryptsetup/wiki/DMVerity#Verity_superblock_format */
|
/* https://gitlab.com/cryptsetup/cryptsetup/wikis/DMVerity#verity-superblock-format */
|
||||||
struct verity_sb {
|
struct verity_sb {
|
||||||
uint8_t signature[8]; /* "verity\0\0" */
|
uint8_t signature[8]; /* "verity\0\0" */
|
||||||
uint32_t version; /* superblock version */
|
uint32_t version; /* superblock version */
|
||||||
|
|||||||
@@ -234,4 +234,4 @@ Copyright \(co 2012-2013 Red Hat, Inc.
|
|||||||
This is free software; see the source for copying conditions. There is NO
|
This is free software; see the source for copying conditions. There is NO
|
||||||
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
The project website at \fBhttp://code.google.com/p/cryptsetup/\fR
|
The project website at \fBhttps://gitlab.com/cryptsetup/cryptsetup\fR
|
||||||
|
|||||||
@@ -1074,13 +1074,13 @@ Copyright \(co 2012-2014 Arno Wagner
|
|||||||
This is free software; see the source for copying conditions. There is NO
|
This is free software; see the source for copying conditions. There is NO
|
||||||
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
The LUKS website at \fBhttp://code.google.com/p/cryptsetup/\fR
|
The LUKS website at \fBhttps://gitlab.com/cryptsetup/cryptsetup/\fR
|
||||||
|
|
||||||
The cryptsetup FAQ, contained in the distribution package and
|
The cryptsetup FAQ, contained in the distribution package and
|
||||||
online at
|
online at
|
||||||
\fBhttp://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions\fR
|
\fBhttps://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions\fR
|
||||||
|
|
||||||
The cryptsetup mailing list and list archive, see FAQ entry 1.6.
|
The cryptsetup mailing list and list archive, see FAQ entry 1.6.
|
||||||
|
|
||||||
The LUKS on-disk format specification available at
|
The LUKS on-disk format specification available at
|
||||||
\fBhttp://code.google.com/p/cryptsetup/wiki/Specification\fR
|
\fBhttps://gitlab.com/cryptsetup/cryptsetup/wikis/Specification\fR
|
||||||
|
|||||||
@@ -137,7 +137,7 @@ Copyright \(co 2012-2014 Milan Broz
|
|||||||
This is free software; see the source for copying conditions. There is NO
|
This is free software; see the source for copying conditions. There is NO
|
||||||
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
The project website at \fBhttp://code.google.com/p/cryptsetup/\fR
|
The project website at \fBhttps://gitlab.com/cryptsetup/cryptsetup\fR
|
||||||
|
|
||||||
The verity on-disk format specification available at
|
The verity on-disk format specification available at
|
||||||
\fBhttp://code.google.com/p/cryptsetup/wiki/DMVerity\fR
|
\fBhttps://gitlab.com/cryptsetup/cryptsetup/wikis/DMVerity\fR
|
||||||
|
|||||||
Reference in New Issue
Block a user