better formatting
This commit is contained in:
parent
68dbec019e
commit
1ff7ada6a4
@ -1,4 +1,4 @@
|
||||
lzop is a file compressor which is very similar to gzip. It
|
||||
uses the LZO library for compression services and its main
|
||||
advantages over gzip are much higher compression and decom-
|
||||
pression speed (at the cost of some compression ratio).
|
||||
lzop is a file compressor which is very similar to gzip. It uses the
|
||||
LZO library for compression services and its main advantages over gzip
|
||||
are much higher compression and decompression speed (at the cost of some
|
||||
compression ratio).
|
||||
|
@ -1,3 +1,3 @@
|
||||
Perl-LZO provides LZO bindings for Perl5. I.e. you can
|
||||
access the LZO library from your Perl scripts thereby com-
|
||||
pressing ordinary Perl strings.
|
||||
Perl-LZO provides LZO bindings for Perl5. I.e. you can access the LZO
|
||||
library from your Perl scripts thereby compressing ordinary Perl
|
||||
strings.
|
||||
|
@ -1,5 +1,4 @@
|
||||
isync is a command line application which synchronizes a
|
||||
local maildir-style mailbox with a remote IMAP4 mailbox. It
|
||||
is suitable for use in IMAP-disconnected mode. Multiple
|
||||
copies of the remote IMAP4 mailbox can be maintained, and
|
||||
all flags are synchronized.
|
||||
isync is a command line application which synchronizes a local
|
||||
maildir-style mailbox with a remote IMAP4 mailbox. It is suitable for
|
||||
use in IMAP-disconnected mode. Multiple copies of the remote IMAP4
|
||||
mailbox can be maintained, and all flags are synchronized.
|
||||
|
@ -1,4 +1,3 @@
|
||||
This module is a complete, RFC 821 compliant, SMTP server
|
||||
implementation written entirely in Perl. It has powerful
|
||||
extensively and customization facilities that allow for a
|
||||
variety of potential uses.
|
||||
This module is a complete, RFC 821 compliant, SMTP server implementation
|
||||
written entirely in Perl. It has powerful extensively and customization
|
||||
facilities that allow for a variety of potential uses.
|
||||
|
@ -1,7 +1,6 @@
|
||||
The Solid POP3 Server is an implementation of a Post Office
|
||||
Protocol version 3 server that has flexibility as its main
|
||||
goal. The server is easily configurable and has support for
|
||||
few features such as:
|
||||
The Solid POP3 Server is an implementation of a Post Office Protocol
|
||||
version 3 server that has flexibility as its main goal. The server is
|
||||
easily configurable and has support for few features such as:
|
||||
|
||||
o APOP authentication scheme
|
||||
o Virtual hosting
|
||||
@ -9,16 +8,14 @@ few features such as:
|
||||
o Bulletins
|
||||
o Expiration of messages
|
||||
|
||||
Each user can specify his maildrop (its position and type).
|
||||
The format used in specification of maildrop's position
|
||||
should handle almost all widely-used system configurations.
|
||||
The server also seems to be fast, however no tests have been
|
||||
performed, so it's rather relative feeling. The design used
|
||||
is very similar to the design of Solar Designer's POPA3D
|
||||
server. This solution let's minimalize size of code working
|
||||
with root privileges. The code was also heavily checked for
|
||||
buffer overflow leaks and file races. None have been found
|
||||
as for now. All operations on files are done with user priv-
|
||||
ileges. There is no SUID APOP secrets database management
|
||||
program (as in QPOP). Each user can specify his secret in
|
||||
his own home directory.
|
||||
Each user can specify his maildrop (its position and type). The format
|
||||
used in specification of maildrop's position should handle almost all
|
||||
widely-used system configurations. The server also seems to be fast,
|
||||
however no tests have been performed, so it's rather relative feeling.
|
||||
The design used is very similar to the design of Solar Designer's POPA3D
|
||||
server. This solution let's minimalize size of code working with root
|
||||
privileges. The code was also heavily checked for buffer overflow leaks
|
||||
and file races. None have been found as for now. All operations on
|
||||
files are done with user privileges. There is no SUID APOP secrets
|
||||
database management program (as in QPOP). Each user can specify his
|
||||
secret in his own home directory.
|
||||
|
@ -1,5 +1,4 @@
|
||||
The Lucent Remote Access RADIUS server 2.1 with support for
|
||||
RADIUS proxy, iPass roaming, and ActivCard.
|
||||
The Lucent Remote Access RADIUS server 2.1 with support for RADIUS
|
||||
proxy, iPass roaming, and ActivCard.
|
||||
|
||||
This port does not use iPass roaming or ActivCard at this
|
||||
time.
|
||||
This port does not use iPass roaming or ActivCard at this time.
|
||||
|
@ -1,9 +1,8 @@
|
||||
SING stands for 'Send ICMP Nasty Garbage.' It is a tool that
|
||||
sends ICMP packets fully customized from command line. It's
|
||||
main purpose is to replace and complement the ping command,
|
||||
adding certain enhancements as fragmentation; send and
|
||||
receive spoofed packets; send many ICMP information types
|
||||
(echo as the old ping, address mask, timestamp, and router
|
||||
discovery) and errors (redirect, unreach, and time
|
||||
exceeded); and send monster packets. It also supports loose
|
||||
and strict source routing and record routing.
|
||||
SING stands for 'Send ICMP Nasty Garbage.' It is a tool that sends ICMP
|
||||
packets fully customized from command line. It's main purpose is to
|
||||
replace and complement the ping command, adding certain enhancements as
|
||||
fragmentation; send and receive spoofed packets; send many ICMP
|
||||
information types (echo as the old ping, address mask, timestamp, and
|
||||
router discovery) and errors (redirect, unreach, and time exceeded); and
|
||||
send monster packets. It also supports loose and strict source routing
|
||||
and record routing.
|
||||
|
@ -1,4 +1,4 @@
|
||||
This is Crypt::CBC, a Perl-only implementation of the cryp-
|
||||
tographic cipher block chaining mode (CBC). In combination
|
||||
with a block cipher such as Crypt::DES or Crypt::IDEA, you
|
||||
can encrypt and decrypt messages of arbitrarily long length.
|
||||
This is Crypt::CBC, a Perl-only implementation of the cryptographic
|
||||
cipher block chaining mode (CBC). In combination with a block cipher
|
||||
such as Crypt::DES or Crypt::IDEA, you can encrypt and decrypt messages
|
||||
of arbitrarily long length.
|
||||
|
@ -1,2 +1,2 @@
|
||||
This is Crypt::DES, an XS-based implementation of the DES
|
||||
cryptography algorithm.
|
||||
This is Crypt::DES, an XS-based implementation of the DES cryptography
|
||||
algorithm.
|
||||
|
@ -1,12 +1,11 @@
|
||||
Radiusreport can produce many varied reports by analysing
|
||||
your RADIUS detail files. detail files can be uncom-
|
||||
pressed/compressed/gzipped.
|
||||
Radiusreport can produce many varied reports by analysing your RADIUS
|
||||
detail files. detail files can be uncompressed/compressed/gzipped.
|
||||
|
||||
o User online time reports (bandwidth used, etc.)
|
||||
o IP address usage.
|
||||
o Last login time reports.
|
||||
|
||||
As of V.02 radiusreport can generate individual files for
|
||||
each user by using the -o flag in conjunction with '-l all'.
|
||||
This function will enable you to 'reprocess' radiusreport's
|
||||
output, e.g. to email a copy of each users report to them.
|
||||
As of V.02 radiusreport can generate individual files for each user by
|
||||
using the -o flag in conjunction with '-l all'. This function will
|
||||
enable you to 'reprocess' radiusreport's output, e.g. to email a copy
|
||||
of each users report to them.
|
||||
|
@ -1,20 +1,17 @@
|
||||
safecat is a program which implements D. J. Bernstein's
|
||||
maildir algorithm to copy stdin safely to a file in a speci-
|
||||
fied directory. With safecat, the user is offered two assur-
|
||||
ances. First, if safecat returns a successful exit status,
|
||||
then all data is guaranteed to be saved in the destination
|
||||
directory. Second, if a file exists in the destination
|
||||
directory, placed there by safecat, then the file is guaran-
|
||||
teed to be complete.
|
||||
safecat is a program which implements D. J. Bernstein's maildir
|
||||
algorithm to copy stdin safely to a file in a specified directory. With
|
||||
safecat, the user is offered two assurances. First, if safecat returns
|
||||
a successful exit status, then all data is guaranteed to be saved in the
|
||||
destination directory. Second, if a file exists in the destination
|
||||
directory, placed there by safecat, then the file is guaranteed to be
|
||||
complete.
|
||||
|
||||
When saving data with safecat, the user specifies a destina-
|
||||
tion directory, but not a file name. The file name is
|
||||
selected by safecat to ensure that no filename collisions
|
||||
occur, even if many safecat processes and other programs
|
||||
implementing the maildir algorithm are writing to the direc-
|
||||
tory simultaneously. If particular filenames are desired,
|
||||
then the user should rename the file after safecat com-
|
||||
pletes. In general, when spooling data with safecat, a sin-
|
||||
gle, separate process should handle naming, collecting, and
|
||||
deleting these files. Examples of such a process are dae-
|
||||
mons, cron jobs, and mail readers.
|
||||
When saving data with safecat, the user specifies a destination
|
||||
directory, but not a file name. The file name is selected by safecat to
|
||||
ensure that no filename collisions occur, even if many safecat processes
|
||||
and other programs implementing the maildir algorithm are writing to the
|
||||
directory simultaneously. If particular filenames are desired, then the
|
||||
user should rename the file after safecat completes. In general, when
|
||||
spooling data with safecat, a single, separate process should handle
|
||||
naming, collecting, and deleting these files. Examples of such a
|
||||
process are daemons, cron jobs, and mail readers.
|
||||
|
@ -1,7 +1,7 @@
|
||||
Mirfak is an open-source mod_frontpage reimplementation that
|
||||
is more secure, and can be used with a binary installation
|
||||
of Apache (possibly including mod_ssl, php, etc).
|
||||
Mirfak is an open-source mod_frontpage reimplementation that is more
|
||||
secure, and can be used with a binary installation of Apache (possibly
|
||||
including mod_ssl, php, etc).
|
||||
|
||||
This module replaces the Apache-FP patches and module sup-
|
||||
plied with the Microsoft FrontPage Server Extensions
|
||||
available from Microsoft and Ready-to-Run Software.
|
||||
This module replaces the Apache-FP patches and module supplied with the
|
||||
Microsoft FrontPage Server Extensions available from Microsoft and
|
||||
Ready-to-Run Software.
|
||||
|
@ -1,26 +1,23 @@
|
||||
The Webalizer is a web server log file analysis program
|
||||
which produces usage statistics in HTML format for viewing
|
||||
with a browser. The results are presented in both columnar
|
||||
and graphical format, which facilitates interpretation.
|
||||
Yearly, monthly, daily and hourly usage statistics are pre-
|
||||
sented, along with the ability to display usage by site,
|
||||
URL, referrer, user agent (browser), search string,
|
||||
entry/exit page, username and country (some information is
|
||||
only available if supported and present in the log files
|
||||
being processed). Processed data may also be exported into
|
||||
most database and spreadsheet programs that support tab
|
||||
delimited data formats.
|
||||
The Webalizer is a web server log file analysis program which produces
|
||||
usage statistics in HTML format for viewing with a browser. The results
|
||||
are presented in both columnar and graphical format, which facilitates
|
||||
interpretation. Yearly, monthly, daily and hourly usage statistics are
|
||||
presented, along with the ability to display usage by site, URL,
|
||||
referrer, user agent (browser), search string, entry/exit page, username
|
||||
and country (some information is only available if supported and present
|
||||
in the log files being processed). Processed data may also be exported
|
||||
into most database and spreadsheet programs that support tab delimited
|
||||
data formats.
|
||||
|
||||
The Webalizer supports CLF (common log format) log files, as
|
||||
well as Combined log formats as defined by NCSA and others,
|
||||
and variations of these which it attempts to handle intelli-
|
||||
gently. In addition, wu-ftpd xferlog formatted logs and
|
||||
squid proxy logs are supported.
|
||||
The Webalizer supports CLF (common log format) log files, as well as
|
||||
Combined log formats as defined by NCSA and others, and variations of
|
||||
these which it attempts to handle intelligently. In addition, wu-ftpd
|
||||
xferlog formatted logs and squid proxy logs are supported.
|
||||
|
||||
Gzip compressed logs may now be used as input directly. Any
|
||||
log filename that ends with a '.gz'xtension will be assumed
|
||||
to be in gzip format and uncompressed on the fly as it is
|
||||
being read. In addition, the Webalizer also supports DNS
|
||||
lookup capabilities if enabled at compile time.
|
||||
Gzip compressed logs may now be used as input directly. Any log
|
||||
filename that ends with a '.gz'xtension will be assumed to be in gzip
|
||||
format and uncompressed on the fly as it is being read. In addition,
|
||||
the Webalizer also supports DNS lookup capabilities if enabled at
|
||||
compile time.
|
||||
|
||||
The OpenBSD port enables Reverse-DNS lookup by default.
|
||||
|
@ -1,17 +1,18 @@
|
||||
Fvwm95 is a hack based on fvwm2.x. It tries to emulate the good features of a
|
||||
well known product without bloating the regular fvwm code.
|
||||
Fvwm95 is a hack based on fvwm2.x. It tries to emulate the good
|
||||
features of a well known product without bloating the regular fvwm code.
|
||||
|
||||
The main aspects are:
|
||||
|
||||
* A familiar look and feel. It can be interesting for users moving from the
|
||||
MS-World to Unix, or for those who have to switch regularly between the two.
|
||||
Or for those that simply would like to have the same MS look and feel in
|
||||
Unix, or for those that just want to have another window manager, or... But
|
||||
before all, it's meant to be useful, simple and efficient.
|
||||
* A familiar look and feel. It can be interesting for users moving from
|
||||
the MS-World to Unix, or for those who have to switch regularly
|
||||
between the two. Or for those that simply would like to have the same
|
||||
MS look and feel in Unix, or for those that just want to have another
|
||||
window manager, or... But before all, it's meant to be useful, simple
|
||||
and efficient.
|
||||
|
||||
* Same flexible and easy configuration as the native fvwm.
|
||||
* Same flexible and easy configuration as the native fvwm.
|
||||
|
||||
* Functionality extensible via loadable modules.
|
||||
* Functionality extensible via loadable modules.
|
||||
|
||||
* A taskbar: find quickly an application window and don't take space with icon
|
||||
windows.
|
||||
* A taskbar: find quickly an application window and don't take space
|
||||
with icon windows.
|
||||
|
@ -1,21 +1,22 @@
|
||||
Qvwm is a Windows 95/98/NT like window manager for X Window System. It allows
|
||||
Windows 95/98/NT users to use X Window System without hesitation and X Window
|
||||
System users to use Windows 95/98/NT without hesitation.
|
||||
Qvwm is a Windows 95/98/NT like window manager for X Window System. It
|
||||
allows Windows 95/98/NT users to use X Window System without hesitation
|
||||
and X Window System users to use Windows 95/98/NT without hesitation.
|
||||
|
||||
The name qvwm derives from the following: 'q' stands for '9'(same pronunciation
|
||||
in Japanese and almost the same shape) and 'v' for '5'(V is 5 in Roman numerals)
|
||||
Also, qvwm is "98 Window Manager" because 'v' stands for '8'(vertically flipped,
|
||||
V is similar to 8 in kanji characters).
|
||||
The name qvwm derives from the following: 'q' stands for '9'(same
|
||||
pronunciation in Japanese and almost the same shape) and 'v' for '5'(V
|
||||
is 5 in Roman numerals) Also, qvwm is "98 Window Manager" because 'v'
|
||||
stands for '8'(vertically flipped, V is similar to 8 in kanji
|
||||
characters).
|
||||
|
||||
Features:
|
||||
|
||||
* Written with C++ from scratch.
|
||||
* Internationalized without patches.
|
||||
* The same graphics with Windows 95 at a pixel level.
|
||||
* Enables the user to switch among windows using the task switcher.
|
||||
(Alt+Tab)
|
||||
* Enables the user to make some windows taskbar indicators.
|
||||
* Enables the user to move and resize a whole window. (full-drag)
|
||||
* Virtual screen. (extension of Windows 95)
|
||||
* Dialog box on termination.
|
||||
* Titlebar animation on minimizing/maximizing a window.
|
||||
* Written with C++ from scratch.
|
||||
* Internationalized without patches.
|
||||
* The same graphics with Windows 95 at a pixel level.
|
||||
* Enables the user to switch among windows using the task switcher.
|
||||
(Alt+Tab)
|
||||
* Enables the user to make some windows taskbar indicators.
|
||||
* Enables the user to move and resize a whole window. (full-drag)
|
||||
* Virtual screen. (extension of Windows 95)
|
||||
* Dialog box on termination.
|
||||
* Titlebar animation on minimizing/maximizing a window.
|
||||
|
Loading…
Reference in New Issue
Block a user