On Wednesday 04 November 2020 08:34:00 am Slávek Banko via tde-users wrote: > On Wednesday 04 of November 2020 13:06:32 Janek Stolarek wrote: > > > > Somehow I imagined/hoped that R14.0.9 will be followed by R14.1.0. What > > is the roadmap for the R14.1.0 release? I am eagerly awaiting support > > for decrypting encrypted external drives, which I believe Michele is > > working on as part of R14.1.0. > > Yes, support for unlocking / locking encrypted disks is one of the things > that will be in R14.1.0. If you want to test it, you can consider using > the PTB repository => Preliminary Testing Builds, which is based on the > master branch. I've been using LUKS for a long time on several different distributions, all with TDE installed. So this conversation has made me curious how TDE having ‘support for unlocking / locking encrypted disks’ is different than what is currently in use? Current usage: root keyfile {optional for non-root drives, must use passkey on root drive*} /etc/crypttab /etc/fstab And AFAIK, that works for any drive (USB or otherwise) ‘see-able’ by the system. How’s the TDE process going to look? Will it interfere with current usage of LUKS? (Seriously don’t want all my drives to just ‘stop working!’) Thanks, Michael * That’s not technically true, there are some hybrid USB holds the passkey methodologies. (Granted you’d probably want to store the USB in a safe. And how paranoid do you have to be to not let an employee be able to unlock their system by themselves....) ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx