Hello,

On Thu, Feb 26, 2015 at 11:27:11AM +0100, Federico Maggi wrote:
> > For the practical purposes if you need tracing right now, I suggest
> > not using OpenOCD at all and instead learn the ETM/ETB configuration
> > and dumping facilities already provided by Linux, the kernel.
> 
> This is interesting, although it may lead to artifacts on the host. The
> assumption of Rodrigo's work (which I'm supervising) is that the traced 
> process
> may be effectively trying to fingerprint the environment for signs of being
> monitored. For instance, assuming that I'm working in kernel space, I'm
> wondering how the collected trace could be transferred outside the host for
> subsequent analysis, without leaving evidence. As I'm not a kernel hacker, I 
> see
> that we could write to a serial port or something else and then read from it
> from a separate machine.

I think if the traced process is running in its own container (or even
a VM), it has absolutely no way to tell if it's being traced or
not. The trace data can be transferred by whatever means, that might
be an http daemon or netcat or usb mass storage or serial, anything
you want would work about the same afaict, a process inside a
container wouldn't be able to see it anyway.

Good luck with your research! Feel free to publish a link here once
you have a preprint ready :)

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to