______ __ ______ __ __ __ __ _____ __ __ __
| __ \.-----.--| |______| __ \.---.-.| |--.| |--.|__| |_ ______| \.-----.----.--.--.--------.-----.-----.| |_.---.-.| |_|__|.-----.-----.
| <| -__| _ |______| <| _ || _ || _ || | _|______| -- | _ | __| | | | -__| || _| _ || _| || _ | |
|___|__||_____|_____| |___|__||___._||_____||_____||__|____| |_____/|_____|____|_____|__|__|__|_____|__|__||____|___._||____|__||_____|__|__|
The next few sections will be dedicated to the red rabbit documentation, the sections will be disected by module, eg: (0x0001 is module search) it goes from there
from the list above. Another example of how modules will be seperated is by the cloumn number in the chart above where Brute is the second module name, its section will
be labeled 0x0002 - BRUTE -, please take your time going through the documentation ALOT of people often forget about documentation then come to the devs confused as to
why some dont work, or how the script works and how to use it, so please, when i mean read it i mean READ IT CAREFULLY!
This section of the script will primarily be talking about JUST
errors that can happen inside of red rabbit, known bugs, and latest
update on the errors and bug fixes
this section wont be really split up much
since there is no way to organize the errors
other than the modules red rabbit will use like
common errors with the requests module which will
usually start an error message like so and so
> Windows Based Errors
Red Rabbit has never been a windows supportive tool
in fact it was brought up to steer as farrrrr away
as possible from windows system support during development
however some people still tried to run it on windows,
resulting in well different errors.
In red rabbit's source code it imports alot of
custom made modules and some of those module's
like the gopacket module need certian header files
or may even need certian paths that are not supported
in that code, when trying to run red rabbit on a windows
based or windows system you get many errors such as files
could not be installed properlly due to NULL input, or the
module could not find the filepath specified, or even that
the perl Makefile.pl file can not install itself in a directory
or move the files to a new destination because that destination
file simply does not exist. All of these errors are being worked
on as the version 1.0 release, eventually red rabbit will have
good and decent windows support, but for now it stays primary to
arch or debian based linux distributions
> Errors when installing red rabbit
there are a few issues you can get when installing red rabbit
most of this being due to non proper install during module or
third party module installs. A common one that seems to pop up
even with currently testing red rabbit v 1.0 on linux has been
insufficient and really annoying to fix. Currently the error
you will get is during install of the gopacket third party
library is that pcap.h is not a directory and when you use
command
sudo apt-get install libpcap-dev
you get the error that the libpcap has a insufficient version
and you may need to install a certian version based on its
depends. This is a wacky error and one there is no way of
fixing that is known, even after hours of trying to fix it
there was no luck in actually trying to fix the issue. So
in conclusion of this error it is very very annoying and
simply will stop compiliation or instaklling of red rabbit
any version really and if you can run wireshark and not
red rabbit because of a simple pcap error your system is
what would be assumed as broken
> errors when running some file based utilities
Red Rabbit is currently a very very dependant script
on the user to input their own data, or if there is
something like config in the command name it will be
taking it from a .YAML file
When running commands that use files, there can be
many errors you can get just by running one, a simple
error being a giant ass panic error that fills your
screen with a bunch of panic and large output talking
about " invalid null segment | segment violation"
this could have been caused by a few things, and it
could have also been done as a bug in the function but
for now here are the most common ones and how to fix them
-> panic: argument nil or something is nil
nil, null, 0x000, etc mainly all mean empty
so if red rabbit gives you an error that you
can not simply run the command because of a
0x000 base value, nil or NULL or empty value
then you will most likely be doing something wrong
some functions require flags while others dont
see dashbord
flags
for more information. Anyway this argument error
is a easy fix, if the error is around a file
function and again states something like invalid nil
indifference or nill value make sure your filepath
is working and has no '' or "" in it outside of
spcifying flags.
if the error still continues then make sure the
filepath you are using is not malformed, when
specifying a flag with filpaths make sure
the file you are going to search for at the
end or the file you will be using at the end
of a filepath eg(/usr/share/wordlists/dnsmap.txt)
where dnsmap.txt is the end file does not have ''
or "" or special characters that may cause the
filepath to be malformed.
> Errors when running file dependant functions
in the documentation page, parse, see parse
for more informaion
parse
There is a command called parse xmln something
where something is replaced by an element to be
parsed in the XML file, like most commands
in red rabbit that revolve around JSON, XML,
YAML, or other files you can get a error that says
file may be closed or too many open files
currently this is a dev issue and can result
in dev code 255 which indicates is a development
based error, or in simpler terms a code base error
meaning that something went wrong in the code maybe
something wasnt supposed to be there, dev code 255
usually is not supposed to happen.
if you need a simple fix and didnt get a desired output
or it prevented you from finding information on the
element you were searching for simply re run the command
this will or should fix it often times.
in the red rabbit GUI or scan GUI with command
`run RR6 scan gui` the gui for some reason will not
pop up, load, or even run the function, this is currently being fixed
however for the time being you will have to use the other command