Those configuration vars have been removed from r2 because it was
implemented inside "rarun2".
The idea behind that tool is that you can write execution profiles
for the programs you want to run and all this functionality can be
used outside r2, as a system tool. those options are:
- bind a filedescriptor to files or sockets (connect, listen ,..)
- set argument (and allow to get contents of a file as argument)
- preload libraries (osx, bsd, gnu)
- kill program after N seconds
- chroot
- setuid/setgid
- environment vars
This way you can easily write a profile that defines the whole running
environment, to automate fuzzing or debugging processes with different
priviledges or so.
You may also like to know that you can run a process on a different
xterm and debug it on your current terminal.
- open new terminal and type 'tty'
- r2 -d rarun2 stdio=/dev/pts/8 program=/bin/ls
- party hard
--pancake
On 06/20/13 21:22, the wrote:
Hi, It's me again))
I have a problem with variable child.stdio.
I have read about this variable in the radare pdf, radare2 doesn't
recognize it. Is this a bug or did the variable name change since then?
$ r2 -e child.stdio=/dev/pts/1 -d /bin/ls
r_config_set: variable 'child.stdio' not found
Process with PID 3057 started...
PID = 3057
r_config_set: variable 'child.stdio' not found
r_debug_select: 3057 3057
r_config_set: variable 'child.stdio' not found
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
