From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: Richard Weinberger <richard.weinberger@gmail.com>,
Andrew Tierney <cybergibbons@cybergibbons.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Gstir <david@sigma-star.at>
Subject: Re: UBIFS recovery/forensics tools
Date: Sun, 27 Sep 2015 10:27:44 +0800 [thread overview]
Message-ID: <56075420.5080303@cn.fujitsu.com> (raw)
In-Reply-To: <CAFLxGvwtq9WF3SL_ZaAYHMsvi4g3B29XwRddKvPyu2YDz2P-hA@mail.gmail.com>
On 09/25/2015 06:26 PM, Richard Weinberger wrote:
> On Fri, Sep 25, 2015 at 11:29 AM, Andrew Tierney
> <cybergibbons@cybergibbons.com> wrote:
>> Hello all,
>>
>> I am a reverse engineer, and I am finding that UBIFS is becoming
>> increasingly common on embedded devices. A common task is recovering
>> file systems from locked down or damaged devices, and I'm finding this
>> very challenging with UBIFS!
>>
>> I have seen talk on here of userspace tools to recover damaged UBIFS
>> systems. Did anything every come of this? I am currently using "ubi
>> reader" ( https://github.com/jrspruitt/ubi_reader ) with some success.
>
> We're currently working on such tools.
> Stay tuned.
Yes, there is already a RFC for ubifs_dump tool,
http://lists.infradead.org/pipermail/linux-mtd/2015-August/061201.html
fsck.ubifs is in developing. Andrew, do you want something like that?
Yang
>
next prev parent reply other threads:[~2015-09-27 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 9:29 UBIFS recovery/forensics tools Andrew Tierney
2015-09-25 10:26 ` Richard Weinberger
2015-09-27 2:27 ` Dongsheng Yang [this message]
2015-09-27 8:37 ` Andrew Tierney
2015-09-27 8:47 ` Richard Weinberger
2015-09-27 9:50 ` Andrew Tierney
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=56075420.5080303@cn.fujitsu.com \
--to=yangds.fnst@cn.fujitsu.com \
--cc=cybergibbons@cybergibbons.com \
--cc=david@sigma-star.at \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
/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.