MQ Channel Auto Creation Manager (MQCACM) is an MQ Channel Auto-Definition (MQ CHAD) exit which allows a company to control and restrict incoming connection requests to auto-create a channel. MQCACM is invoked when a request is received to start an undefined Receiver, Server-Connection, Cluster-Receiver, or Cluster-Sender channel. MQCACM can modify or clear the supplied default channel definition values for an instance of the channel, so there is no exit incompatibility (cross-platform or otherwise).
jPDFSecure is a Java library which can digitally sign PDF documents and change security settings on PDF Documents. With jPDFSecure, your application or Java applet can encrypt PDF documents, set permissions and passwords, and create and apply digital signatures. jPDFSecure is optimized for performance and is built on top of Qoppa's proprietary PDF technology, so there is no need for any third party software or drivers. jPDFSecure has a simple interface to load PDF documents from files, network drives, URLs, and even input streams, which can be generated at runtime or come directly from a database. After changing security settings, jPDFSecure can save the document to a file, a java.io.OutputStream, or a javax.servlet.ServletOutputStream when running in a J2EE application server to output the file directly to a browser. jPDFSecure is platform-independent and can be used in any environment which supports Java.
MQ Message Encryption (MQME) is a solution that provides encryption for WebSphere MQ message data while it resides in a queue and in the MQ logs. It uses AES and offers the ability to control who accesses protected queues. This control is obtained through the use of UserID grouping, and group files are similar to the Unix /etc/group file. It also has the ability to generate and validate messages using a SHA-2 digital signature.
Moscrack is a WPA cracker for use on clusters. It supports MOSIX, SSH, and RSH connectivity and works by reading a word list from STDIN or a file, breaking it into chunks, and passing those chunks off to separate processes that run in parallel. The parallel processes are then executed on different nodes in your cluster. All results are checked and recorded on your master node. Logging and error handling are taken care of. It is capable of running reliably for long periods of time, without the risk of losing data or having to restart. Moscrack uses aircrack-ng by default. Pyrit for WPA cracking and Dehasher for Unix password hashes are supported via plugins.
MQ Standard Security Exit is a solution that allows a company to control and restrict who is accessing a WebSphere MQ resource. The security exit will operate with WebSphere MQ v6.0, v7.0, v7.1, or v7.5 in Windows, IBM i (OS/400), Unix, and Linux environments. It works with Server Connection, Receiver, Requestor, and Cluster-Receiver channels of WebSphere MQ queue manager. The MQ Standard Security Exit solution is comprised of a server-side security exit.
MQ Channel Encryption (MQCE) is a solution that provides AES encryption for message data flowing between WebSphere MQ (WMQ) resources. It operates with Sender, Receiver, Server, Requestor, Cluster-Sender, Cluster-Receiver, Server Connection, and Client Connection channels of the WMQ queue managers. It is a simple drop-in solution and can be configured as a queue manager channel message exit or as a channel sender/receive exit pair.
MQ Authenticate User Security Exit (MQAUSX) is a solution that allows a company to fully authenticate a user who is accessing a WebSphere MQ resource. It verifies the user's user ID and password (and possibly domain name) against the server's native OS system (or domain controller) or a remote LDAP server. The security exit will operate with WebSphere MQ v6.0, v7.0, v7.1, or v7.5 in Windows, iSeries (OS/400), Unix, and Linux environments. It works with Server Connection, Client Connection, Sender, Receiver, Server, Requestor, Cluster-Sender, and Cluster-Receiver channels of WebSphere MQ queue manager. The MQ Authenticate User Security Exit solution is comprised of 2 components: client-side security exit and server-side security exit.
For high traffic Web sites, Proto Balance Advanced provides connection rate limiting per second and limits the total number of connections. Both are done on a per-client basis. It has a complete Web configuration interface. The IP address of each connecting Web browser is recorded along with its connection stats. It is scalable to millions of clients and handles 10,000 concurrent connections. It performs server backend load balancing with an on-the-fly capability to add and remove servers. Daily and weekly traffic graphs are shown.