Search Results for "client"

...It typically protects web apps from attacks such as SQL injection, XSS, code injection, os command injection, CRLF injection, LDAP injection, XPath injection, RCE, XXE, SSRF, path traversal, backdoor, brute force, HTTP-flood, bot abuse, among others. By deploying a WAF in front of a web application, a shield is placed between the web application and the Internet. While a proxy server protects a client machine’s identity by using an intermediary, a WAF is a type of reverse-proxy, protecting the server from exposure by having clients pass through the WAF before reaching the server. A WAF protects your web apps by filtering, monitoring, and blocking any malicious HTTP/S traffic traveling to the web application.

A client for the MikroTik RouterOS API protocol, written in PHP. Easy, tested and documented. All feedback welcomed.

...So I written this program -- dynipdrop("dynipdrop" daemon and "ipdrop_local" to send a drop-msg from localhost, and "ipdrop_udp" to send a drop-msg to another server(installed the dynipdrop daemon). And I think: "Maybe I can make a client to drop the ssh-scan, like DenyHost(http://denyhost.sf.net)", so I write the "sshdprotector". dynipdrop run on linux and need iptables, I use "portsentry(http://sourceforge.net/projects/sentrytools/" + "sshdprotect" + "dynipdrop" to protect my servers, and hope this software make some help to you.

...Support for versions 4 and 5 of SOCKS protocol. Designed to be easily expandable to support different encryption/authentication/authorization methods. Sample server and client are available.

Telnet over HTTP proxy. Allows users behind firewalls to tunnel Telnet sessions over a HTTP connection. Server uses Java servlets with a Java or C# client.

Server/client suite which provides per-user access control/firewall/QOS. Robust and high speed implementation is secure against MAC/IP spoofing, and can scale to large networks with many clients. Options for additional monitoring and captive portal.

A Java implementation of a NAT-PMP client. At the project's inception, there was not a well-known NAT-PMP client library for Java. This project intends to fill the gap.

PACtory is a highly customizable way for handling proxy configuration settings with a dynamically created .pac-File, also known as "Windows Proxy Auto Detection" or "wpad.dat"-File, which is generated on the fly while the client is requesting it.

The IIOP Toolset provides a graphical user interface to analyze end-to-end connectivity thru firewalls and NAT-gateways between the location of CORBA client and the service endpoint of the CORBA server.

Forwards non-NTLM HTTP client requests to an NTLM proxy server (ie. Microsoft IAS). Can also forward a local port to a remote machine.

WarpTunnel is a porting of http tunnel 3.3 from C into .NET C# platform. WarpTunnel creates a bidirectional virtual data path tunnelled in HTTP requests through firewall or proxy servers.Support DIGEST proxy & SOCKS4/4a/5.Client for Compact Framework 2.0

really simple (minimal) implemention for client only igd from upnp, contains just enough to allow you to open/delete ports on a upnp router. uses libcurl, libxml2 and libxslt

A Port Knocking C-based server & client. Stealth mode by closed ports, strong encryption (ARC4 & BlowFish), Daemon mode, compresed sequence, MD5 digest log check, user passwords and user privelege system, action triggers... GPL license.

The doorman guards the door of a server, manipulating firewall rules to admit only recognized parties. Allows Silent Running - a server with all ports CLOSED. Linux-BSD-OSX server & client; C source & docs + Windows client binary. GPL.

PfPro is a "fat" client for managing configurations for PF-based firewalls. It is a graphical client-side application for managing multiple firewall configurations.

JWall is not just a java gui for iptables. JWall is a multi firewall management client. A secure rulebase can be built with graphical objects. Rulesets can be pushed to remote firewalls (via ssh). The remote firewall just needs to be Linux with sshd

TCP-Switch currently allows sharing one port for four protocols (SSH, HTTP, HTTPS, passive FTP). Each protocol can be forwarded (tunnel) to a different <host:port>. Future releases will allow much more controll, e.g. client IP/port, and other protocols