|
| 1 | +---- |
| 2 | +Zorp |
| 3 | +---- |
| 4 | + |
| 5 | +*Zorp GPL* is a next generation, open source proxy firewall with deep protocol analysis. It allows you to inspect, control, and modify traffic on the application layer of the ISO/OSI model. Decisions can be made based on data extracted from the application-level traffic (for example, HTTP) and applied to a certain traffic type such as users or client machines. It ensures that the traffic complies with the particular protocol standards, and allows you to perform specific actions with the traffic. |
| 6 | + |
| 7 | +Why choose it? |
| 8 | + |
| 9 | +* Free license and active community support |
| 10 | +* Network traffic analysis in 7 protocols |
| 11 | +* Encrypted channel control |
| 12 | +* Content filtering and optional modification |
| 13 | +* Modular, highly flexible configuration |
| 14 | +* The only answer to many unique problems |
| 15 | +* Established project with a 10-year history |
| 16 | + |
| 17 | +Features |
| 18 | +======== |
| 19 | + |
| 20 | +Access control |
| 21 | + Access control in *Zorp GPL* has a lot more possibilities than average firewalls. It is based on zones instead of hosts or IP ranges and besides “who” and “what”, it can also limit “how”. For example, clients arriving from one zone can only read a given FTP server, whereas others have write privileges. |
| 22 | + |
| 23 | +Information leakage prevention |
| 24 | + Information leakage prevention helps to keep sensitive information inside your network. For example, HTTP data flow could include internal IP addresses, the URL of a previously visited website (referrer), or browser and operating system information (agent). *Zorp GPL* is able remove or change this information. |
| 25 | + |
| 26 | +Content filtering |
| 27 | + Content filtering is done by using external applications, like virus scanners, spam filters and URL checkers. Connections can be accepted, rejected or just simply logged. Suspicious content can be quarantined. *Zorp GPL* can integrate with all popular antivirus engines, such as NOD32 or AMaVIS. |
| 28 | + |
| 29 | + Supported protocols: |
| 30 | + |
| 31 | + * wildly used procols: *HTTP*, *FTP*, *SMTP*, *POP3* |
| 32 | + * rarely used: *Finger*, *Whois*, *Telnet* |
| 33 | + * secure: *HTTPS*, *FTPS*, *POP3S*, *SMTPS* |
| 34 | + |
| 35 | +Audit |
| 36 | + Audit of all events is possible, even requests and responses of a protocol, as proxies work at the application level. This can prove not only what happened, but also what did not, for example an old version of a file was deleted, but never uploaded again. |
| 37 | + |
| 38 | +Interoperability |
| 39 | + Interoperability helps in a world where not all protocol implementation is created equal. *Zorp GPL* is able to hide protocol features, like compression from HTTP, translate between different encryption standards, and other changes to make clients and servers interoperate more easily. |
| 40 | + |
| 41 | +Flexibility |
| 42 | + Flexibility is a key feature of *Zorp GPL*. It is easily extendable by additional modules and customizable to solve specific security problems. |
| 43 | + |
| 44 | +Linux support |
| 45 | + *Zorp GPL* administrators can compile and run the product on several Linux-based operating systems. Besides that, pre-compiled binaries are readily available on various Linux distributions, which greatly simplifies its installation on these platforms. Currently binary repositories are available for the following distributions: |
| 46 | + |
| 47 | + * *Debian*: squeeze, unstable; (i386, amd64) |
| 48 | + * *Ubuntu*: from 10.04 (i386, amd64) |
| 49 | + |
| 50 | +Community |
| 51 | +========= |
| 52 | + |
| 53 | +Please join our increasing *Zorp GPL* community by subscribing to one or more of the following forums. |
| 54 | + |
| 55 | +* `FaceBook <https://www.facebook.com/pages/Zorp-GPL/239692256091025>`_ |
| 56 | +* `Google+ <https://plus.google.com/115296005910438881857>`_ |
| 57 | +* `LinkedIn <http://www.linkedin.com/groups/Zorp-GPL-4166962>`_ |
| 58 | +* `Twitter <https://twitter.com/ZorpGPL>`_ |
| 59 | + |
| 60 | +Downloads |
| 61 | +========= |
| 62 | + |
| 63 | +Sources |
| 64 | +^^^^^^^ |
| 65 | + |
| 66 | +* `Zorp GPL <http://github.com/balabit/zorp>`_, the firewall itself |
| 67 | +* `kZorp <http://github.com/balabit/kzorp>`_, kernel module |
| 68 | +* `libzorpll <http://github.com/balabit/libzorpll>`_, low-level networking library |
| 69 | + |
| 70 | +Binaries |
| 71 | +^^^^^^^^ |
| 72 | + |
| 73 | +* *Zorp GPL* packages from `Debian <http://packages.debian.org>`_ and `Ubuntu <http://packages.ubuntu.com>`_ distribution |
| 74 | +* *Zorp GPL* and related packages for Debian and Ubuntu distribution on `MadHouse Project <http://asylum.madhouse-project.org/projects/debian>`_ |
| 75 | + |
| 76 | +Support |
| 77 | +======= |
| 78 | + |
| 79 | +Mailing lists |
| 80 | +^^^^^^^^^^^^^ |
| 81 | + |
| 82 | +* Subscribe to the lists directly in `English <https://lists.balabit.hu/mailman/listinfo/zorp>`_ or `Hungarian <https://lists.balabit.hu/mailman/listinfo/zorp>`_ |
| 83 | +* List archives are available at the above URLs |
| 84 | + |
| 85 | +Documentation |
| 86 | +^^^^^^^^^^^^^ |
| 87 | + |
| 88 | +* `Zorp GPL Tutorial <http://zorp-gpl-tutorial.readthedocs.org>`_ on ReadTheDocs |
| 89 | +* `Configuration examplesGitHub <http://github.com/balabit/zorp-examples>`_ on GitHub |
| 90 | + |
| 91 | +Evaluate |
| 92 | +^^^^^^^^ |
| 93 | + |
| 94 | +There is a set of `virtual machines <http://people.balabit.hu/szilard/zorp-gpl/virtual-machines/>`_ to test *Zorp GPL*. |
| 95 | + |
| 96 | +License |
| 97 | +======= |
| 98 | + |
| 99 | +* *Zorp GPL* is licensed under `GPL 2.0 <http://www.gnu.org/licenses/gpl-2.0.html>`_ |
| 100 | +* *kZorp* is licensed under `GPL 2.0 <http://www.gnu.org/licenses/gpl-2.0.html>`_ |
| 101 | +* *libzorpll* is licensed under `LGPL 2.0 <http://www.gnu.org/licenses/lgpl-2.0.html>`_ |
0 commit comments