From: Martin Steigerwald <martin@lichtvoll.de>
To: Paul van der Vlis <paul@vandervlis.nl>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Re-use SSD
Date: Fri, 22 Sep 2017 13:27:37 +0200 [thread overview]
Message-ID: <3513783.r4zieL0AEN@merkaba> (raw)
In-Reply-To: <oq2pgm$jkv$1@blaine.gmane.org>
Paul van der Vlis - 22.09.17, 12:43:
> Op 14-09-17 om 15:21 schreef Martin Steigerwald:
> > Hello Paul.
> >
> > Paul van der Vlis - 14.09.17, 14:32:
> >> I have bought many laptops with privacy-sensitive data on /home in
> >> ecryptfs on the SSD. And I have promised to carefull remove the data
> >> before re-using.
> >>
> >> What would you advice to do? Is it possible to overwrite the master key
> >> for example? Or is it a good idea to change the passphrase in a very
> >> long one?
> >
> > Technically you can´t really overwrite it. SSDs use Copy on Write.
> >
> > Also I think the passphrase in Ecryptfs just encrypts a key used to
> > encrypt
> > the data… not the data itself.
> >
> >
> > Generic hint for securely erasing SSDs.
> >
> > https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase
>
> This is what I am doing now. The SSD's I've tried are normally freezed,
> but after awaking from suspend-to-ram not anymore.
>
> It looks complex, but it's fast and doable. But indeed not nice to rely
> on the firmware of the SSD...
>
> What I would like are stupid-SSD's without a controller, where the
> filesystem does everything. Or a SSD with open source controller firmware.
Yep.
Open Channel SSDs. But well, I never seen anything like that for laptops or
other kind of consumer hardware.
Then add to it Coreboot or even Libreboot.
This ThinkPad T520 still has Intel Crapware^W Management Engine on it. I
disabled it in the firmware settings… but… I know it can be removed meanwhile…
but as it is not my laptop, I just update the BIOS/UEFI firmware once in a
while. But there are rarely any new updates. So I bet that TCP/IP stack in IME
has a ton of unfixed security issues by now.
Free hardware… thats the next revolution!
Thanks,
--
Martin
prev parent reply other threads:[~2017-09-22 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 12:32 Re-use SSD Paul van der Vlis
[not found] ` <f34084a3-159d-e580-d199-ecf6acf345ff@aron.ws>
2017-09-14 13:03 ` Paul van der Vlis
2017-09-14 13:21 ` Martin Steigerwald
2017-09-14 13:38 ` Martin Steigerwald
2017-09-22 10:43 ` Paul van der Vlis
2017-09-22 11:27 ` Martin Steigerwald [this message]
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=3513783.r4zieL0AEN@merkaba \
--to=martin@lichtvoll.de \
--cc=ecryptfs@vger.kernel.org \
--cc=paul@vandervlis.nl \
/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).