Free https software for linux

displaytag library is an open source suite of custom tags that provide high-level web presentation patterns which will work in an MVC model. The library provides a significant amount of functionality while still being easy to use.
The display tag library can display tables! Give it a list of objects and it will handle column display, sorting, paging, cropping, grouping, exporting, smart linking and decoration of a table in a customizable XHTML style.
Enhancements:
- Fixed some remaining https issues when saving exported files in Internet Explorer with the export filter enabled.
- fix-autolink working with https://, ftp://, etc. Fixes DISPL-150.
- fix-Column body is not rendered when requesting an invalid page. Fixes DISPL-136.
- I18n Struts Adapter now works with Struts 1.1. Fixes DISPL-149.
- fix-Performance optimization: reduce the use of temporary StringBuffers while building the html table. Fixes DISPL-156.
- fix-Sporadic error with factory.requestHelper. Fixes DISPL-148.
- DisplayTag is now able to load displaytag.properties from a different classloader (allows displaytag.jar to be placed in appserver shared libs). Fixes DISPL-144.
- fix-Center of paging banner number. Fixes DISPL-109.
- fix-Tag holding references to resources. Fixes DISPL-145.
- fix-Export of nested tables: now you can export the parent table without errors; nested tables are not included during export. Fixes DISPL-142.

SSL Proxy server listens on a TCP port, accepts SSL connections, and forwards them to another local or remote TCP port.
For example, it is possible to create an HTTPS server if you have an HTTP server and you run an SSL Proxy server on port 443 which forwards the connections to port 80.
SSL Proxys design makes it as secure as possible and still perform well.
Enhancements:
- Improved certificate handling (chained certificates are now supported), more error information on SSL protocol errors during SSL_accept(), -U and -D options (buffer size), and a "powered by" logo.

myPMS is a free password management application which will require you to remember only one password making the management of your important passwords simple.
myPMS is a web-based password management application which means it can be accessed from anywhere. It uses simple HTML, PHP and a MySQL database to store your passwords.
Main features:
- Search by host name or drop-down list
- Capability to store application and host associated with password
- Date inserted stored
- Who inserted or updated password stored
- Unlimited password history
- "Invisible" password until mouse curser hovers over password
- Fade to blank page after 60 seconds for additional security
- Database creation using simple MySQL batch file
- HTTPS (SSL) capability if you require

WebTst is a Web development test infrastructure. It aims to simplify testing by implementing an HTTP and HTTPS capture engine: a Web proxy which records a testers actions using any Web browser and then replays them during testing.
It comes with support for cookie handling, HTTP authentication, concurrency testing, digital certificates, and a number of simple tests, such as cookie setting, pattern matching, response status, and many others.
It also provides the concept of result analyzer components and capabilities for maintaining smoke and regression test suites.
Enhancements:
- This is a major bugfix release, and upgrading is highly recommended for existing users.
- Support was added for XML::Dumper 0.4 (backwards compatibility) and above, and an upgrade script was developed.
- Major fixes were made to handling of interceptor responses (content transfer chunking, status 100 handling).
- Post body content storage was reworked to allow for binary data types.
- The dashboard interface was reworked to allow downloading and viewing of post bodies.
- Interceptor was fixed to properly capture HTTPS hostnames.
- A minor fix was made to the playback_results directory location when running multiple recordings via suiteRunner.pl.

Lua Messaging Engine (LuME) is a set of scripts that offer abstract functions for communication via AOLs OSCAR protocol (as used by ICQ and AIM clients), Microsoft Messengers MSNP, and Yahoos YIM protocol. Lua Messaging Engine also includes utility functions for string operations, SHA hashing, and basic HTTPS communication.

An increasing number of software developers are making use of the simplicity and power behind employing a Lua script interface.

Meetroduction, LLC has been using a Lua script interface as a core design concept for the multi protocol messaging component of its proximity based people finder client: Meetro. Beyond that, the interface offers its users a flexible way to vastly extend the clients functionality.

