07-31-2001
Most commerical port scanners can determine the OS type, scan all ports for vulnerabilities AND detail a report that suggests the appropriate fixes. So, if are running UNIX for a large commercial, government, or other entity; see if they have purchased a good commerical port scanner (and keep it updated with the lastest goodies).
Similar tools are available with shareware. Tools like SATAN, come to mind first. Enjoy!
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Dear Experts,
I would like to know whether there are any tools available to view the Security Audit Trail files (SAT) in UNIX in a easier and customized way. If there is any similar type of S/W is available, please let me know.
Thanks,
Aswin (1 Reply)
Discussion started by: na100006
1 Replies
2. UNIX for Advanced & Expert Users
I am wanting to run backups to remote servers ie: A to B's tape drive and B to A's tape drive. Should I use rsh or ssh? It looks as those rsh opens up security issues (the backup has to run as root). Which one should be used and does someone have the links to set up allowed connections. In what I... (7 Replies)
Discussion started by: jphess
7 Replies
3. UNIX for Dummies Questions & Answers
Hey,
I was wondering if anyone knew of any good tools out there for collecting/viewing/sorting audit data from Solaris (10) and Linux (SUSE and RHE) platforms? I am required by some government standards to audit certain actions on these systems like login and logouts, file access and actions... (0 Replies)
Discussion started by: fearturtle03
0 Replies
4. UNIX for Advanced & Expert Users
I am going to take up a position in Data & Network Security.
I would need to write network shell scripts doing the following task:
Going to around 2000 servers and findout which groups has access to each servers and which ids are there in each group that has access.
I need to implement... (1 Reply)
Discussion started by: pinnacle
1 Replies
5. Solaris
What files are in this directory? Are they files that tell you what events have been performed on the system for the day? Also, I am searching in one of these files for a Permission Denied entry. How do I go about searching for this entry in these files if they are so huge and cannot display on my... (2 Replies)
Discussion started by: jastanle84
2 Replies
6. AIX
Dear All
When I start the AIX(6100-06)audit subsystem.
the log will save in /audit/stream.out (or /audit/trail), but in default when /audit/stream.out to grow up to 150MB.
It will replace the original /audit/stream.out (or /audit/trail).
Then the /audit/stream.out become empty and... (2 Replies)
Discussion started by: nnnnnnine
2 Replies
7. Red Hat
Hi all
I am trying to add secure and audit logs to logrotate for a client whom wants the logs for a period of 6 months, compressed/zipped weekly for auditing.
I am terrible with logrotate and since there isn't default settings for both logs, I created two new entries in my /etc/logrotate.d/... (7 Replies)
Discussion started by: hedkandi
7 Replies
LEARN ABOUT REDHAT
sane-find-scanner
sane-find-scanner(1) General Commands Manual sane-find-scanner(1)
NAME
sane-find-scanner - find SCSI and USB scanners and their device files
SYNOPSIS
sane-find-scanner [-h|-?] [-v] [-q] [-f] [devname]
DESCRIPTION
sane-find-scanner is a command-line tool to find SCSI and some USB scanners and determine their Unix device files. It's part of the sane-
backends package.
For SCSI scanners, it checks the default generic SCSI device files (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI
inquiry command and looking for a device type of "scanner" or "processor" (some old HP scanners seem to send "processor"). So sane-find-
scanner will find any SCSI scanner connected to those default device files even if it isn't supported by any SANE backend.
For USB scanners, first the USB kernel scanner device files (e.g. /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner are tested. The
files are opened and the vendor and device ids are determined if the operating system supports this feature. Currently USB scanners are
only found this way if they are supported by the Linux scanner module or the FreeBSD or OpenBSD uscanner driver. After that test, sane-
find-scanner tries to scan for USB devices found by the USB library libusb (if available). There is no special USB class for scanners, so
the heuristics used to distinguish scanners from other USB devices is not perfect. sane-find-scanner will even find USB scanners, that are
not supported by any SANE backend.
sane-find-scanner won't find parallel port scanners, or scanners connected to proprietary ports.
OPTIONS
-h, -? Prints a short usage message.
-v Verbose output. If used once, sane-find-scanner shows every device name and the test result. If used twice, SCSI inquiry informa-
tion and the USB device descriptors are also printed.
-q Be quiet. Print only the devices, no comments.
-f Force opening all explicitely given devices as SCSI and USB devices. That's useful if sane-find-scanner is wrong in determing the
device type.
devname Test device file "devname". No other devices are checked if devname is given.
EXAMPLE
sane-find-scanner -v
Check all SCSI and USB devices for available scanners and print a line for every device file.
sane-find-scanner /dev/scanner
Look for a (SCSI) scanner only at /dev/scanner and print the result.
SEE ALSO
sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1), sane-"backendname"(5)
AUTHOR
Oliver Rauch, Henning Meier-Geinitz and others
SUPPORTED PLATFORMS
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel, libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the vendor
and device ids only works with Linux or libusb.
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris, FreeBSD, NetBSD, OpenBSD, and HP-UX.
BUGS
No support for parallel port scanners yet.
15 Sep 2002 sane-find-scanner(1)