Free smbd log it software for linux

Buildog was inspired by my need to track the steps involved in software builds. Particularly the software packages in the Linux From Scratch book.

It is not a package manager in the traditional sense, it will not track dependences. It tries to stay out of your way as much as possible.

If you grow weary of RPM spec files, or this months "package manager" (there are about a dozen or so of them out there, with new distributions adding their own every month) Buildog may be for you.

What it will do for you is log the information required to build it, files it created, URLs it needs (it will fetch them for you too if you want, with support for mirrors and caching) a log of the build stages, notes and descriptions, its home page, and any other information you may wish to add.

Its pretty simple to use, if youve ever installed packages from source, youll get the hang if it quickly.

Installation

Quite a bit of work has gone into making this install nicely. Perl programs are kind of notorious for being difficult to install.

It uses the autoconf to guess your location of perl, supports the usual --prefix --bindir --sysconfdir and --localstatedir options. Type make install to install it, (a plain make shows what will be installed where).

SMBD Audit application is a set of VFS audit module for Samba 3 and web frontend to view and search samba audit logs.

Module stores logs directly into MySQL database with libmysqlclient.

You can search database by Login, Address, Share, Action, Log Message(specify filename or directory name), From and To Date.

Here is a very short list of what SMBD Audit package includes, and what it does.

- a VFS audit module, to provide logging to MySQL database

- a web front end to view and search logs.

dclog is a logging library for C and C++. It supports the concept of log levels, configurable logfile timestamps, and a configurable prefix to log messages.

Installation:

1. From source:

make all
make install (as root)

2. Gentoo users:

emerge -vp dclog
emerge dclog

Nmap Log Stripp3r program is intended to be a way to condense all, or some, of the IPs of a "random" nmap scan into a file for later usage.

Common uses are to be able to feed the file back into nmap with the -iL switch, or feeding it into another port or vulnerability scanner of your choice.

Stripp3r supports stripping the nmap log of all but the IPs of hosts running a certain service, a version of a service, or even an arbitrary banner, and writing them to a file.

This is intended to be a way to condense all the IPs of a "random" Nmap scan into a file for later useage. Common uses are to be able to feed the file back into Nmap its self with the -iL switch, or feeding it into another port or vulnerability scanner.

Useage: ./stripp3r < logfile > < output > "< version string >" -v

Pretty simple. First, you must run an Nmap scan, on random hosts.

Ex. nmap -p 80 -sV -v -iR 500000 -oN nmaplogfile.nmap

This will tell nmap to do a scan service scan of 500,000 random IP addresses for the port 80, vobosely, and save the log to a file named nmaplogfile.nmap. You can change this around, eg, scanning a different service port (if say, you were looking for computers running FTP, you would scan for port 21 instead of 80 for HTTP), scanning a different number of hosts (500,000 or so is good, takes a few hours ususally though), or saving the log file to a different filename.

Nmap will then save a list of hosts that were "up" to a log file, with some informaiton about them, specifically weather the port that you specified was open, closed, or filtered. We are interested in "open" ports, so by default, Stripp3r will take all the log
enteries that have the port your specified listed as "open" and condense them into a file, listing only the IPs, one on each line.

Ex. ./stripp3r nmaplogfile.nmap output.ips

You can be more specific, and have Stripp3r put only the IPs that are running a certain service in the output file. The service string will only register the strings matching EXACTLY, so be careful to get the case and such correct.

apache httpd 1.3.27 (wont work)
Apache 1.3.27 (wont work)
Apache httpd 1.3.27 (works!)

Ex. ./stripp3r nmaplogfile.nmap output.ips "Apache httpd 1.3.27"

If you want to try it with verbosity, say

Ex. ./stripp3r nmaplogfile.nmap output.ips "Apache httpd 1.3.27" -v

And stripp3r will print out what it finds, along with writing it to the file.

You may change, copy, and reproduce this file, as long as the author is given credit for the initial writing of the code.

Log::StdLog is a Perl module with a simple log file via a special filehandle.

SYNOPSIS

use Log::StdLog { level => warn, file => "$0.log" };

# Messages at the same or a higher level are logged...
print {*STDLOG} error => "This error message will be loggedn";
print {*STDLOG} warn => "This warning message will be loggedn";

# Messages at a lower level are ignored...
print {*STDLOG} info => "This info message will NOT be loggedn";

# The default message level is the one that was specified
# when the module was loaded...

print {*STDLOG} "This is a warning message. It will be loggedn";

This module provides a very simple kind of log file, with a very simple interface. Messages are logged simply by printing to *STDLOG, which the module exports to any namespace into which its loaded.

Snowlog is a webserver access log browser/analyzer. It does not generate static reports, but lets you browse through the requests in real time. Filters that accept regular expressions can be applied.

Installation:

make
make install (as root)

IPTables log analizer displays Linux 2.4 iptables logs (rejected, acepted, masqueraded packets...) in a nice HTML page (it support rough netfilter logs but also Shorewall and Suse Firewall logs).

This page shall be easy to read and understand to reduce the manual analysis time.

This page containts statistics on packets and links to more detailled information on a given host, port, domain and so on.

To convice you, here is a typical syslog entry for iptables :

[IPTABLES DROP] : IN=ppp0 OUT= MAC= SRC=172.186.2.157 DST=193.253.186.217 LEN=36 TOS=0x00 PREC=0x00 TTL=115 ID=4775 PROTO=ICMP TYPE=8 CODE=0 ID=512 SEQ=3663

How does it work ?

A small deamon is launched by a user which can read iptables logs files. Each time a new packet is logged, the daemon insert a new row in the database.

The statistics and so on are elaborated by the PHP page itself.

PostgreSQL Table Log contains functions that allow you to log PostgreSQL table inserts, updates, and deletes into another table.
This can be used to recover the state of the logged table or to recover specific rows from a given time period.
Enhancements:
- This version now works with PostgreSQL versions 8.2 and later.
- Some warnings have been removed and the documentation was cleaned up.
- PGXS is now used for building from source.
- RPM packages are available.