[Hackrf-dev] hackrf_transfer -t issues?

[Mudge Zatko]

Thanks Mike.

Any idea when (if?) this will be looked into?

GRC is cool and all, but part of the allure of HackRF (at least to me) is
the ability to perform meaningful replay and mutation fuzzing from a
minimalistic unix environment.

To that end, hackrf_transfer -t would look to be ideal in quickly enabling
some initial  security analysis of various receiver codecs.

Or perhaps there's another alternative to transfer -t that you or someone
else on the list is aware of they could point me to in the meantime?

thanks again,

.mudge





On Fri, Aug 30, 2013 at 7:45 AM, Michael Ossmann <mike at ossmann.com> wrote:


> On Tue, Aug 27, 2013 at 08:52:32AM -0700, Mudge Zatko wrote:

> >

> > has anyone had luck with replaying captured signals via

> > hackrf_transfer -t?

>

> There is definitely a bug:

>

> https://github.com/mossmann/hackrf/issues/91

>

> I haven't had a chance to look for the root cause yet.

>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20130830/76e27692/attachment.htm