Sponsored Content
Full Discussion: Security & audit
Special Forums Cybersecurity Security & audit Post 4801 by Neo on Tuesday 31st of July 2001 08:19:05 PM
Old 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

Security Audit Trail

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

RSH or SSH & security

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

Security Audit logging

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

Network Shell Script & Blade Logic & Network Security

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

/etc/security/audit/SERVERNAME/files

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

When AIX audit start, How to set the /audit/stream.out file size ?

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

Secure & Audit logs

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
sane-kodak(5)						   SANE Scanner Access Now Easy 					     sane-kodak(5)

NAME
sane-kodak - SANE backend for big Kodak flatbed and ADF scanners DESCRIPTION
The sane-kodak library implements a SANE (Scanner Access Now Easy) backend which provides access to large Kodak flatbed and ADF scanners. This document describes backend version 7, which shipped with SANE 1.0.21. SUPPORTED HARDWARE
This version should support models which speak the Kodak SCSI and Firewire protocols. The i1860 was used to develop the backend, but other models may work with only minimal modifications. Please see the list at http://www.sane-project.org/sane-supported-devices.html for an updated list. If you have a machine not on that list, or reported as 'untested': the best way to determine level of support is to test the scanner directly, or to collect a trace of the windows driver in action. Please contact the author for help or with test results. UNSUPPORTED HARDWARE
Most of the recent Kodak consumer or workgroup level machines are based on other chipsets and are not supported by this backend. Some of these scanners may be supported by another backend. OPTIONS
Effort has been made to expose the basic hardware options, including: source s Selects the source for the scan. Options may include "Flatbed", "ADF Front", "ADF Back", "ADF Duplex". mode m Selects the mode for the scan. Options may include "Lineart", "Halftone", "Gray", and "Color". resolution Controls scan resolution. Available choices may be limited by mode. tl-x, tl-y, br-x, br-y Sets scan area upper left and lower right coordinates. These are renamed t, l, x, y by some frontends. page-width, page-height Sets paper size. Used by scanner to determine centering of scan coordinates when using ADF and to detect double feed errors. Other options will be available based on the capabilities of the scanner. Use 'scanimage --help' to get a list, but be aware that some options may be settable only when another option has been set, and that advanced options may be hidden by some frontend programs. CONFIGURATION FILE
The configuration file "kodak.conf" is used to tell the backend how to look for scanners, and provide options controlling the operation of the backend. This file is read each time the frontend asks the backend for a list of scanners, generally only when the frontend starts. If the configuration file is missing, the backend will use a set of compiled defaults, which are identical to the default configuration file shipped with SANE. Scanners can be specified in the configuration file in 2 ways: "scsi KODAK" Requests backend to search all scsi busses in the system for a device which reports itself to be a scanner made by 'KODAK'. "scsi /dev/sg0" (or other scsi device file) Requests backend to open the named scsi device. Only useful if you have multiple compatible scanners connected to your system, and need to specify one. Probably should not be used with the other "scsi" line above. The only configuration option supported is "buffer-size=xxx", allowing you to set the number of bytes in the data buffer to something other than the compiled-in default, 32768 (32K). Some users report that their scanner will "hang" mid-page, or fail to transmit the image if the buffer is not large enough. Note: This option may appear multiple times in the configuration file. It only applies to scanners discovered by 'scsi/usb' lines that fol- low this option. Note: The backend does not place an upper bound on this value, as some users required it to be quite large. Values above the default are not recommended, and may crash your OS or lockup your scsi card driver. You have been warned. ENVIRONMENT
The backend uses a single environment variable, SANE_DEBUG_KODAK, which enables debugging output to stderr. Valid values are: 5 Errors 10 Function trace 15 Function detail 20 Option commands 25 SCSI trace 30 SCSI detail 35 Useless noise KNOWN ISSUES
Most hardware options are either not supported or not exposed for control by the user, including: multifeed detection, image compression, autocropping, endorser, iThresholding, multi-stream, etc. CREDITS
The various authors of the sane-fujitsu backend provided useful code. Kodak provided access to hardware, documentation and personnel. SEE ALSO
sane(7), sane-scsi(5) AUTHOR
m. allan noah: <kitno455 a t gmail d o t com> 10 Feb 2010 sane-kodak(5)
All times are GMT -4. The time now is 05:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy