I think that the contents of this mail can interest somebody here in the list :)

I will have to send a mail about the development guidelines for radare2, the
end of life of radare1 and the further work i have in mind for radare3. Yep
we're in the middle of the balance ;)

In few works..the main idea is that radare1 will keep as it is, no more development
unless bugfixes

radare2 will be a completely new core rewritten from scratch, actually it is starting to work, but obviously 2 years of monolithic development cannot be replaced by a proper refactored modules in a month, so you can still using radare1 for all your needs, and feel free to report bugs, clean warnings, etc.. i will try to keep the
radare1 core available

the new radare2 framework is getting a pretty good design, but im missing some stuff and this will be delegated for radare2 for various reasons. basically I think that having radare1 up and running allow me to get a global idea of what we need and how we need to do it. Now its time for refactoring these ideas. and radare3 will be mostly compatible with radare2, but with enhaced capabilities for multithreading and paralel processing to support multiple processors, cuda, and clustering to be used
from the core.

For this last point i need to reach radare2 framework stabilized and start working
on paralelized platforms to make the new design as well as possible.

PD: Maybe radare4 will be then redesigned for quantum computers :P

--pancake
--- Begin Message ---
Hello Pancake,

Sure add it to the mail list.
I am not a big fan of mailing lists myself to be honest.
As I always get a lot of spam I am not interested in ;)
Anyway, sure forward it.
I understand that it would not be compatible. But I am a bit scared to write 
this plugin and then lose the power.
As I am planning to make a Cheap-RipOff of the Hexrays Pseudo Code Plugin (Your 
Pseudo code is nice, But I want to add ifs etc ;) just for fun. ^^)
Anyway I bet you have loads of fun coding this.

We'll be in contact ;)

Oh and about the gui, please never focus on it!
Make the core ;) and then look at a gui if you have spare time ;) 
Since this way you can use it over SSH ^^ (When I am bored at work/school that 
is ;))

I'll order a Book on lul asap and I will read the Crackme Radare Tutorials.
Thanks! ;) (yes, AGAIN!)

Cheers for now,
Robin


> Date: Tue, 3 Feb 2009 15:46:49 +0100
> From: [email protected]
> To: [email protected]
> Subject: Re: Radare
> 
> Robin Vossen wrote:
> > Hey Pancake,
> >
> > Thanks for the fast responses.
> > Thanks for the link you gave me, I really want to use Radare as a 
> > replacement for my normal Suit (IDA (finding were to Patch), 
> > Olly(Getting the Opcodes), HxD(HexEditor to patch))
> with ida you can do all the job, th eproblem is that that to write in a 
> file you have to manually
> modify the cofnigruation file. you can also make it visualize the bytes 
> of each opcode in
> options->preferences or so.. but imho is quite hard decision by ida guys 
> to disable
> these options by default
> 
> > Radare is so much cheaper and more stable then IDA. (heh)
> yeah, but users want GUIs :P no matter how much they cost
> 
> > Anyway, when I did manage to do the patch with Radare I think I would 
> > understand it. And thus I will start developing Plugins for Radare.
> There are some chapters in the radare book explaining how to write 
> plugins or extensions for it.
> 
> > Ive got some neat ideas, In what language would you develop them? (As 
> > I want to be compatable with Radare2 aswell ;) so If I would use Perl 
> > for the plugin I would want to make sure it will work in Radare2 
> > aswell with not to much ScriptHacking ;))
> well. in radare2 all the internal stuff will be quite different. so, all 
> the binary plugins will be
> incompatible, the only mostly compatible stuff will be the scripting 
> language and most of
> the commands. But if you write a perl, lua or python script run inside 
> radare you will
> probably need to rewrite it unless your script stills using the low 
> level cmd interface. this is
> 
> in python:
>   foo = r.cmd("pd 20") 
> 
> so, you get in foo the output of the command.  the rest of the scripting 
> API will be different
> in radare2, because now we are defining a complete internal API and all 
> the scripting bindings
> will use it directly.
> 
> > Anyway, I think you should not make Radare TO easy. As a Unix way is a 
> > great way to work. And fast when you get it.
> > Maybe you want to do a Deamon Mode. So its easy to make a Frontend 
> > (3th Party) if someone would please.
> Well. this is one of the limitations of the design of radaer1, as 
> radare2 is implemented in multiple
> libraries, all plugins can have access to this api. So no need for 
> daemon modes or so.
> 
> radare in daemon mode can be done in multiple ways:
> 
>  - using the remote api (opening the listen://:9999 uri for example)
>  - using scripts and fifos (see below)
>  - launching a python script from inside. (read scripts/radapy.py for 
> example)
> 
> i have just written these two stupid shellscripts to use radare in batch 
> mode. having one
> instnace running and feeding it with commands from any other program or 
> shell:
> 
> $ cat run-daemon.sh
> #!/bin/sh
> rm -f a b
> mkfifo a
> while : ; do
>         cat a
> done | radare -d ls
> 
> $ cat run-command.sh
> #!/bin/sh
> printf "magic" > b
> #echo "COMMAND: '$1 > b'"
> echo "$1 > b" > a
> while [ "magic" = "`cat b`" ]; do
>         # wait here
>         true
> done
> cat b ; rm b
> 
> i will probably commit it before the end of the day.. i have other 
> things to do before this :P
> 
> but well. you get the idea of how it works..
> 
> > But then you can just focus on your CoreCode.
> >
> The new design allows to completely split the requirements of each 
> module of the core,
> so no more limitations or problems for extending it.
> 
> The next rewrite (r3) will be focusing on the multithreading support. 
> allowing paralel computing,
> cuda, and so on..but atm, r2 needs to be done. r1 has some limitations 
> because of some
> bad design decissions. But it is quite hacky and funny to use and i get 
> lot of fun developing it :)
> 
> so i think its a nice piece of software, but of course , nothing is 
> never perfect at all ;)
> > Again thanks for your wonderfull tool ^^
> hehe ;) thanks
> 
> PD: can i fwd this mail and continue the discussion in the mailing list? 
> i think that can be
> interesting for other people.
> 
> i hope you enjoy it :)
> 
> --pancake

_________________________________________________________________
See all the ways you can stay connected to friends and family
http://www.microsoft.com/windows/windowslive/default.aspx

--- End Message ---
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org

Reply via email to