Set Up dm-crypt Based Encrypted Block Devices
cryptsetup is used to conveniently set up dm-crypt based device-mapper
targets. It allows to set up targets to read cryptoloop compatible
volumes as well as LUKS formatted ones. The package additionally
includes support for automatically setting up encrypted volumes at boot
time via the config file /etc/crypttab.
- Developed at security
-
9
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory/cryptsetup && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
baselibs.conf | 0000000037 37 Bytes | |
cryptsetup-2.3.6.tar.sign | 0000000833 833 Bytes | |
cryptsetup-2.3.6.tar.xz | 0011154148 10.6 MB | |
cryptsetup-rpmlintrc | 0000000234 234 Bytes | |
cryptsetup.changes | 0000073901 72.2 KB | |
cryptsetup.keyring | 0000003284 3.21 KB | |
cryptsetup.spec | 0000006790 6.63 KB |
Revision 114 (latest revision is 128)
- cryptsetup 2.3.6: * integritysetup: Fix possible dm-integrity mapping table truncation. * cryptsetup: Backup header can be used to activate TCRYPT device. Use --header option to specify the header. * cryptsetup: Avoid LUKS2 decryption without detached header. This feature will be added later and is currently not supported. * Additional fixes and workarounds for common warnings produced by some static analysis tools (like gcc-11 analyzer) and additional code hardening. * Fix standalone libintl detection for compiled tests. * Add Blake2b and Blake2s hash support for crypto backends. Kernel and gcrypt crypto backend support all variants. OpenSSL supports only Blake2b-512 and Blake2s-256. Crypto backend supports kernel notation e.g. "blake2b-512".
Comments 0