[eresi-dev] My annoucement

simkin aka.simkin at gmail.com
Mon Sep 24 15:45:14 UTC 2007


hi, sorry for not saying this sooner but i can't keep on with the code,
im going to start to work next month and i won't have enough time for it.
however i think i'll be interested on the project and perhaps
also in coding something again in the future when i have more time.
i expect that my code has been of some help.
thanks. good luck with the project, im sure it will be a very good software.

bye


2007/9/22, jv at ens dot fr <julien.vanegue at ens.fr>:
>
> Good afternoon
>
> Today Thomas Garnier is leaving the project.
>
> Once more the project team has to renew.
>
> As Thomas explained, both himself and the
> ERESI project has switched of central interest.
> ERESI started as a pure security project and
> has turned into a  research project applied to
> security. While it may give us less popularity, it
> brings us more academic and industrial perspectives
> in the future.
>
> As in every project, ERESI has to evolve for surviving.
>
> When I started the ELFsh project 6 years ago and
> a half ago, I would have never imagined it could
> reach this level of development. Soon, I got great
> help from Sebastien Roy who developed the original
> libasm for the INTEL architecture.
>
> As we were meeting more and more people in events
> where ELFsh was getting presented, new people got
> a lot of interest and became contributors. That was
> the case of security researchers known as kil3r, grugq,
> or yannmalcom, giving a hand on some code and having
> fun with us at every events and conference we presented,
> acted, or even organized.
>
> For almost 2 years now, the project has been handled in
> a more professional manner. Rafal Lesniak has done a
> remarkable job on administrating the website server, opening
> the bugtracking system, and setting up the web CVS. Thanks
> to this organization, it made it possible for more people to join
> our collective and community effort, and we could reach a high
> level of development alltogether. Julio Auto is doing a great job
> on the topic of code analysis, and more recently Anthony Desnos
> has started his effort on kernel-level analysis, which can as well
> benefit from all our previous work on static and runtime analysis,
> thanks to the architecture of the ERESI project which has always
> been toward providing ultimate code reusability.
>
> Thomas will be a great loss for the project without a doubt,
> but I have faith in the future of ERESI. As a project leader, I
> have always welcomed and received serious collaborators
> propositions very seriously, and even if I can sound as lacking
> so much diplomacy in public sometimes, I always kept a
> necessary distance for handling even beginner contributors
> (if they really give at least a little feedback in the first times).
> When Thomas started to develop ERESI, he was a beginner
> in C programming. No doubt that he has made so much
> improvements since then. I am sure this evolution was due
> only to his hard work, but I am happy to see that he appreciated
> all the time we spent on IRC talking about experiences in the
> computer security community. I will always support Thomas
> for his future projects and I personally do not exclude to work again
> with him in the future on other projects if we can find agreement
> on our collective needs.
>
> The new cycle of ERESI is starting. ERESI is developped by the ERESI
> team, by alphabetical order: Julio Auto, Anthony Desnos, Rafal Lesniak,
> Sebastien Roy, and Julien Vanegue. We will continue developping and
> presenting our work in conferences and journals like we did in the past.
>
> We look forward to the next 6 years
>
> Happy reversing
>
> Julien Vanegue
>
>
>
> _______________________________________________
> eresi-dev mailing list
> eresi-dev at lists.einherjar.de
> http://lists.einherjar.de/mailman/listinfo/eresi-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.einherjar.de/pipermail/eresi-dev/attachments/20070924/770cb31b/attachment.html 


More information about the eresi-dev mailing list