From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] dc3dd: add new package
Date: Fri, 22 Jun 2018 12:09:14 +0200 [thread overview]
Message-ID: <20180622100914.2rjeeodtdax5j4hz@pengutronix.de> (raw)
In-Reply-To: <1529656004.4757.20.camel@diehl.com>
On Fri, Jun 22, 2018 at 08:26:44AM +0000, Denis OSTERLAND wrote:
> Am Freitag, den 22.06.2018, 09:23 +0200 schrieb Michael Olbrich:
> > > + select LIBC_PTHREAD
> > > + select LIBC
> > > + prompt "dc3dd "
> > > + help
> > > + dc3dd is a patched version of GNU dd with added features for computer forensics.
> > > + It was developed at the DoD Cyber Crime Center by Jesse Kornblum.
> > > +
> > What's the usecase to install two versions of dd? Is dc3dd compatible with
> > coreutils dd? If it is, then I think the whole package should have the
> > 'depends on !...' and no suboption.
> >
> See https://tools.kali.org/forensics/dc3dd
> The usecase is checksum validation while copy.
> We use it for production.
> It seems to be not 100% compatible, at least I miss "bs=" option.
> Shall I remove the link?
I think that would be better.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-06-22 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 13:12 Denis OSTERLAND
2018-06-22 7:23 ` Michael Olbrich
2018-06-22 8:26 ` Denis OSTERLAND
2018-06-22 10:09 ` Michael Olbrich [this message]
2018-06-22 11:15 ` [ptxdist] [PATCH v2] " Denis OSTERLAND
2018-07-24 11:54 ` Denis OSTERLAND
2018-07-25 13:16 ` Michael Olbrich
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=20180622100914.2rjeeodtdax5j4hz@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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