Nautilus Debian Repository
This page describes how to set up your Debian box to work with the OSHEAN repository.
Information about installation and configuration of individual Nautilus packages can be found at NautilusInstallation.
Using the OSHEAN Nautilus repository
Adding the OSHEAN Nautilus GPG key
All packages in the Nautilus repository are signed with our GPG key for security purposes. It is highly recommend that you verify our public key and add it to your apt keyring to ensure your packages are unmodified from the ones provided by OSHEAN.
Public Key: nautilus-release.asc
Key ID: 0x7A87DACC
Fingerprint: D64D B40E A666 625F 4EAC C845 8C8B 17DC 7A87 DACC
Download our public key, and verify its fingerprint:
gpg --keyserver pgpkeys.mit.edu --recv-key 7A87DACC gpg --fingerprint 7A87DACC
Add the key to APT's keyring (see SecureApt):
gpg -a --export 7A87DACC | apt-key add -
Setting up the repository
Append the following line to your /etc/apt/sources.list file:
deb http://nautilus.oshean.org testing main
Now run aptitude update, and make sure there are no errors. You can now download any package from our repository.
Installing packages
To install any of the available Nautilus packages, you can use the command aptitude install. For example, to install our custom build of snort, you can run:
# aptitude install nautilus-snort
For more detailed information on installing packages within the Nautilus system, please see NautilusInstallation.
Updating packages
To upgrade your Nautilus system (and Debian etch itself) to the latest version released by OSHEAN, run
# aptitude update # aptitude upgrade
The update command to aptitude refreshes information from our repository; the upgrade command finds and downloads any appropriate updates for installed packages.
You may also update individual packages as needed by specifying the package name to aptitude upgrade:
# aptitude upgrade nautilus-snort-rules
The nautilus-snort-rules package is updated very frequently (at least weekly). It is important to keep up with the latest snort rules released by the community as new vulnerabilities emerge.
Repository status and conventions
Package listing
The packages available in the Nautilus repository are listed below.
Debian packaging status is currently tracked over here.
| Package Name | Component | Version | Description | Status |
| nautilus-base-system | All | 9.1-3 | System definitions | testing |
| nautilus-distribution | All | 2.0-2 | Virtual package depending on all nautilus packages | testing |
| nautilus-web | Web | 0.2-6 | Integrated web interface for Nautilus | testing |
| nautilus-snort | snort | 2.8.2.2-4 | upstream snort with MySQL and Aruba support | testing |
| nautilus-snort-rules | snort | 20081104 | community/Emerging Threats rules - updated weekly | testing |
| nautilus-acidbase | snort | 1.2.7-1 | BASE web interface for snort | etch/stable |
| nautilus-periscope | Periscope | 0.9.0 | IPAudit replacement | N/A |
| nautilus-ntop | ntop | 20081014-5 | current SVN of ntop | testing |
Supported architectures
Currently only the i386 build of Debian is supported. However, we plan to add AMD64/EM64T packages to the repository in the future, as most of our servers run newer 64-bit capable Xeon processors. If other architectures are requested (ppc and sparc), packages may be provided in the future.
OSHEAN also provides source packages for all Nautilus components, so if an architecture does not have a binary package, you may download and build the source code yourself. See the APT HOWTO for more details.
Stable, testing, and unstable
Debian GNU/Linux is divided into three distributions - stable (codename etch), testing (codename lenny), and unstable (codename sid). Only the stable build, which contains tried-and-tested versions of all of Debian's many software packages, is recommended for production use. The testing and unstable builds are far more bleeding-edge, and may not always work as intended; however, they are useful to developers and system administrators who are willing to work around bugs to use the latest version of a piece of software.
Nautilus is distributed to members only with stable builds of our core components, but we distribute packages that we are still testing through our repository so members can test them on non-production systems. We encourance and appreciate any and all feedback from members using the testing packages, as it will greatly improve the quality of our next stable release.
