There are some technical reasons why SAINT is important - it does do and detect things that weren't possible before, at least by no other tools or methods that the authors knew about. It's easy to use, and fills a gap that was only poorly covered by previous software. However, the death of the Internet is not, and should not be predicted.
When I try to run SAINT, it says (something like):
"missing right bracket at perl/getfqdn.pl line 48, at end of line"
You need to upgrade your version of perl - you're probably using the
alpha version of perl5.
What do I need to uncompress the SAINT tar file?
To uncompress the archives, you'll need to use the Un*x uncompress program
if it ends in ".Z", or the GNU unzip if it ends in ".gz".
Where do I get a version of perl that will work?
perl5 is available via anonymous ftp from ftp.netlabs.com
When I try to run SAINT, it says (something like):
"Can't locate ctime.pl in @INC at perl/status.pl line 5."
ctime.pl is bundled with perl5; if you've installed that, you should
have it - look for it in the library subdirectories. If it's there,
as a last resort you can copy "ctime.pl" (and perhaps "getopts.pl"
into the main SAINT directory, and SAINT should find it there.
When I try to run saint I get "Xlib:connection
to ":0.0" refused by server"
You can do a "xhost +hostname", where "hostname" is the host you're
running it on, and try again. Also, look at
the problems with X, networks, and SAINT.
I'm trying to get SAINT to compile on my ULTRIX box.
Why won't it work/where is rpgen?
DEC/Ultrix doesn't have "rpcgen". You'll need to run it
on another machine and drag the resulting source code over (or upgrade
to SAINT version 1.1 or better.)
SAINT doesn't find any hosts at all - it starts
and stops with "(0 host(s) visited)". This is bogus! Give me my
money back!
Calm down. You probably can't use ICMP to detect if a host is alive
or not. Try setting "$dont_use_ping=1" in config/saint.cf (it's
near the bottom.) It should work, or we'll give you double your money back.
SAINT crashed, hung, or did very odd things to a system
that it was run against.
We've received reports of various OS's that seem to have significant
trouble with SAINT scans, particularily the UDP and TCP scans that span
lots of ports. Among the afflicted:
I ran SAINT to analyze my results and the
machine slows grinds down to a standstill (and possibly crashes), but I
don't get any answers.
It could be, with a large amount of data, that SAINT is using too much
memory to fit in your machine. An enormous amount of memory is
consumed by the program (see
memory requirements for
more on this.) Try checking the memory used by SAINT on your machine;
if it needs more, get more memory - adding swap space is a very painful
way of trying to deal with this.
Given that Satan starts its own http server
on the local host, why doesn't it use 'localhost' instead of the FQDN
of the local host when trying to contact it?
This breaks some HTML browsers. Try running with $dont_use_nslookup (found
in config/saint.cf) when your naming service is crippled.
Whenever I click on a hyper link it doesn't work.
Be careful if you use proxy services (typically if you're behind a
firewall you do) to access the WWW - you should unset environment
variables (such as $http_proxy $file_proxy, $socks_ns, etc.) and/or
change your browser's configuration to not use your SOCKS host or HTTP
Proxy host (in your HTML browser's option section.)
I merged some databases together with the "merge"
function in the SAINT Data Management, but when I exited SAINT,
they weren't saved. What gives?
The database merging only works in memory. Currently there is no way to
save this to disk (until the next version of SAINT.)
I get "bin/tcp_scan: socket: Too many open files"
in the window from which I start Satan.
The machine's open file table is getting exhausted. Tcp_scan backs off
and succeeds after a few attempts. You'll need to build a bigger kernel or
run less processes.
I'm trying to get SAINT running on my Linux box.
Linux is far from a standard Un*x, and SAINT has a tendency to push the
OS and perl to the limits. We've tried to do as much as possible to
make it work, but there are probably various problems we haven't found
because we don't have a Linux box to play with. (Cross?) posting to
comp.security.unix and comp.os.linux.* could probably give you more
help than we could.
Why doesn't it warn remote hosts that it is probing them?
This could be built into saint; the most reliable general solution
would be to send mail to the probed system (say, to "root" or "postmaster").
A beta-tester suggested that an entry could be written to the target's
syslog. Neither of the solutions are incredibly reliable. The
former relies on someone reading the mail and the account existing, as
well as having to deal with hundreds if not thousands of pieces of mail
that might go to machines that the user of SAINT controls. The latter
has several problems, first and foremost in that it depends on people
actually looking at the syslog records, and secondly that if an intruder
uses SAINT to break in, they will typically "flatten", modify, or simply
destroy such records. Finally, many systems don't run or have non-standard
syslog programs and quite a few filter out requests with packet filters,
so they would never see the warning.
Nonetheless, we'll probably be putting either or both of these as options in the next release of SAINT.
What's the difference between it and COPS?
COPS is a host-based Un*x security auditing tool; that means you run it
on the host you wish to examine the security of. SAINT is a remote
network security auditing tool, which means it can report
on the security of any host OR network that has IP connectivity to where
you run the tool; you don't need an account or privileges on the remote
targets to report on them.
What's the difference between it and ISS and other remote scanners?
ISS, and any other remote auditing tool that we're aware of, scans a network
or remote host and then reports on any problems that it may find. While
SAINT does that as well, the inferencing, the web of trust that it
uncovers, the automatic probing of secondary targets, the rich reporting
schema with context sensitive hypertext links to the documentation, the
rich configurability, etc. all make SAINT different to what is currently
available.
What's a remote security auditing tool/probe/scanner?
This means it can report on the security of any host OR network that has
IP connectivity to where you run the tool; you don't need an account or
privileges on the remote targets to report on them.
I'm using a B/W monitor, and it's hard to
see the difference between red and black dots. What can I do?
The easiest thing to do is to just mv (or link or whatever) the
html/dots/whitedot.gif to html/dots/reddot.gif. That'll
give a much higher contrast and should be easier to read.
How can I change from one HTML browser (e.g. Mosaic,
Netscape, whatever) to another, without running reconfig or something?
Simply edit the file config/paths.pl. You'll see a line that
looks like:
$MOSAIC = "/usr/local/bin/netscape";
Change the path inside the parenthesis to point to wherever your
preferred browser is; for instance, if you want to use Mosaic, and it's
in /usr/bin/X11, you'd change the above line to:
$MOSAIC = "/usr/bin/X11/Mosaic";
Why does SAINT keep fingering the same host(s) over and over again?
SAINT will finger a host repeatedly if it gets new information about the
host; for instance, if it finds out that a user might exist on a host, it
will finger to try and find out remote login information.
SAINT died (or the machine crashed, or whatever)
in the middle of a run - do I have to start everything over again?
SAINT saves data at regular intervals to its database files; the easiest
thing to do is to simply start it up again, with the same target and
probe levels. If SAINT has remembered anything, it will grind away for
awhile, finding out what it has seen before, and then resume on the targets
that it hasn't scanned.
How can I tell if anyone is running SAINT against
me?
CIAC wrote and is distrbuting something called
Courtney, but it is far from foolproof. It is very difficult
to detect the lighter SAINT scans; the heavier ones, however, are
typically best detected by running Wietse's tcpd wrappers and examining
the logs - a good tipoff is if many of your machines in the same area
log connections from the same remote site. Some of the SAINT probes
output a message to the console - if users report odd messages on their
console screen, take them seriously ;-)
{When is the port of/can you help me port/do
you have any information on porting} SAINT to MacOS/DOS/VMS/MVS/Whatever?
SAINT, at least on the server side, is heavily linked to Un*x and perl5.
While it might be possible to port SAINT to one of these other OS's (if
you can call them that! ;-)) would be fairly difficult and not something
that either one of us wants to touch with a ten foot (or ~ 3 meter) pole.
I see a lot of odd files that are appearing
on my system after running SAINT, such as /tmp/sh11318, tmp_file.1288,
etc. What's the deal?
SAINT uses perl extensively in it's tests; the .saint
probes use such commands as:
open(FOO, "|program <<_EOF
some input
more input
_EOF");
This will leave a temporary file behind when SAINT determines that they
have run out of time and kill off the probe. Almost all temporary files
that are created at various time within the SAINT are deleted
automatically, but since the << files are created internally by the shell,
it is impossible for SAINT to know how to delete the files
that remain. Simply delete them, or create a cron job to
automatically sweep the /tmp directory for you.
Why doesn't SAINT check for
[insert your favorite bug here]?
There are several reasons why SAINT does not probe for all known bugs: