PNG  IHDR* pHYs+ IDATx]n#; cdLb Ǚ[at¤_:uP}>!Usă cag޿ ֵNu`ݼTâabO7uL&y^wFٝA"l[|ŲHLN밪4*sG3|Dv}?+y߉{OuOAt4Jj.u]Gz*҉sP'VQKbA1u\`& Af;HWj hsO;ogTu uj7S3/QzUr&wS`M$X_L7r2;aE+ώ%vikDA:dR+%KzƉo>eOth$z%: :{WwaQ:wz%4foɹE[9<]#ERINƻv溂E%P1i01 |Jvҗ&{b?9g=^wζXn/lK::90KwrюO\!ջ3uzuGv^;騢wq<Iatv09:tt~hEG`v;3@MNZD.1]L:{ծI3`L(÷ba")Y.iljCɄae#I"1 `3*Bdz>j<fU40⨬%O$3cGt]j%Fߠ_twJ;ABU8vP3uEԑwQ V:h%))LfraqX-ۿX]v-\9I gl8tzX ]ecm)-cgʒ#Uw=Wlێn(0hPP/ӨtQ“&J35 $=]r1{tLuǮ*i0_;NƝ8;-vݏr8+U-kruȕYr0RnC]*ެ(M:]gE;{]tg(#ZJ9y>utRDRMdr9㪩̞zֹb<ģ&wzJM"iI( .ꮅX)Qw:9,i좜\Ԛi7&N0:asϓc];=ΗOӣ APqz93 y $)A*kVHZwBƺnWNaby>XMN*45~ղM6Nvm;A=jֲ.~1}(9`KJ/V F9[=`~[;sRuk]rєT!)iQO)Y$V ی ۤmzWz5IM Zb )ˆC`6 rRa}qNmUfDsWuˤV{ Pݝ'=Kֳbg,UҘVz2ﴻnjNgBb{? ߮tcsͻQuxVCIY۠:(V뺕 ٥2;t`@Fo{Z9`;]wMzU~%UA蛚dI vGq\r82iu +St`cR.6U/M9IENDB`Cryptsetup 2.3.2 Release Notes ============================== Stable bug-fix release. All users of cryptsetup 2.x should upgrade to this version. Changes since version 2.3.1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Support compilation with json-c library version 0.14. * Update FAQ document for some LUKS2 specific information. * Add option to dump content of LUKS2 unbound keyslot: cryptsetup luksDump --unbound -S or optionally with --master-key-file option. The slot number --key-slot (-S) option is mandatory here. An unbound keyslot store a key is that is not assigned to data area on disk (LUKS2 allows to store arbitrary keys). * Rephrase some error messages and remove redundant end-of-lines. * Add support for discards (TRIM) for standalone dm-integrity devices. Linux kernel 5.7 adds support for optional discard/TRIM operation over dm-integrity devices. It is now supported through --allow-discards integritysetup option. Note you need to add this flag in all activation calls. Note that this option cannot be used for LUKS2 authenticated encryption (that uses dm-integrity for storing additional per-sector metadata). * Fix cryptsetup-reencrypt to work on devices that do not allow direct-io device access. * Fix a crash in the BitLocker-compatible code error path. * Fix Veracrypt compatible support for longer (>64 bytes) passphrases. It allows some older images to be correctly opened again. The issue was introduced in version 2.3.1.