From: Richard Weinberger <richard.weinberger@gmail.com>
To: coreassumption <coreassumption@protonmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: securely wipe sensitive data from mtd?
Date: Sun, 24 Feb 2019 10:20:54 +0100 [thread overview]
Message-ID: <CAFLxGvwVGFs-6gtYXb1Nba6RE3Nx2hx03kmWziET6aaXcK=6hA@mail.gmail.com> (raw)
In-Reply-To: <cMCf6e-7A9hCUl29t7xLtWy9cUfo7cj7Wr1L1i47ZnErTNqBquZ-tGlHbUNaL8L1MCId_0Ke0x9eV0tOfG-hN0ytN6m3lBb0XTxAOQFP8OQ=@protonmail.com>
On Sun, Feb 24, 2019 at 9:04 AM coreassumption
<coreassumption@protonmail.com> wrote:
>
> What is the proper way to clean a mtd of any sensitive data that may be located on them (NOR and NAND)?
>
> Would flashing a new image via uBoot be enough? Or would the wear leveling mechanism prevent this from clearing everything?
>
> Would writing 0's from a running OS's be sufficient? Or is the device 'smart' and not write zero streams?
This is not how flash works. You cannot overwrite anything.
> Are multiple passes of writing suggested or is this just a holdover from myths of magnetic mediums?
Well, if you do a block erase the data should be gone. But you can
never be sure that the flash chip really does.
So, like for any other storage type, encrypt the data and throw the
key away. :-)
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-02-24 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 8:04 securely wipe sensitive data from mtd? coreassumption
2019-02-24 9:20 ` Richard Weinberger [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='CAFLxGvwVGFs-6gtYXb1Nba6RE3Nx2hx03kmWziET6aaXcK=6hA@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=coreassumption@protonmail.com \
--cc=linux-mtd@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.