[Eresi-cvs] Fwd: [eresi-crew] eresi gui module

[Julien Vanegue]

---------- Forwarded message ----------
From: Julien Vanegue <jvanegue at gmail.com>
Date: Tue, Jun 23, 2009 at 7:29 PM
Subject: Re: [eresi-crew] eresi gui module
To: zadig bru <zadig.bru at gmail.com>


Hi Zadig and thanks for your efforts on improving ERESI!

Your approach is interesting because it doesnt sacrify portability. On the
other hand as you mention, performance is not going to be very good. So if I
understand well, the server side make use of a mini-http server embedded
into an ERESI module ? That sounds very interesting.. I cant wait  to see a
web-based solution for reverse engineering with ERESI, especially the part
about graphs, organizing graphs dumped on disk, being able to browse
functions's graph more easily etc.. Since you already support the handling
of symbol table, remember you can always know the list of blocks or
functions in the graph via the symtab with STT_BLOCK and STT_FUNC syms...
that make things easier to manage from your module .. I guess.

I believe for now its a good idea to focus on elfsh rather than the whole
ERESI, thats already a big part (and some commands are shared with other
tools anyway, such as the graph command). Kernsh and Etrace would also be
good targets for such an interface, but I guess they need some improvements
before thinking of the interface..

A feature I would definitely like to see in there is the ability to upload a
binary from the browser, analyze it on the server side, and see the result
from the browser. Is it what you are doing ?

Let us know of the advances definitely.

Julien



On Tue, Jun 23, 2009 at 12:07 PM, zadig bru <zadig.bru at gmail.com> wrote:

> Hello everybody,
>
> Some of you already heard me talking about a gui for eresi. After a
> long time I finally started working a little bit on it.
> I would like to have some feedback before continuing the way I
> choosed. Here is a paper about it:
>
> http://reveng.110mb.com/papers/2009/1-everest/index.php
>
> You will find in it all the reasons why I choose this architecture.
>
> Zadig.
>
> _______________________________________________
> eresi-crew mailing list
> eresi-crew at lists.einherjar.de
> http://lists.einherjar.de/mailman/listinfo/eresi-crew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.einherjar.de/pipermail/eresi-cvs/attachments/20090623/0848d8cd/attachment.html>