Ports Search

Net::Printer ============ Perl module for directly printing to a print server/printer without having to create a pipe to either lpr or lp. This essentially mimics what the BSD LPR program does by connecting directly to the line printer printer port (almost always 515), and transmitting the data and control information to the print server. Please note that this module only communicates with the BSD Line Printer Daemon Protocol as described in RFC-1179. It does not natively speak to remote print servers via SMB, Apple-Talk or Netware. Remote print services running lpsched, such as Sun Solaris or other Sys V-derived operating systems, will work so long as the print spoolers are set up to understand the BSD protocol. Most modern network-capable laser printers, such as those manufactured by HP and LexMark, also "speak" BSD.

XmBibTeX is a Motif (LessTif) reference manager based on the BibTeX file format. It allows to add, delete, and edit references. The references can be saved in the BibTeX file format and also written on a LaTeX file that can be printed using LaTeX and BibTeX. References can be retrieved by several search strategies. Import of references from the Medline and Inspec file format is included. However, I found that the Medline file format is not unique. Up to now, there are import filters available for the "Ovid Medline", the "PubMed Medline" and for the "Spirs Medline" format. It would be nice if some people could write additional import filters for other file formats.

The rux is a simple and at the same time powerful utility for texts recoding from one encoding to another. At present time several the most popular Cyrillic code pages such as utf-8, koi8-r, cp866, cp1251, iso8859-5 and mac-cyrillic are supported. Also rux gives the opportunity to recode box- drawing characters, which exists in some Cyrillic code pages, to replace them by their non-graphic analogues ('-', '+', etc.). Besides, the rux can detect a code page of the input files automatically. Usually rux is used without any options because some values are accepted by default. There are -o koi8-r, -e, -t. The expectancy value of the presence of every Cyrillic characters in the some text were taken from the dump of Russian translation of the `FreeBSD Handbook'.

CDO is a collection of command line Operators to manipulate and analyse Climate model Data. Supported file formats are GRIB, netCDF, SERVICE, EXTRA and IEG. There are more than 250 operators available. The following table gives a short overview about the main categories. * File information (info, sinfo, diff, ...) * File operations (copy, cat, merge, split*, ...) * Selection (selcode, selvar, sellevel, seltimestep, ...) * Missing values (setctomiss, setmisstoc, setrtomiss) * Arithmetic (add, sub, mul, div, ...) * Mathematical functions (sqrt, exp, log, sin, cos, ...) * Comparision (eq, ne, le, lt, ge, gt, ...) * Conditions (ifthen, ifnotthen, ifthenc, ifnotthenc) * Field statistic (fldsum, fldavg, fldstd, fldmin, fldmax, ...) * Vertical statistic (vertsum, vertavg, vertstd, vertmin, ...) * Time range statistic (timavg, yearavg, monavg, dayavg, ...) * Ensemble statistic (enssum, ensavg, ensstd, ensmin, ...) * Regression (detrend) * Field interpolation (remapbil, remapcon, remapdis, ...) * Vertical interpolation (ml2pl, ml2hl) * Time interpolation (inttime, intyear)

Code Saturne is a system designed to solve the Navier-Stokes equations in the cases of 2D, 2D axisymmetric or 3D flows. Its main module is designed for the simulation of flows which may be steady or unsteady, laminar or turbulent, incompressible or potentially dilatable, isothermal or not. Scalars and turbulent fluctuations of scalars can be taken into account. The code includes specific modules, referred to as "specific physics", for the treatment of lagrangian particle tracking, semi-transparent radiative transfer, gas combustion, pulverised coal combustion, electricity effects (Joule effect and electric arcs) and compressible flows. The code also includes an engineering module, Matisse, for the simulation of nuclear waste surface storage. Code_Saturne relies on a finite volume discretisation and allows the use of various mesh types which may be hybrid (containing several kinds of elements) and may have structural non-conformities (hanging nodes). NCS means "Noyau Code Saturne", i.e. "Code Saturne Kernel". This is the numerical solver.

Gringotts is an application to store sensitive data like passwords, pincodes, credit card numbers, etc. Features: * Fast, light GTK2 interface. * Good integration with GNOME, as well as all the other window managers. * High stress on safety & security. * Not only "normal" string passwords can be used, but any file can be the password to your data. * 8 encryption algorythms are available through the mcrypt library: RIJNDAEL-128 (AES), RIJNDAEL-256, SERPENT, TWOFISH, CAST 256, SAFER+, LOKI97, 3DES. * 2 160-bit hash algorythms, used to generate the key: SHA1, RIPEMD160. * 2 compression types, with 4 compression levels each: ZLib, BZip2. * Complete & easy management of entries' order. * Complete Search function. * Very intuitive usability, you won't need any manual. * It comes with a thread-safe C library, libGringotts, that can be used in any other project to save data in files in a simple and safe way.

racoon speaks IKE (ISAKMP/Oakley) key management protocol, to establish security association with other hosts. This is the IPSec-tools version of racoon. Enchancements: - Support of NAT-T and IKE fragmentation. - Support of many authentication algorithms. - Tons of bugfixes. Known issues: - Non-threaded implementation. Simultaneous key negotiation performance should be improved. - Cannot negotiate keys for per-socket policy. - Cryptic configuration syntax - blame IPsec specification too... - Needs more documentation. Design choice, not a bug: - racoon negotiate IPsec keys only. It does not negotiate policy. Policy must be configured into the kernel separately from racoon. If you want to support roaming clients, you may need to have a mechanism to put policy for the roaming client after phase 1 finishes.

Nmap is a utility for network exploration and security auditing. It supports various types of host discovery (determine which hosts are up), many port scanning techniques for different protocols, version detection (determine service protocols and application versions listening behind ports), and TCP/IP stack fingerprinting (remote host OS or device identification). Nmap also offers flexible target and port specification, decoy/stealth scanning, sunRPC scanning, and much more. Also included is Ncat, the nc(1) work-a-like of the Nmap project. Refer to the separate port security/zenmap for those parts of the Nmap toolset which depend on python. The translated manual pages for Nmap are contained in security/nmap-i18n-man. See the web page and the Phrack Magazine article (Volume 7, Issue 51 September 01, 1997, article 11 of 17) http://nmap.org/p51-11.html

Firewall Builder consists of object-oriented GUI and set of policy compilers for various firewall platforms. In Firewall Builder, firewall policy is a set of rules, each rule consists of abstract objects which represent real network objects and services (hosts, routers, firewalls, networks, protocols). Firewall Builder helps user maintain database of objects and allows policy editing using simple drag-and-drop operations. Preferences and objects databases are stored in XML format. GUI and policy compilers are completely independent. Support for a new firewall platform can be added to GUI without any changes done to the program, although new policy compiler must be written. This provides for consistent abstract model and the same GUI for different firewall platforms. Currently three most popular free firewalls are supported: ipchains, iptables and ipfilter. Because of this, Firewall Builder can be used to manage firewalls built on variety of platforms including, but not limited to, Linux running ipchains or iptables and FreeBSD or Solaris running ipfilter.

[ excerpt from developer's www site ] The Cryptokit library for Objective Caml provides a variety of cryptographic primitives that can be used to implement cryptographic protocols in security-sensitive applications. The primitives provided include: Symmetric-key cryptography: AES, DES, Triple-DES, ARCfour, in ECB, CBC, CFB and OFB modes. Public-key cryptography: RSA encryption and signature; Diffie-Hellman key agreement. Hash functions and MACs: SHA-1, MD5, and MACs based on AES and DES. Random number generation. Encodings and compression: base 64, hexadecimal, Zlib compression. Additional ciphers and hashes can easily be used in conjunction with the library. In particular, basic mechanisms such as chaining modes, output buffering, and padding are provided by generic classes that can easily be composed with user-provided ciphers. More generally, the library promotes a "Lego"-like style of constructing and composing transformations over character streams.