Free reliably software for linux

ulxmlrpcpp is a library to call methods on a remote server. ulxmlrpcpps main goal is to be as easy to use as possible but be fully compliant. It is object oriented and written in C++.
ulxmlrpcpp is a library to perform calls via XML-RPC in an object oriented approach implemented in C++. It is intended to have simple interfaces and to be easy to learn. But it shall still be fully compliant to the standards and safe in its use.
Unlike other implementations is does not insist on HTTP for transportation but might also accept other ways. For example a simple serial line with a user defined protocol.
This library uses expat as xml parser. In the unlikely case that you dont have it on your system download it from http://expat.sourceforge.net.
The following files are useful to learn more about this library:
- contrib/*
Contributed demos or other useful stuff
- ulxmlrpcpp/tests/*
Validators and test applications. Intended mainly for visual checking.
For the expected output see the according *.out.
val1_[server|client] are most important since they check most of the
functionality several thousand times.
secure_[server|client] demonstrates an approach to send and receive secure calls.
But dont take the encryption algorithm to serious, it is just to show how to do it
basically :-) Replace it by your favourite encryption algorithm.
mt_[server|client] does all the processing in parallel using threads.
- ulxmlrpcpp/apps/*
More or less useful applications in the real world
- ulxmlrpcpp/docs/en/index.html
The handbook with an introduction.
- ulxmlrpcpp/docs/api/html/index.html
The api docs. They are not part of the source distribution. Either download
them from the same place or generate yourself if you have doxygen installed.
Just type "make apidoc" in the the source directory.
In ulxr_config.h/ulxr_config-bcb5.h/ulxr_config-msvc.h/... there are some #defines that might be useful on non-autoconf systems or when you need to set up some things manually after running "configure".
There is also a directory for Borland BCB5 or M$VC++ users with project files. See "bcb5" resp. msvc and its subdirectories with the READMEs.
BCB5 users will want to turn off CodeGuard to increase the speed after they have verified that everything is working correctly with their applications.
ulxmlrpcpp is known to run fine on Linux, OpenBSD and Solaris, Windoze ports are working but not very reliably (BCB5 is ok from my point of view).
Enhancements:
- This release contains several fixes regarding SSL, timeout handling, and code generation.
- There are now more possibilities to create client and server code from sources as well as from introspection.
- The documentation contains examples on how to use the generated files.

Pathfinder PKI Daemon is designed to provide a mechanism for any program to perform RFC3280-compliant path validation of X509 certificates, even when some of the intermediate certificates are not present on the local machine. The project will automatically download any such certificates (and their CRLs) from the Internet as needed using the AIA and CRL distribution point extensions of the certificates it is processing.

By default, the Pathfinder daemon listens on the D-Bus system bus for incoming requests. In this way, any project can easily gain the ability to reliably validate the trustworthiness of X509 certificates. For the convenience of those using OpenSSL or NSS (Netscape Security Services), two libraries containing a callback suitable for use with an SSL connection are provided with the main Pathfinder distribution.

If you are looking for a demonstration of Pathfinder, you may be interested in Pathviewer, which provides a graphical view of path validation via a GTK+ interface.

Jagacy 3270 Emulator is a feature-rich 3270 terminal emulator. It supports SSL, TN3270E, and over thirty languages. The project does not contain the screen-scraping library, and is a cost effective solution for a stand-alone Java 3270 terminal emulator.
The emulator can be configured to help create screen-scraping applications. Developers can also develop their own custom terminal emulators (with automated logon and logoff). Jagacy 3270 screen-scraping is faster, easier to use, and more intuitive than HLLAPI. It excels in creating applications reliably and quickly.
Main features:
- 100% pure Java.
- Feature rich 3270 terminal emulator.
- SSL support.
- Extended TN3270 (TN3270E) support.
- 17 different terminal types (including 132 columns).
- Internationalization support. Over 30 different languages supported.
- Configurable using properties, if desired. No changes necessary when host name or screens change.
- Easily create a custom 3270 terminal emulator.
- Small footprint (less than 150K). Runs efficiently within the Eclipse and NetBeans IDEs.
- Can display the 3270 session in a window while an application is running.
- Includes a full-featured 3270 terminal emulator tailored to developing and debugging applications.
Enhancements:
- Add features/limitations/changes here

pod2man is a Perl module that can convert POD data to formatted *roff input.

SYNOPSIS

pod2man [--section=manext] [--release=version] [--center=string] [--date=string] [--fixed=font] [--fixedbold=font] [--fixeditalic=font] [--fixedbolditalic=font] [--official] [--lax] [--quotes=quotes] [input [output] ...]

pod2man --help

pod2man is a front-end for Pod::Man, using it to generate *roff input from POD source. The resulting *roff code is suitable for display on a terminal using nroff(1), normally via man(1), or printing using troff(1).

input is the file to read for POD source (the POD can be embedded in code). If input isnt given, it defaults to STDIN. output, if given, is the file to which to write the formatted output. If output isnt given, the formatted output is written to STDOUT. Several POD files can be processed in the same pod2man invocation (saving module load and compile times) by providing multiple pairs of input and output files on the command line.

--section, --release, --center, --date, and --official can be used to set the headers and footers to use; if not given, Pod::Man will assume various defaults.

pod2man assumes that your *roff formatters have a fixed-width font named CW. If yours is called something else (like CR), use --fixed to specify it. This generally only matters for troff output for printing. Similarly, you can set the fonts used for bold, italic, and bold italic fixed-width output.

Besides the obvious pod conversions, Pod::Man, and therefore pod2man also takes care of formatting func(), func(n), and simple variable references like $foo or @bar so you dont have to use code escapes for them; complex expressions like $fred{stuff} will still need to be escaped, though. It also translates dashes that arent used as hyphens into en dashes, makes long dashes--like this--into proper em dashes, fixes "paired quotes," and takes care of several other troff-specific tweaks. See Pod::Man for complete information.

OPTION

-c string, --center=string

Sets the centered page header to string. The default is "User Contributed Perl Documentation", but also see --official below.

-d string, --date=string

Set the left-hand footer string to this value. By default, the modification date of the input file will be used, or the current date if input comes from STDIN.

--fixed=font

The fixed-width font to use for vertabim text and code. Defaults to CW. Some systems may want CR instead. Only matters for troff(1) output.

--fixedbold=font

Bold version of the fixed-width font. Defaults to CB. Only matters for troff(1) output.

--fixeditalic=font

Italic version of the fixed-width font (actually, something of a misnomer, since most fixed-width fonts only have an oblique version, not an italic version). Defaults to CI. Only matters for troff(1) output.

--fixedbolditalic=font

Bold italic (probably actually oblique) version of the fixed-width font. Pod::Man doesnt assume you have this, and defaults to CB. Some systems (such as Solaris) have this font available as CX. Only matters for troff(1) output.

-h, --help

Print out usage information.

-l, --lax

Dont complain when required sections are missing. Not currently used, as POD checking functionality is not yet implemented in Pod::Man.

-o, --official

Set the default header to indicate that this page is part of the standard Perl release, if --center is not also given.

-q quotes, --quotes=quotes

Sets the quote marks used to surround C text to quotes. If quotes is a single character, it is used as both the left and right quote; if quotes is two characters, the first character is used as the left quote and the second as the right quoted; and if quotes is four characters, the first two are used as the left quote and the second two as the right quote.

quotes may also be set to the special value none, in which case no quote marks are added around C text (but the font is still changed for troff output).

-r, --release

Set the centered footer. By default, this is the version of Perl you run pod2man under. Note that some system an macro sets assume that the centered footer will be a modification date and will prepend something like "Last modified: "; if this is the case, you may want to set --release to the last modified date and --date to the version number.

-s, --section

Set the section for the .TH macro. The standard section numbering convention is to use 1 for user commands, 2 for system calls, 3 for functions, 4 for devices, 5 for file formats, 6 for games, 7 for miscellaneous information, and 8 for administrator commands. There is a lot of variation here, however; some systems (like Solaris) use 4 for file formats, 5 for miscellaneous information, and 7 for devices. Still others use 1m instead of 8, or some mix of both. About the only section numbers that are reliably consistent are 1, 2, and 3.
By default, section 1 will be used unless the file ends in .pm in which case section 3 will be selected.

EXAMPLES

pod2man program > program.1
pod2man SomeModule.pm /usr/perl/man/man3/SomeModule.3
pod2man --section=7 note.pod > note.7

If you would like to print out a lot of man page continuously, you probably want to set the C and D registers to set contiguous page numbering and even/odd paging, at least on some versions of man(7).

troff -man -rC1 -rD1 perl.1 perldata.1 perlsyn.1 ...

To get index entries on stderr, turn on the F register, as in:

troff -man -rF1 perl.1

The indexing merely outputs messages via .tm for each major page, section, subsection, item, and any X directives.

Vshnu project is a visual shell for Linux/Unix finally done right. Best used as an optional color visual mode to a regular command line shell, vshnu is handy for powerful directory listing and navigation, Unix command assembly, special actions on file types, and fileset handling. Written in Perl for portability and high configurability, it also provides the advantages of a Perl interpreter as part of your Unix shell environment.
Skilled Unix users know the importance of the shell or command line interface (CLI). (Old-time Unix users didnt even have a choice about it). While having more of a learning curve than a graphical user interface (GUI), it permits powerful, creative, complex operations to be specified quickly and reliably. For anyone but the superficial user, learning a CLI is an investment that pays off rewardingly. Command line environments are still readily usable over low-bandwidth network connections and restricted displays.
However, when one is concerned about file manipulation and management (which is a very good thing to be concerned about as the basis of your interface, as most GUIs would rather lead you to forget), a CLI can be a frustratingly terse interface to the filesystem. Too many tedious ls(1) and cd(1) commands are needed to keep watch on whats there. A GUI file manager can address this problem, but then youre in mouseland and have lost the advantages of the CLI.
Enter the visual shells. Not a new idea, visual shells can operate within an entire terminal or console screen. File listings are displayed for your constant reference. Common commands and operations can typically be performed in fewer keystrokes in a visual interface. As the vi(1) visual editor evolved from the ed(1) and ex(1) command line editors, visual shells have attempted to evolve from command line shells. Some visual shells have promoted themselves as simpler menu-oriented interfaces suitable for novices, while others emphasize more expert functionality.
Nonetheless, visual shells have never really caught on, except some in certain circles such as Emacs "dired" mode and the Midnight Commander program. I believe this is because they have been designed as largely self-contained applications with limited configurability. Using a visual shell has required a significant jump into a new base interface tool, and few are so compelling or standard to make that worthwhile.
Hence the design of vshnu, the New Visual Shell. In the Unix tradition, it works with things already there and fills a empty niche. When incorporating it into your Unix environment, you keep your command line shell, your editor, your pager, and access to all your tools, tricks and know-how.
Vshnu can operate as an optional supplemental visual mode to your command line shell. You switch between command line and visual mode easily as you wish. Your interface bandwidth and power for Unix operations is on a higher plane and life gets sweeter. In addition, being written in Perl, it ports to any Unix system without compilation, gives you the advantages of a Perl interpreter running readily at hand, and permits visual command customizability limited only by your creativity, yet doesnt require knowledge of Perl for normal usage. Vshnu is a tool thats worthwhile even if only used occasionally as an interactive, pageable, color ls(1), yet still pays back, with interest, whatever more you put into using it.
Main features:
- Extensive options for sorting and listing a directorys files
- Multiple methods for navigating directories and selecting files
- Directory locations may be marked for quick returns
- Lists command outputs alongside files, including a builtin "ls -l"
- Directory and file histories
- In color terminals, uses color for more informative displays, including file coloring by type via the standard LS_COLORS environment variable
- Expands and collapses chosen subdirectories
- Option to display Internet (Swatch) time
- Multiple methods for choosing and operating on individual or arbitrary sets of files
- Key commands and file actions are 100% configurable, extensible, self-documenting and arbitrarily complex, including multiple choice options
- File actions are customizable by file name/type/contents/etc, with common actions configured by default
- Online help descriptions of key commands and file actions, by mode and by command
- Separate per-site and per-user configurability
- Adjustable file column displays
- Adapts to changing screen sizes (but works best on screens 80 characters wide or more)
- Current directory and environment is propogated between vshnu and the parent command line shell
- Multiple interfaces for shell commands and Perl statements
- Perl statements may be {{embedded}} within shell commands
- A Perl "where" clause to subset the displayed files
- Can use the CD_PATH environment variable as a search path for files and directories
- Recognizes the following standard environment variables: DISPLAY, EDITOR, HOME, HOST, LS_COLORS, MAIL, PAGER, PATH, PERL_RL, SHELL and VISUAL

SubEthaSMTP is an easy to understand Java library that provides a receptive SMTP server component.
By plugging this component into your Java application, you can easily receive SMTP mail using a simple abstract Java interface.
Also included is a small sub-project called Wiser, an easy to use incoming mail testing framework.
Main features:
- A mailing list manager (ie, SubEtha Mail)
- A mail server that delivers mail to user inboxes
- A mail archiver like Mail Archive
- An email test harness (Implemented in this project. Its called Wiser.)
SubEthaSMTP was split out of the SubEtha Mail mailing list manager because it is a useful standalone component. When we wrote SubEtha, the last thing we wanted to do was write our own SMTP server. In our search for a modular Java SMTP component, we examined:
Apache JAMES
JBoss Mail Server
Dumbster
Jsmtpd
JES
Java Mail Server
Since youre reading this page you probably already know what we found: Six different SMTP implementations without the slightest thought given to reusability. Even Jstmpd, which purports to be a "A Modular Java SMTP Daemon", isnt. Furthermore, even though JBoss Mail is in active development, the team was unintersted in componentization of the SMTP processing portion of their server.
During the development of SubEthas testing harness, we tried out the Dumbster software and found that not only was the API difficult to use, it did it not work properly, the developer has not done any development on it in about a year and it does not work reliably on Mac OS X. With two simple classes we re-implemented it as an included project called Wiser.
We hate reinventing wheels. This should be the LAST FREAKING JAVA SMTP IMPLEMENTATION.
Enhancements:
- This release fixes a couple of bugs with SMTP RFC handling.

Tiger Envelopes is an easy way to get your email privacy back.
With Tiger Envelopes you use email just like you always have with everyone. And, without you doing anything, your messages are private with people who use envelopes.
The mission of Tiger Envelopes is to make private email easy.
Theres a tradeoff between ease of use and security. For too many years some security professionals have said any privacy thats not perfect is worse than worthless. They say it creates a false sense of security.
No one has a false sense of security about envelopes. Theyre made of paper. But we know theyre much more private than messages without envelopes, such as postcards or email.
Tiger gives you envelopes for your email.
Envelopes comes in two versions, Free and Business.
Tiger Free Envelopes is free in both senses, gratis and libre. It is released under the GPL.
Tiger Business Envelopes is commercial. Its based on Tiger Free Envelopes and adds support plus advanced features businesses need. Source code is included for security audits, but its not GPL.
Enhancements:
- Improved imap support for Thunderbird.
- Start Envelopes from the installer during new installations more reliably.
- Change welcome email message to "what to do" message.
- Save options if installer canceled and options changed.
- Shortened the message in the installers final panel.
- Include how to start the control panel on Linux.
- Removed welcome message from control panel.
- Fixed net.n3.nanoxml.StdXMLParser so searches for dtd in jar files when offline.
- Called closeSession() if user, password, or remote host invalid.
- Improved error messages if remote host not found.
- Ignore files starting with . in the notices directory.
- Created ProxyUser class to manage client and remote user data in proxies.
- Removed thirdparty source that we havent customized.
- Added thirdparty/lib directory with unmodified third party jar files.
- Added setChanged() to envelopes.io classes.
- Delete email accounts from options after theyre anonymized.
- Send notice if Tiger account not defined for a POP3 account.
- Send error message to mail client if POP3 command invalid.
- Validate POP3, IMAP, and SMTP commands from mail client.
- Send 252 response code when VRFY requested of SMTP proxy.
- Send 550 response code when EXPN received by SMTP proxy.