mod_urlscheme is an Apache 1.3/2.0/2.2 module that allows the Apache configuration author control over the scheme to use when constructing self-referential URLs.
Please note that this module is different from mod_scheme, which embeds the Tinyscheme interpreter into Apache. You can find that module here. I changed the name from mod_scheme to mod_urlscheme to avoid confusion.
The original module was only written to work on Apache 2.0. There is now also a version for Apache 1.3 + EAPI, although it wont work with stock 1.3. Please see the "Apache 1.3" section at the bottom of this page for details. The 2.0 module will work almost unchanged on Apache 2.2. There is a small naming change in the API that requires a slightly different version.
In several situations, Apache will attempt to construct a URL that will point to itself and will deliver the result to the client. The most notable occasion for this is when Apache is constructing a client redirect. This can for example happen when the client requests a URL that maps to a directory but doesnt include a trailing slash: Apache will send back a redirect to the same URL, but with a trailing slash appended. Other occasions include Redirect directives in the Apache configuration, or mod_proxy rewriting redirects coming from a backend server (when mod_proxy is functioning as a reverse proxy).
A self-referential URL has four distinct major components: the scheme, the hostname, the port number and the request URI, the latter including perhaps a query string and a fragment identifier. The combination of ServerName, UseCanonicalName and the use of the clients HTTP Host header allows an Apache administrator full control over the hostname and port number part of the generated URLs, but the scheme is up to Apache itself.
Normally, the scheme is always "http". A module such as mod_ssl will override this and set the scheme to "https" for those locations where it is active. But that doesnt help you when the Apache server is behind another server that will handle the HTTPS traffic for you. Imagine the following layered approach:
- The clients HTTPS request comes in to the first machine on port 443 (the default port for HTTPS). The first machine, which perhaps has dedicated hardware to speed up SSL processing, accepts the connection and provides for all the encryption/decryption. It forwards the decrypted request as a regular HTTP request to port 81 on the next machine.
- The second machine runs Apache. It will be listening on ports 80 and 81. It will receive the request from the first machine on port 81. The fact that its coming in on that port establishes the request as being secure, and Apache may provide different processing rules depending on whether the request is secure or not. (Of course, the Apache server should be behind a firewall, so a client cant connect to port 81 directly and circumvent the access controls.)
Now, if Apache for some reason needs to generate a redirect, the scheme on the redirect URL will be "http", because thats what Apache is serving. But that URL isnt valid on the outside: the scheme should be "https", so that the client will proceed to get the new URL from the same secure location.
One solution is to let the machine that handles the SSL work do the rewrite from http://www.example.com:81/ to https://www.example.com/. But that doesnt help you if the first machine is (for example) a dumb SSL tunnel that doesnt understand HTTP. In that case, Apache will need to be convinced its scheme is actually "https", not "http".
Thats where mod_urlscheme comes in.
Installation:
These instructions assume a Unix installation. For other systems, please consult the Apache documentation. mod_urlscheme is a very simple module that requires no special treatment. Simply put, if you can build mod_example from the stock Apache tree, then you can build mod_urlscheme as well.
Put the downloaded mod_urlscheme.c file in a temporary directory somewhere where you will compile it.
If you want to include mod_urlscheme as a static module in your Apache server, prepare your Apache source directory as per the Apache build instructions. When calling the ./configure command, include the option --with-module=experimental:/path/to/mod_urlscheme.c (for Apache 1.3: --add-module=/path/to/mod_urlscheme.c). You need to specify the full path to the source file after the colon. Then, proceed with the build instructions as you would normally. The module will be included in your Apache binary as a static module.
For a dynamic module, first install a full Apache distribution, including the apxs tool and the C headers. If you install from pre-packaged bundles, such as RPMs, you may need to separately install the development package. On RPM-based systems that usually means you need to have the httpd-devel package installed. You will also need a fully functional compiler suite installed.
Go to the directory where you put the mod_urlscheme.c file and run apxs -c mod_urlscheme.c. Refer to the Apache documentation to see if you need to specify more command line options for your system.
If the compile succeeded, you will now have a dynamic Apache module ready to use. You may need to look in the .libs subdirectory to find the actual mod_urlscheme.so file (under Unix, that is). Copy the module to the Apache module directory, which is the modules subdirectory of the server root (for Apache 1.3: the libexec subdirectory). Alternatively, you can put it in any other location; just make a note of where you put it, so you can refer to the location later on.

Evolution Jescs is the Evolution Connector for Sun Java Enterprise System Calendar Server (SJESCS), which adds support for SJESCS 5.1 and above to Evolution.

This connector supports the WCAP (Web Calendar Access Protocol) 2.0, 3.0, 3.1.

How to setup a JESCS account?

Now it is integrated into "Mail Accounts" under menu "Edit-->Preferences". Click "Add" button to bring up the account setup widzard. In "Identity" page, please input your Full Name and Email Address. In "Receiving Email" page, choose "Sun Calendar WCAP" as the Server Type. Input Host and Username here.

If your server listens to another port instead of the default one (80 for http, 143 for https), please input Host in the "Host:Port" format, such as "calendar.sun.net:8080". For "Use Secure Connection", please choose "Never" for http and "Always" for https.

In "Receiving Options" page, if you want to poll the server for new events and tasks at a different interval than the default 30 minutes, please check the checkbox and choose a interval. Please note that a small interval setting will impact the performance of the connector. If you are sure you are the only one accessing your calendar, you can set the interval to a very large number.

The "Sending Email" page actually is useless for the connector. You can just input anything here so that you can go forward.

In "Account Management" page, please enter your account name here. Then you can finish your JESCS account setting.