Copyright © 1996-2024 Balasys IT Zrt. (Private Limited Company)
Copyright © 2024 Balasys IT Zrt. All rights reserved. This document is protected by copyright and is distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this document may be reproduced in any form by any means without prior written authorization of Balasys.
This documentation and the product it describes are considered protected by copyright according to the applicable laws.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)
Linux™ is a registered trademark of Linus Torvalds.
Windows™ 10 is registered trademarks of Microsoft Corporation.
The Balasys™ name and the Balasys™ logo are registered trademarks of Balasys IT Zrt.
The Zorp™ name and the Zorp™ logo are registered trademarks of Balasys IT Zrt.
AMD Ryzen™ and AMD EPYC™ are registered trademarks of Advanced Micro Devices, Inc.
Intel® Core™ and Intel® Xeon™ are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries.
All other product names mentioned herein are the trademarks of their respective owners.
DISCLAIMER
Balasys is not responsible for any third-party websites mentioned in this document. Balasys does not endorse and is not responsible or liable for any content, advertising, products, or other material on or available from such sites or resources. Balasys will not be responsible or liable for any damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods, or services that are available on or through any such sites or resources.
May 30, 2024
Abstract
This document describes the log messages of Zorp
Table of Contents
List of Procedures
Welcome to the Zorp Professional 7 Log Messages Guide!
This document describes the log messages of the various Zorp components. The messages of each component can be found in their respective chapters. The format of log messages is the following:
Class: The component that sent the log message. For example, core
Verbosity: The verbosity level of the log message. If the log level of the component is lower than the verbosity level of the message, the message is not displayed. For example, 2
Session ID: An identifier that helps to find the log messages related to a particular connection. For example, zorp/intra_HTTP:1/http
Summary: A short description of the event that happened. This part of the message is static and ends with a semicolon (;). Also, this part of the message is used as the title of the section describing the log message in the Zorp 7 Log Messages Guide. For example, Error connecting to remote host;
Dynamic part: The variables or parameter values that apply for the particular event. For example, error='Connection refused'
core.error(2): (zorp/intra_HTTP:1/http): Error connecting to remote host; error='Connection refused'
^ ^ ^ ^
| | | |
+class(verbosity level) | |
| | |
+session_id | |
+Summary |
+Dynamic part
To enable , see Procedure 1, Single-line log message for connections.
Purpose:
Zorp can log a single message for every connection that includes every relevant detail about the connection. That way, it is easy to find a specific connection, and also to process the connection data with external log analyzing tools. To enable logging a single message for every connection that includes every relevant detail about the connection, complete the following steps. This log message contains the following information:
session ID: ID number of the TCP session.
rule ID: The ID number of the firewall rule.
session start time (UNIX timestamp): Date when the connection started (UNIX timestamp).
session end time: Date when the connection was closed (UNIX timestamp).
client proto: The transport protocol used in the client-side connection. This is the protocol used in the transport layer (Layer 4) of the OSI model (for example, TCP, UDP, ICMP, and so on.
client IP: The IP address of the client.
client port: The port number of the client.
client zone: The zone the client belongs to.
server proto: The transport protocol used in the server-side connection. This is the protocol used in the transport layer (Layer 4) of the OSI model (for example, TCP, UDP, ICMP, and so on.
server IP: The IP address of the server connected by Zorp.
server port: The port number of the server connected by Zorp.
server zone: The zone the client belongs to.
client local IP address (after NAT): The IP address of Zorp used in the client-side connection.
client local port (after NAT): The port number of Zorp used in the client-side connection.
server local IP address (after NAT): The IP address of Zorp used in the server-side connection.
server local port (after NAT): The port number of Zorp used in the server-side connection.
verdict: Indicates what Zorp decided about the connection.
ACCEPTED: Zorp accepted the connection, and it was established without any problems.
DENIED_BY_CONNECTION_FAIL: Connection failed, that is, it was allowed to pass Zorp but timed out on the server.
DENIED_BY_LIMIT: Zorp rejected the connection because it exceeded the parameter of the instance, or the parameter of the service.
DENIED_BY_POLICY: Zorp did not find a matching firewall rule for the connection.
DENIED_BY_UNKNOWN_FAIL: The connection failed for some reason.
NO_SERVICE_FOUND: Zorp did not find a matching service for the parameters of the connection.
info: Additional information about the connection (if any).
core.summary(4): (svc/example_service_name:1234): Connection summary; rule_id='N/A' session_start='1406290229', session_end='1406290229', client_proto='TCP', client_address='10.10.1.10', client_port='3394', client_zone='example-zone', server_proto='TCP', server_address='10.10.1.10', server_port='3394', server_zone='example-zone', client_local='10.10.1.10', client_local_port='55268', server_local='10.10.60.253', server_local_port='55258', verdict='ACCEPTED', info='Ending forwarded session' core.summary(4): (svc/example_service_name:1234): Connection summary; rule_id='N/A' session_start='1406290229', session_end='1406290229', client_proto='TCP', client_address='10.10.1.10', client_port='3394', client_zone='example-zone', server_proto='TCP', server_address='10.10.1.10', server_port='3394', server_zone='example-zone', client_local='10.10.1.10', client_local_port='55268', server_local='10.10.60.253', server_local_port='55258', verdict='NO_SERVICE_FOUND', info='No applicable service found for this client & server zone, dropping packet'
Steps:
Login to your Zorp host.
Execute the following commands:
echo 1 > /proc/sys/net/netfilter/kzorp/log_session_verdict zorpctl log --logspec 'core:4'
Repeat this procedure on your other Zorp firewall hosts.
Expected result:
When a connection ends, Zorp logs a single-line log message about the connection, for example:
core.summary(4): (svc/example_service_name:1234): Connection summary; rule_id='N/A' session_start='1406290229', session_end='1406290229', client_proto='TCP', client_address='10.10.1.10', client_port='3394', client_zone='example-zone', server_proto='TCP', server_address='10.10.1.10', server_port='3394', server_zone='example-zone', client_local='10.10.1.10', client_local_port='55268', server_local='10.10.60.253', server_local_port='55258', verdict='REJECTED_BY_POLICY' info=''
This message reports that the connection was successfully established.
This message indicates that the given python function is not callable. Check your AuthenticationProvider methods. @see: Auth.AuthenticationProvider
This message indicate that Zorp failed opening a new socket. It is likely that Zorp reached some resource limit.
This message indicates that Zorp was unable to query the local address.
This message indicates that the setsockopt requesting reception of original destination addresses of UDP frames failed.
This message indicates that the setsockopt requesting reception of original destination addresses of UDP frames failed.
This message indicate that the creation of a new socket failed for the given reason. It is likely that the system is running low on memory, or the system is running out of the available fds.
This message reports that a new dispatcher thread is starting. This is used if threaded dispatching is enabled. @see: Dispatcher
This message reports that the dispatcher thread is exiting. It it likely that Zorp unbinds from that address.
This message indicates that Zorp was unable to create a dispatcher thread for accepting new connection, and it is reverting back to the original non-threaded mode. It is likely that Zorp reached its thread or resource limit. Check your logs for further information.
This message indicates that a new connection was accepted, but no Dispatcher/Proxy was interested in it.
This message indicates that Dispatcher was configured to be accept transparent connections, but it was connected directly. Configure it either non-transparent or deny direct access to it and set up the appropriate TPROXY rule. @see: Dispatcher
This message indicates that a Dispatcher/Proxy was unable bind to a specified address, because another instance is already listening there and specified that only one connection could be accepted.
This message indicates that a Dispatcher/Proxy tries to unbind from the specified address, but have not registered itself to that address.
This message indicates that a Dispatcher/Proxy tries to unbind from the specified address, but Zorp does not bind to that address.
This message serves informational purposes, and indicates that the given module was successfully loaded from the given shared object.
This message indicates that packet stats interval was specified, but no action was configured to handle the event. Check your policy for packetStats event.
Indicates that an invalid session ID is specified by the authorize command
This message reports that Zorp is about to call the proxy's __destroy__() event. This method handles the pre destroy tasks, like the shutdown of the server side connection.
This message indicates an internal error, please contact your Zorp support for assistance.
This message indicates that Zorp was unable to create a new thread for the new proxy instance. It is likely that Zorp reached a thread limit, or not enough resource is available.
A stop request arrived to the proxy. It has to be stopped.
This message indicates that stacking a child proxy failed, because creating an AF_UNIX domain socketpair failed on the client side.
This message indicates that stacking a child proxy failed, because creating an AF_UNIX domain socketpair failed on the server side.
This message reports that Zorp is about to stack a proxy class with the given fds as communication channels.
This message reports that Zorp is about to stack a proxy class with the given fds as communication channels.
This message indicates that stacking a child proxy failed, because creating an AF_UNIX domain socketpair failed for the control channel.
This message reports that Zorp is about to stack a program with the given fds as communication channels.
This message indicates that Zorp began establishing connection with the indicated remote host.
This message indicates that the decision layer denied the given connection.
This message indicates that a Dispatcher on the given local address is started.
This message indicates that Zorp was unable to open the policy file. Check the permissions of your policy file.
This message indicates that Zorp was unable to parse the policy file. Check the logs for further information on where the error occurred in the policy.
This message indicates that Zorp was unable to find the required proxy module. Check your installation, or contact your Zorp support for assistance.
This message indicates that Zorp was unable to find the required proxy module. Check your installation, or contact your Zorp support for assistance.
This message reports that the given proxy-exported attribute was fetched, and it contained the also given value.
This message reports that the given proxy-exported attribute was changed to the given value.
This message indicates that the Satyr authentication client sent an invalid command. Check your Satyr package version, or contact your Zorp support for assistance.
This message indicates an internal error, please contact your Zorp support for assistance.
This message indicates that establishing a connection to the authentication agent failed for the given reason.
This message indicates that the SATYR authentication subsystem does not support the address family the client used to access the service to be authenticated. Please contact your Zorp support for assistance.
This message indicates that Zorp was unable to connect to the client Satyr authentication client. It is likely that the client does not run Satyr on the default port or something blocks the connection. Check your client configuration.
This message indicates that the SSL handshake with the authentication agent failed because of the given SSL error condition.
This message indicates that Satyr authentication failed, because non-IPv4 address was used. Please contact your Zorp support for assistance.
This message indicates that Satyr authentication failed, because Zorp was unable to send data to Satyr.
This message indicates that Satyr authentication failed, because Zorp was unable to read the client authentication answer.
This message indicates an internal error, please contact your Zorp support for assistance.
This message indicates an internal error, please contact your Zorp support for assistance.
This message indicates an internal error, please contact your Zorp support for assistance.
This message indicates an internal error, please contact your Zorp support for assistance.
This message reports that the SZIG framework was unable to create its socket and thus zorpctl won't be able to access and display internal Zorp information.
This message indicates that the url filter database can't be loaded. This could be because of a bad file format, version mismatch or an error in the generated database.
This message indicates that Zorp was unable to load the policy. It is likely that the policy has any kind of syntactical problem. Check the traceback in the log to find out where the problem occurs.
This message indicates that Zorp was unable to initialize the policy.
This message indicates that the loading of the initial policy failed, because of some policy problem. Check the log to find out where the problem occurs.
This message reports that Zorp caught a HUP signal and tries to reload its policy.
This message indicates that Zorp was unable to load the new policy, and reverts to the old one. Check the logs to find out where the error occurs in the new policy.
This message indicates that server unexpectedly closed its connection.
This message reports that the data-transfer to or from some endpoint is closed.
This message indicates that the data-transfer is interrupted by a timed progress callback and Zorp is closing the date-transfer channels.
This message say that zorp found an invalid character in finger request.
This message is about too long username found in the request.
This message is appear when a too long hostname found in the request horname chain.
This message appear when some error found in client side when writting the header.
This message appear when some error found in client side when writting the response.
This message appear when some error found in client side when writting the footer.
This message is about administrator decision to reject the finger session.
This message is about administrator decision to drop finger session.
This debug message is about proxy state when finger fetched request and asking policy about it
This debug message is about proxy state when finger start connect to server.
This debug message is about proxy state when finger start send the request to server.
This debug message is about proxy state when finger start to copy server answer to client.
This message reports that the data connection is accepted from the client.
This message reports that the data connection is accepted from the server.
This message reports that the data connection is established to the client.
This message indicates that the data connection is established to the client, but the no connection is expected or the connection is canceled meanwhile.
This message reports that the data connection is established to the server.
This message indicates that the data connection is established to the server, but the no connection is expected or the connection is canceled meanwhile.
This message indicates that the previous data connection was not completely teared down and a new one is about to accept. This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the previous data connection was not completely teared down while a new connection is being established. This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the previous data connection was not completely teared down and a new one is being established. This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the previous data connection was not completely teared down and a new one is about to accept. This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the data connection is going to be destroyed.
This message indicates an internal error that a previous data connection was not completed successfully. This condition should not occur, though the event is harmless, an explicit data reset clears this state. Please contact the Balasys QA team (devel@balasys.hu).
This message indicates an internal error that the proxy is unable to start a stacked data proxy because either the data connection to the FTP client or the FTP server is not yet established. Please contact the Balasys QA team (devel@balasys.hu).
This message indicates an internal error that the current command descriptor changed while the data connection was being set up, thus we are unable to know which direction is permitted during data transfer. Please contact the Balasys QA team (devel@balasys.hu).
This message reports that data connection is established between the client and the server, and proxy is being stacked for the data transfer.
This message indicates that the IP address of the data connection to be established differs from the IP of the control connection. This might be caused by a real bounce attack on FTP, or a erroneously configured NAT translation on the client or server side.
This message indicates that the IP address of the data connection to be established differs from the IP of the control connection. This might be caused by a real bounce attack on FTP, or a erroneously configured NAT translation on the client or server side.
This message indicates that the IP address of the data connection to be established differs from the IP of the control connection. This might be caused by a real bounce attack on FTP, or a erroneously configured NAT translation on the client or server side.
This message indicates that the IP address of the data connection to be established differs from the IP of the control connection. This might be caused by a real bounce attack on FTP, or a erroneously configured NAT translation on the client or server side.
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the configured max_line_length is above upper limit and Zorp sets it to the upper limit.
This message indicates that the configured max_username_length is above max_line_length which does not make sense and Zorp sets it to the max_line_length.
This message indicates that the configured max_password_length is above max_line_length which does not make sense and Zorp sets it to the max_line_length.
This message indicates that the configured max_hostname_length is above max_line_length which does not make sense and Zorp sets it to the max_line_length.
This message indicates that the character set specified in the valid_chars_username attribute has a syntax error.
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message reports that Zorp was unable to write out a full line and some data remained in the buffer.
This message indicates that the server's answer does not begin with a valid 3 character long number.
This message indicates that Zorp was unable to fetch the answer from the server. It is likely caused by some timeout.
This message indicates that too short answer is read from the server. A valid answer must be at least 4 character long.
This message indicates that the server's answer has invalid continuation mark.
This message indicates that the given response is rejected and changed by the policy.
This message indicates that Zorp was unable to read from the client side.
This message indicates that an empty command is received, and policy does not permit it.
This message indicates that an unknown command is received and policy does not permit it.
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the given request was not permitted in non-transparent mode before the sever connection was established. It is likely caused by an AUTH command.
This message reports that the given request is answered by Zorp without sending the request to the server.
This message indicates that the given request is rejected and the connection is aborted by Zorp.
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
* This message reports that the server send an answer * which have too many lines. Increase the self.max_continuous_line variable * if this is not a security incident.
This message reports that Zorp is reading from it's peers on the given side.
This message indicates that the port part of the username in non-transparent mode is not permitted by the policy and Zorp rejects the request. Check the 'target_port_range' attribute.
This message indicates that the username sent by the client contains invalid characters and Zorp rejects the request. Check the 'valid_chars_username' attribute.
This message indicates that the hostname part of the username in non-transparent mode is too long and Zorp rejects the request. Check the 'max_hostname_length' attribute.
This message indicates that the username is too long and Zorp rejects the request. Check the 'max_username_length' attribute.
This message indicates that the username is too long and Zorp rejects the request. Check the 'max_username_length' attribute.
This message indicates that the username sent by the client contains invalid characters and Zorp rejects the request. Check the 'valid_chars_username' attribute.
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the password is too long and Zorp rejects the request. Check the 'max_password_length' attribute.
This message indicates that the password is too long and Zorp rejects the request. Check the 'max_password_length' attribute.
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the data transfer command's answer sent by the server is invalid and Zorp resets the data transfer.
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the parameter of the request is invalid and Zorp rejects the request. This request must not have any parameter at all.
This message indicates that the parameter of the request is invalid and Zorp rejects the request. This request must not have any parameter at all.
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the required parameter for the TYPE command is missing and Zorp rejects the request.
This message indicates that the requested transfer type specification is normally valid but currently unsupported by the proxy and Zorp rejects the request.
This message indicates that the requested transfer type specification is invalid and Zorp rejects the request.
This message indicates that the required parameter for the MODE command is missing and Zorp rejects the request.
This message indicates that the MODE command parameter is invalid and Zorp rejects the request.
This message indicates that the required parameter for the STRU command is missing and Zorp rejects the request.
This message indicates that the STRU command parameter is invalid and Zorp rejects the request.
This message indicates that Zorp was unable to start listening for the data connection on the server side and Zorp rejects the request.
This message indicates that Zorp was unable to start listening for the data connection on the server side and Zorp rejects the request.
This message indicates that the response to the PASV command is invalid and Zorp rejects the response.
This message indicates that the proxy was unable to connect to the server on the port specified in its PASV response and Zorp rejects the response.
This message indicates that Zorp was unable to start listening for the data connection on the server side and Zorp rejects the request.
This message indicates that Zorp was unable to start listening for the data connection on the server side and Zorp rejects the request.
This message indicates that the required parameter for the EPSV command is missing and Zorp rejects the response.
This message indicates that the parameter of the EPSV response does not begin with a bracket and Zorp rejcets the response.
This message indicates that the parameter of the EPSV response does not have a closing bracket and Zorp rejects the response.
This message indicates that the EPSV command response is invalid and Zorp rejects the response.
This message indicates that the port number of the EPSV command response is invalid and Zorp rejects the response.
This message indicates that Proxy cannot detect the server address. This an internal error.
This message indicates that the protocol specified by the EPSV command response is not supported by the proxy and Zorp rejects the response.
This message indicates that the proxy was unable to connect to the server on the port specified in its EPSV response and Zorp rejects the response.
This message indicates that the parameter of the PORT command is invalid and Zorp rejects the request.
This message indicates that the 'data_mode' attribute of the policy is invalid and Zorp rejects the request. Check the 'data_mode' attribute.
This message indicates that the proxy was unable to connect to the client on the port specified in its PORT response and Zorp rejects the response.
This message indicates that the response of the PASV command is invalid and Zorp rejects the response.
This message indicates that the proxy was unable to connect to the client on the port specified in its PORT response and Zorp rejects the response.
This message indicates that the response of the PORT command is invalid and Zorp rejects the response.
This message indicates that the 'data_mode' attribute of the policy is invalid and Zorp rejects the request. Check the 'data_mode' attribute.
This message indicates that Zorp was unable to start listening for the data connection on the client side and Zorp rejects the request.
This message indicates that Zorp was unable to start listening for the data connection on the client side and Zorp rejects the request.
This message indicates that Zorp was unable to start listening for the data connection on the client side and Zorp rejects the request.
This message indicates that Zorp was unable to start listening for the data connection on the client side and Zorp rejects the request.
This message indicates that the response of the PORT command is invalid and Zorp rejects the response.
This message indicates that the required parameter for the EPRT command is missing and Zorp rejects the request.
This message indicates that the parameter of the EPRT command is invalid and Zorp rejects the request.
This message indicates that the port number of the EPRT command is invalid and Zorp rejects the request.
This message indicates that the protocol specified by the EPRT command is not supported by the proxy and Zorp rejects the response.
This message indicates that the host address of the EPRT command is invalid and Zorp rejects the request.
This message indicates that the 'data_mode' attribute of the policy is invalid and Zorp rejects the request. Check the 'data_mode' attribute.
This message indicates that the proxy was unable to connect to the client specified in the EPRT response and Zorp rejects the response.
This message indicates that the response of the EPRT is invalid and Zorp rejects the response.
This message indicates that the proxy was unable to connect to the client specified in the EPRT response and Zorp rejects the response.
This message indicates that the 'data_mode' attribute of the policy is invalid and Zorp rejects the request. Check the 'data_mode' attribute.
This message indicates that Zorp was unable to start listening for the data connection on the client side and Zorp rejects the response.
This message indicates that Zorp was unable to start listening for the data connection on the client side and Zorp rejects the response.
This message indicates that Zorp was unable to start listening for the data connection on the client side and Zorp rejects the response.
This message indicates that Zorp was unable to start listening for the data connection on the client side and Zorp rejects the response.
This message indicates that the response of the EPSV command is invalid and Zorp rejects the response.
This message indicates that the parameter of the ALLO command is invalid and Zorp rejects the request.
This message indicates that the request_stack or response_stack hash contains an invalid stacking tuple. It should contain a (stack_type, proxy_class) tuple. Check your Zorp configuration.
This message indicates that the request_stack or response_stack hash contains an invalid stacking type. Check your Zorp configuration.
This message indicates that the processed request was invalid, and the data transfer failed.
This message indicates that the stacked proxy returned the specified verdict about the content. Check the stacked proxy log for further information.
This message indicates that the stacked proxy accepted the content.
This message indicates that the policy does not contain any setting for the given request and Zorp rejects the request. Check the 'request' attribute.
This message indicates that the policy type is invalid for the given request and Zorp rejects the request. Check the 'request' attribute.
This message indicates that the policy for the given request is invalid and Zorp rejects the request. Check the 'request' attribute. It is likely that the parameter for the FTP_REQ_POLICY is invalid.
This message indicates that the callback for the given request policy is invalid and Zorp rejects the request. Check the 'request' attribute. It is likely that the parameter for the FTP_REQ_POLICY is invalid.
This message indicates that the returned value of the callback for the given request policy is invalid and Zorp rejects the request. Check the callback function.
This message indicates that the policy does not contain any setting for the given response and Zorp rejects the response. Check the 'response' attribute.
This message indicates that the policy type is invalid for the given response and Zorp rejects the request. Check the 'request' attribute.
This message indicates that the policy for the given response is invalid and Zorp rejects the response. Check the 'response' attribute. It is likely that the parameter for the FTP_RSP_POLICY is invalid.
This message indicates that the callback for the given response policy is invalid and Zorp rejects the response. Check the 'response' attribute. It is likely that the parameter for the FTP_RSP_POLICY is invalid.
This message indicates that the returned value of the callback for the given response policy is invalid and Zorp rejects the response. Check the callback function.
This message indicates that the policy does not contain any setting for the given feature and Zorp drops the feature. Check the 'features' attribute.
This message indicates that the policy type is invalid for the given feature and thus Zorp drops the feature.
This message indicates that Zorp caught an invalid error code internally. Please report this event to the BalaSys Development Team (at devel@balasys.hu).
This message reports that Zorp is sending the given error page to the clients browser. It is likely that some protocol/configuration/proxy error occurred.
This message reports that Zorp was about to write to an invalid stream. Please report this event to the BalaSys Development Team (at devel@balasys.hu).
This message reports that Zorp was unable to write to the given stream. It is likely that the peer closed the connection unexpectedly.
This message indicates that the client tried to use the given unsupported HTTP authentication. Currently only Basic HTTP authentication is supported by Zorp.
This message indicates that the client sent a malformed username:password field, during the authentication phase.
This message indicates that the username:password field received during authentication was malformed.
This message indicates that the client sent an invalid HTTP request to the proxy.
This message indicates that the client sent a CONNECT method request, but it is only supported for HTTP/1.0 or later.
This message indicates that the client sent the given type request, which is not permitted by the policy. Check the permit_proxy_requests and the permit_server_requests attributes.
This message indicates that no Host header was sent by the client. As the content of the host header is used to reconstruct the requested URL, the request_url attribute will refer to a host named 'unknown'.
This message indicates that an HTTP/0.9 request was sent by the client, and Host header is required by the policy, but HTTP/0.9 does not support headers. Check the require_host_header attribute.
This message indicates that no Host header was sent by the client, but it was required by the policy. Check the require_host_header attribute.
This message indicates that there was an error parsing an already canonicalized URL. Please report this event to the BalaSys Development Team (at devel@balasys.hu)
This message indicates that there was an error parsing an already canonicalized URL. Please report this event to the BalaSys Development Team (at devel@balasys.hu)
This message indicates that a client tried to use FTP over HTTP which is not allowed by default. Either set a parent proxy or enable the permit_ftp_over_http attribute.
This message indicates that the requested URL refers to an unsupported protocol scheme. Zorp currently knows about http and cache_object protocols, and can support the ftp protocol if a parent_proxy supporting ftp over http tunneling is present.
This message indicates that the HTTP request was rejected because the hostname part in the URL was too long. You can increase the permitted limit by changing the max_hostname_length attribute.
This message indicates that the request hash contains an invalid item for the given request method. Check your Zorp configuration.
This message indicates that the request hash contains an invalid POLICY tuple for the given request method. It should contain a valid call-back function in the tuple.
This message indicates that the request hash contains an invalid REJECT tuple for the given request method. It should contain an error message, which is sent back to the client.
This message indicates that the request hash contains an invalid action for the given request method. Check your Zorp configuration.
This log message indicates that the policy requested a custom response to be sent to the client.
This log message indicates that the specified HTTP request was not permitted by your policy.
This log message indicates that the specified HTTP request was not permitted by your policy.
This message indicates that the proxy did not allow addressing the specified port as the target_port_range attribute does not allow it.
This message indicates that initializing the server stream failed. Please report this event to the BalaSys Development Team (at devel@balasys.hu).
This message indicates that Zorp was unable to enable HTTP/0.9 compatibility mode, due to the full buffer. If you experience this problem many times, please contact your Zorp support.
This message indicates that the server sent back HTTP/0.9 response, which is prohibited by the policy. It is likely a buggy or old server. Check the permit_http09_responses attribute.
This message indicates the the HTTP status line returned by the server was invalid.
This message indicates that the server sent the response with an invalid HTTP version. It is likely that the server is buggy.
This message indicates that the server sent an unsupported protocol version. It is likely that the server is buggy.
This message indicates that the response hash contains an invalid item for the given response. Check your Zorp configuration.
This message indicates that the response hash contains an invalid POLICY tuple for the given response. It should contain a valid call-back function in the tuple.
This message indicates that the response hash contains an invalid REJECT tuple for the given response. It should contain an error message, which is sent back to the client.
This message indicates that the response hash contains an invalid action for the given response. Check your Zorp configuration.
This message indicates that the status code returned by the server is not a permitted response code for this request.
This message indicates that the received CONNECT request did not include a port number to connect to.
This message indicates that the our parent proxy refused our CONNECT request. It is likely that the parent proxy does not permit CONNECT method.
This message reports that CONNECT method is in use, and CONNECT method was accepted by out parent proxy.
This message indicates that an internal error occurred, the connectMethod function did not return an integer. Please report this event to the BalaSys Development Team (at devel@balasys.hu).
This message reports that Zorp is fetching the request and the headers from the client.
This message reports that Zorp is processing the fetched request and the headers.
This message reports that the maximum number of requests in a keep-alive loop is reached, and Zorp is closing after this request. Check the max_keepalive_request attribute.
This message reports that Zorp is filtering the processed request and the headers.
This message indicates that Zorp is recechecking the HTTP request after possible changes performed by the policy layer.
This message reports that Zorp is sending the filtered request and headers, and copies the requests data to the server.
This message reports that Zorp is fetching the response and headers from the server.
This message reports that Zorp is processing the fetched response and the headers.
This message reports that Zorp is filtering the processed response and the headers.
This message reports that Zorp is sending the filtered response and headers, and copies the response data to the client.
This message indicates an internal error in HTTP proxy. Please report this event to the BalaSys Development Team (at devel@balasys.hu).
This message reports that Zorp is exiting the keep-alive loop and closing the connection.
This message indicates that the chunk length line is too long. It is likely caused by a buggy client or server.
This message indicates that the chunk length is invalid. It is likely caused by a buggy client or server.
This message indicates that the chunk length is invalid. It is likely caused by a buggy client or server.
This message indicates that the length of the chunk is larger than allowed or is a negative number. Check the 'max_chunk_length' attribute.
This message indicates that Zorp unexpectedly got EOF during chunk encoded data transfer. It is likely a caused by a buggy client or server.
This message indicates that the chunk footer contains data. It is likely caused by a buggy client or server.
This message reports that the stacked proxy sent a content-length hint on how much data will be sent and the http proxy is using it to set the Content-Length header.
This message indicates that the request_stack or response_stack hash contains an invalid stacking tuple. It should contain a (stack_type, proxy_class) tuple. Check your Zorp configuration.
This message indicates that the request_stack or response_stack hash contains an invalid stacking type. Check your Zorp configuration.
This message indicates that the Content-Length headers value is not a valid number. It is likely caused by a buggy client or server.
This message indicates that the processed request was invalid, and the data transfer failed.
This message indicates that the stacked proxy returned the specified verdict about the content. Check the stacked proxy log for further information.
This message reports that the stacked proxy sent an error hint on how the parent proxy should present the reject verdict towards the client.
This message reports that the stacked proxy sent an error info string on how the parent proxy should present the reject verdict reason towards the client.
This message reports that the stacked proxy has not sent an indication on how the parent proxy should present the reject verdict reason towards the client.
This message indicates that the stacked proxy accepted the content.
This message indicates that the response given by the FTP server was too short, not even the mandatory status code was included.
This message indicates that the FTP server gave an invalid response, the status code returned by the server was not numeric.
This message indicates that the FTP server gave an invalid response as the status code changed from the one which was present on the first line.
This message indicates that the FTP server returned an unknown status code in response to our login request.
This message indicates that the FTP server greeted Zorp with a non-220 response code.
This message indicates that the directory specified in the URL was not accepted by the FTP server.
This message indicates that the directory specified in the URL was not accepted by the FTP server.
This message indicates that the directory specified in the URL was not accepted by the FTP server.
This message indicates that an I/O error occurred while sending our RETR or LIST request.
This message indicates that an I/O error occurred while trying to establish the data connection with the FTP server.
This message indicates that the FTP server did not react with a 150 response after the data connection was established.
This message indicates that the FTP server did not return with an appropriate status code at the end of the data transfer.
This message indicates that the HDR_CHANGE_NAME parameter is invalid, for the given header. Check your request_headers and response_headers hashes.
This message indicates that the HDR_CHANGE_VALUE parameter is invalid, for the given header. Check your request_headers and response_headers hashes.
This message indicates that the HDR_CHANGE_BOTH parameter is invalid, for the given header. Check your request_headers and response_headers hashes.
This message indicates that the action is invalid, for the given header. Check your request_headers and response_headers hashes.
This message indicates that Zorp was unable to fetch headers from the server. Check the permit_null_response attribute.
This message indicates that Zorp fetched an invalid header from the server. It is likely caused by a buggy server.
This message indicates that the server tried to send more header lines, than the allowed maximum. Check the max_header_lines attribute.
This message indicates that the request method sent by the client is invalid.
This message indicates that the URL sent by the client is invalid.
This message indicates that the protocol version sent by the client is invalid.
This message indicates that the server sent an invalid response status line.
This message indicates that the protocol version sent by the server is invalid.
This message indicates that the response code sent by the server is invalid.
This message indicates that the protocol version sent by the client is unsupported.
This message indicates that the protocol version sent by the server is unsupported.
This message is logged when the policy layer returned a non-integer value in its packetStats() function. packetStats() is expected to return ZV_REJECT or ZV_ACCEPT.
This message indicates that the verdict returned by the packetStats() function requests to terminate the session.
This message indicates that the response line is too long and Zorp aborts the connection. Check the 'max_reply_length' attribute.
This message indicates that the status of the response is invalid and Zorp rejects the response. The response should begin with '+OK' or with '-ERR'.
This message reports that the fetched response contains a parameter.
This message indicates that the multi-line data transfer failed and Zorp rejects the response.
This message indicates that the request line is too long and Zorp rejects the request. Check the 'max_request_length' attribute.
This message reports that the fetched request contains a parameter.
This message indicates that the request was unknown and Zorp aborts the connection. Check the 'permit_unknown_command' and the 'request' attributes.
This message indicates that the request command is not allowed in this state of the protocol and Zorp rejects the request.
This message indicates that the request must not have any parameter and Zorp is going to drop the parameter.
This message indicates that the numerical parameter of the request is missing and Zorp aborts the connection.
This message indicates that the numerical parameter of the request is not in the given range and Zorp aborts the connection.
This message indicates that the numerical parameter of the request is a negative number which is invalid and Zorp aborts the connection.
This message indicates that the numerical parameter of the request is zero which is invalid and Zorp aborts the connection.
This message indicates that the numerical parameter of the request contains junk characters after the number but Zorp ignores and truncates the junk.
This message indicates that the first numerical parameter is not in the given range and Zorp aborts the connection.
This message indicates that the first numerical parameter of the request is a negative number which is invalid and Zorp aborts the connection.
This message indicates that only one numerical parameter is present but two is required and Zorp rejects the request.
This message indicates that the second numerical parameter is not in the given range and Zorp aborts the connection.
This message indicates that the second numerical parameter of the request is a negative number which is invalid and Zorp aborts the connection.
This message indicates that the numerical parameters of the request contain junk characters after the numbers but Zorp ignores and truncates the junk.
This message indicates that the username parameter of the request is too long and Zorp rejects the request. Check the 'max_username_length' attribute.
This message indicates that the password parameter of the request is too long and Zorp rejects the request. Check the 'max_password_length' attribute.
This message indicates that the username parameter is too long or the digest missing after the username and Zorp rejects the request.
This message indicates that the MD5 digest parameter of the request is invalid and Zorp rejects the request.
This message indicates that the numerical parameter of the response is missing and Zorp aborts the connection.
This message indicates that the numerical parameter of the response is not in the given range and Zorp aborts the connection.
This message indicates that the numerical parameter of the response is a negative number which is invalid and Zorp aborts the connection.
This message indicates that the numerical parameter of the response contains junk characters after the number but Zorp ignores and truncates the junk.
This message indicates that the numerical parameter of the response is not in the given range and Zorp aborts the connection.
This message indicates that the numerical parameter of the response is missing and Zorp aborts the connection.
This message indicates that the numerical parameter of the response is a negative number which is invalid and Zorp aborts the connection.
This message indicates that the second numerical parameter of the response is not in the given range and Zorp aborts the connection.
This message indicates that the second numerical parameter of the response is missing and Zorp aborts the connection.
This message indicates that the second numerical parameter of the response is a negative number which is invalid and Zorp aborts the connection.
This message indicates that the second numerical parameter of the response contains junk characters after the number but Zorp ignores and truncates the junk.
This message indicates that the stacked proxy rejected the content and Zorp rejects the response.
This message indicates that the policy does not contain any setting for the given request and Zorp rejects the request. Check the 'request' attribute.
This message indicates that the policy type is invalid for the given request and Zorp aborts the connection. Check the 'request' attribute.
This message indicates that the policy for the given request is invalid and Zorp aborts the connection. Check the 'request' attribute. It is likely that the parameter for the POP3_REQ_POLICY is invalid.
This message indicates that the callback for the given request policy is invalid and Zorp aborts the connection. Check the 'request' attribute. It is likely that the parameter for the POP3_REQ_POLICY is invalid.
This message indicates that the returned value of the callback for the given request policy is invalid and Zorp aborts the connection. Check the callback function.
This message indicates that the policy does not contain any setting for the given response and Zorp rejects the response. Check the 'request' attribute.
This message indicates that the policy type is invalid for the given response and Zorp aborts the connection. Check the 'request' attribute.
This message indicates that the policy for the given request/response is invalid and Zorp aborts the connection. Check the 'request' attribute. It is likely that the parameter for the POP3_REQ_POLICY is invalid.
This message indicates that the callback for the given request policy is invalid and Zorp aborts the connection. Check the 'request' attribute. It is likely that the parameter for the POP3_REQ_POLICY is invalid.
This message indicates that the returned value of the callback for the given response policy is invalid and Zorp aborts the connection. Check the callback function.
This message indicates that the stack policy type is invalid for the given response, so nothing will be stacked. Check the 'response_stack' attribute.
This message indicates that the stack policy for the given response is invalid and Zorp stacks nothing. Check the 'response_stack' attribute. It is likely that the parameter for the POP3_STK_MIME or POP3_STK_DATA is invalid.
This message indicates that the stack policy for the given response is invalid and Zorp stacks nothing. Check the 'response_stack' attribute. It is likely that the parameter for the POP3_STK_POLICY is invalid.
This message indicates that the callback for the given request policy is invalid and Zorp stacks nothing. Check the 'request' attribute. It is likely that the parameter for the POP3_STK_POLICY is invalid.
This message indicates that the returned value of the callback for the given response policy is invalid and Zorp stacks nothing. Check the callback function.
This message indicates that the request command verb is invalid and Zorp rejects the request.
This message indicates that the request line is too long and Zorp rejects the request. Check the 'max_request_length' attribute.
This message indicates that the given command is not permitted in this state of the communication and Zorp rejects the request.
This message indicates that the given request is unknown and Zorp rejects it. Check the 'permit_unknown_command' and the 'request' attributes.
This message reports that the request is going to be copied to the server.
This message indicates that an error occurred during sending the request to the server.
This message reports that the authentication request is going to be fetched.
This message indicates that the authentication request line is too long and Zorp rejects the request. Check the 'max_auth_request_length' attribute.
This message reports that the authentication request is going to be copied to the server.
This message indicates that an error occurred during sending the authentication request to the server.
This message indicates that the response contains non-numeric characters and Zorp rejects the response.
This message indicates that the continuation character of the response contains an invalid character and Zorp rejects the response. The response must contain ' ' or '-' after the response code.
This message indicates that the response line is too long and Zorp rejects the response. Check the 'max_response_length' attribute.
This message indicates that the reply code has changed in the continuation lines and Zorp rejects the response.
This message reports that the response is going to be copied to the client.
This message indicates that an error occurred during sending the response to the client.
This message indicates that the response code 250 for the NOOP request is required and Zorp ignores the invalid policy while generating NOOPs to the server.
This message indicates that the response code 354 for the DATA request is required and Zorp ignores the invalid policy during data transfer to the server.
This message indicates that the content was declared invalid by the stacked proxy and Zorp rejects it.
This message inidicates that an error occurred during stacked proxy handle the contents and Zorp send back a temporary error message.
This message indicates that an empty message is received from the stacked proxy and Zorp rejects it.
This message indicates that Zorp was unable to send RSET command to the server.
This message reports that Zorp is exiting from the SMTP proxy loop and closing connections on both side.
This message indicates that parsing the local part of the address failed.
This message indicates that the local part of the mail is invalid because it does not end with a '@' sign.
This message indicates that the domain name of the mail is invalid.
This message indicates that the address path is invalid because it does not start with a '>;' sign.
This message indicates that the source-root information of the address patch is invalid.
This message indicates that the address information is invalid.
This message indicates that the address path is invalid because it does not start with a '<;' sign but ends with it.
This message indicates that the address path is invalid because it does not end with a '<;' sign.
This message indicates that the SIZE extension of the MAIL command is invalid because it must contain non-numeric characters. Zorp rejects the request.
This message indicates that the BODY extension of the MAIL command is invalid because it must contain either '7BIT' or '8BITMIME'. Zorp rejects the request.
This message indicates that the AUTH extension of the MAIL command is invalid because it must be xtext. Zorp rejects the request.
This message indicates that the given extension is invalid with the MAIL command and Zorp rejects the request.
This message indicates that the policy type is invalid for the given request and Zorp aborts the connection. Check the 'request' attribute.
This message indicates that the parameter of the request policy of the given request is invalid and Zorp aborts the connection. Check the 'request' attribute.
This message indicates that the parameter of the request policy of the given request is invalid and Zorp aborts the connection. Check the 'request' attribute.
This message indicates that the returned value of the callback for the given request policy is invalid and Zorp aborts the connection. Check the callback function.
This message indicates that the policy type is invalid for the given response and Zorp aborts the connection. Check the 'response' attribute.
This message indicates that the parameter of the response policy of the given request is invalid and Zorp aborts the connection. Check the 'response' attribute.
This message indicates that the parameter of the response policy of the given request is invalid and Zorp aborts the connection. Check the 'response' attribute.
This message indicates that the returned value of the callback for the given response policy is invalid and Zorp aborts the connection. Check the callback function.
This message indicates that the Telnet protocol contained a sequence of protocol elements that would have needed an unreasonably large buffer to process. These structures are not commonly found in normal Telnet streams but could be used to mount a denial of service attack on a Telnet client or server by a malicious host.
This message appears, when Zorp canno find a literal in message rebuilding.
This message appear when reading continuation answer from message but Zorp cannot found a request that need continuation message. this probable means unknown capabilities or syncronization problem between server and proxy.
Placeholder imap.c.21
This message means that literal length contains non number characters
This message appears literal length attribute is not complete. The close parenthesis is not found
This message indicates that the stacked proxy rejected the content and Zorp rejects the response.
This message indicates that the policy type is invalid for the given request and Zorp aborts the connection. Check the 'request' attribute.
This message indicates that the stack policy for the given response is invalid and Zorp stacks nothing. Check the 'response_stack' attribute. It is likely that the parameter for the POP3_STK_MIME or POP3_STK_DATA is invalid.
This message indicates that the stack policy for the given response is invalid and Zorp stacks nothing. Check the 'response_stack' attribute. It is likely that the parameter for the POP3_STK_POLICY is invalid.
This message indicates that the callback for the given request policy is invalid and Zorp stacks nothing. Check the 'request' attribute. It is likely that the parameter for the POP3_STK_POLICY is invalid.
This message indicates that the returned value of the callback for the given response policy is invalid and Zorp stacks nothing. Check the callback function.
Too many SearchResultEntry message arrived for the corresponding request, and the required action is LDAP_RSP_DROP
Too many SearchResultEntry message arrived for the corresponding request, and the required action is LDAP_RSP_ABORT
response_overrun_action may contain other values than LDAP_RSP_DROP and LDAP_RSP_ABORT, in this case the assumed value is LDAP_RSP_DROP
This message attempt when zorp cannot call the given policy function.
This message attempt when zorp cannot found what to do with a command.
This message attempt when zorp cannot found what to do with a command answer.
This message atempt when zorp cannot parse policy return value.
This message attempt when zorp cannot found what to do with a command.
This message attempt when zorp cannot call the given policy function.
This mesage attempt when called policy function return with wrong value.
This message indicates that the stacked proxy rejected the content and Zorp rejects the response.
This message indicates that the stack policy type is invalid for the given response, so nothing will be stacked. Check the 'response_stack' attribute.
This message indicates that the stack policy for the given response is invalid and Zorp stacks nothing. Check the 'response_stack' attribute. It is likely that the parameter for the NNTP_STK_POLICY is invalid.
This message indicates that the callback for the given request policy is invalid and Zorp stacks nothing. Check the 'request' attribute. It is likely that the parameter for the NNTP_STK_POLICY is invalid.
This message indicates that the returned value of the callback for the given response policy is invalid and Zorp stacks nothing. Check the callback function.
This message indicates that the client_channel_stack or the server_channel_stack hash contains an invalid stacking type. Check your Zorp configuration.
This message indicates that the client_channel_stack or the server_channel_stack hash contains an invalid stacking tuple. It should contain a (stack_type, proxy_class) tuple. Check your Zorp configuration.
This message reports that a REQUIRED type Basic ACL rule is evaluated with the given result.
This message reports that every Basic ACL rule were evaluated with the given final result.
This message indicates that the cache size(threshold) is reached, and cache is shifted. @see: Cache.ShiftCache
This message indicates that the connection to the server succeeded.
This message indicates that the connection to the server can not be established, because no server address is set.
This message reports that the remote end is down and the down state of the remote end is stored, so connection is wont be tried to it within the timeout latter.
This message reports that the remote end is down, but the down state is not stored of the remote end, so connection will be tried to it next time.
This message reports that the remote end is down and the down state is stored of the remote end, so connection wont be tried within the timeout latter.
This message indicates that side stacking failed, because a socketPair creation is failed. It is likely that there is now resource available. Try increase fd limits.
This message indicates that the KZorp result lookup has failed for this session.
This message indicates that no applicable service was found for this client zone in the services cache. It is likely that there is no applicable service configured in this ZoneDispatcher at all. Check your ZoneDispatcher service configuration. @see: Dispatcher.ZoneDispatcher
This message indicates that no applicable service was found for this client zone. Check your ZoneDispatcher service configuration. @see: Dispatcher.ZoneDispatcher
This message indicates that no applicable service was found for this client zone in the services cache. It is likely that there is no applicable service configured in this CSZoneDispatcher at all. Check your CSZoneDispatcher service configuration. @see: Dispatcher.CSZoneDispatcher
This message indicates that no applicable service was found for this client zone. Check your CSZoneDispatcher service configuration. @see: Dispatcher.CSZoneDispatcher
This message reports that a matching regexp pattern was found for the given string.
This message indicates that the file containing the match regexps cannot be opened. It is likely that the file does not exists or it is not permitted to read. @see: Matcher.RegexpFileMatcher
This message indicates that the file containing the ignore regexps cannot be opened. It is likely that the file does not exists or it is not permitted to read. @see: Matcher.RegexpFileMatcher
This message reports that the recipient address has been already checked and the cached information is used.
This message reports that the recipient address has not been already checked and it is going to be checked now directly.
This message indicates that the sender address was rejected during the recipient address verify check and the recipient address is rejected.
This message reports that the recipient address verify was successful and it is accepted.
This message reports that the recipient address verify was unsuccessful and it is rejected.
This message indicates that an SMTP error occurred during the recipient address verify and it is rejected.
This message reports that the NAT type and the old address before the NAT mapping occurs.
This message reports that the NAT type and the new address after the NAT mapping occurred.
This message indicates that an error occurred during child proxy stacking. The stacking failed and the subsession is destroyed.
This message reports that a new proxy is about to be stacked under the current proxy, as a child proxy.
This message reports that the user authentication was successful.
This message indicates that a service trying to enter to the given zone was denied by the policy. Check that the destination zone is included in the target zone list of the service.
This message indicates that the given hostname could not be resolved. It could happen if the hostname is invalid or nonexistent, or it if your resolve setting are not well configured. Check your "/etc/resolv.conf"
This message indicates that the initialization function of the given instance was not found in the policy file.
This message indicates that downloading the necessary information to the kernel-level KZorp subsystem has failed.
This message reports that the given instance is stopping.
This message reports that the given instance is freeing its external resources (for example its kernel-level policy objects).
This message indicates that flushing the instance-related information in the kernel-level KZorp subsystem has failed.
This message indicates that the remote port is bellow 1024 and due to the violation the connection is closed.
This message indicates that the remote port is bellow 1024 and due to the violation the connection is closed.
This message indicates that the server's remote port is not control_port-1 or 20 and due to the violation the connection is closed.
This message indicates an internal error, please contact the Balasys QA team (devel@balasys.hu).
This message indicates that the request was blocked by the URIFilter.
This message indicates that the sender address was administratively prohibited and the request is rejected. Check the 'sender_matcher' attribute.
This message reports that the sender address check was successful and the request is accepted.
This message indicates that the email address local-part contains a percent sign and it is not permitted by the policy and the request is rejected. Check the 'permit_percent_hack' attribute.
This message indicates that the email address local-part contains a exclamation mark and it is not permitted by the policy and the request is rejected. Check the 'permit_exclamation_mark' attribute.
This message indicates that relaying the given address is not permitted by the policy and the request is rejected. Check the 'relay_check' attribute.
This message reports that the relay check was successful and the request is accepted.
This message indicates that the given recipient address is administratively prohibited and request is rejected. Check the 'recipient_matcher' attribute.
This message reports that the recipient check was successful and the request is accepted.
This message reports that the zone of the client is being checked.
This message reports that the domain name of the email is being checked.
This message is logged when Zorp caught a fatal signal. Possible reason is bad RAM or other hardware.
This message indicates that Zorp found no or invalid license file. Check your license file at "/etc/zorp/license.txt".
This message serves informational purposes, and indicates that the given module was successfully loaded from the given shared object.
This message is logged when ZMS caught a fatal signal. Possible reason is bad RAM or other hardware.
This message serves informational purposes, and indicates that the given module was successfully loaded from the given shared object.
This message indicates that the module directory does not exist.
This message serves informational purposes, and indicates that the given module was successfully loaded from the given shared object.
This message indicates that the module directory does not exist.
THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED. BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS LICENSE MAY BE CONSIDERED TO BE A CONTRACT, THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
Definitions
"Adaptation" means a work based upon the Work, or upon the Work and other pre-existing works, such as a translation, adaptation, derivative work, arrangement of music or other alterations of a literary or artistic work, or phonogram or performance and includes cinematographic adaptations or any other form in which the Work may be recast, transformed, or adapted including in any form recognizably derived from the original, except that a work that constitutes a Collection will not be considered an Adaptation for the purpose of this License. For the avoidance of doubt, where the Work is a musical work, performance or phonogram, the synchronization of the Work in timed-relation with a moving image ("synching") will be considered an Adaptation for the purpose of this License.
"Collection" means a collection of literary or artistic works, such as encyclopedias and anthologies, or performances, phonograms or broadcasts, or other works or subject matter other than works listed in Section 1(f) below, which, by reason of the selection and arrangement of their contents, constitute intellectual creations, in which the Work is included in its entirety in unmodified form along with one or more other contributions, each constituting separate and independent works in themselves, which together are assembled into a collective whole. A work that constitutes a Collection will not be considered an Adaptation (as defined above) for the purposes of this License.
"Distribute" means to make available to the public the original and copies of the Work through sale or other transfer of ownership.
"Licensor" means the individual, individuals, entity or entities that offer(s) the Work under the terms of this License.
"Original Author" means, in the case of a literary or artistic work, the individual, individuals, entity or entities who created the Work or if no individual or entity can be identified, the publisher; and in addition (i) in the case of a performance the actors, singers, musicians, dancers, and other persons who act, sing, deliver, declaim, play in, interpret or otherwise perform literary or artistic works or expressions of folklore; (ii) in the case of a phonogram the producer being the person or legal entity who first fixes the sounds of a performance or other sounds; and, (iii) in the case of broadcasts, the organization that transmits the broadcast.
"Work" means the literary and/or artistic work offered under the terms of this License including without limitation any production in the literary, scientific and artistic domain, whatever may be the mode or form of its expression including digital form, such as a book, pamphlet and other writing; a lecture, address, sermon or other work of the same nature; a dramatic or dramatico-musical work; a choreographic work or entertainment in dumb show; a musical composition with or without words; a cinematographic work to which are assimilated works expressed by a process analogous to cinematography; a work of drawing, painting, architecture, sculpture, engraving or lithography; a photographic work to which are assimilated works expressed by a process analogous to photography; a work of applied art; an illustration, map, plan, sketch or three-dimensional work relative to geography, topography, architecture or science; a performance; a broadcast; a phonogram; a compilation of data to the extent it is protected as a copyrightable work; or a work performed by a variety or circus performer to the extent it is not otherwise considered a literary or artistic work.
"You" means an individual or entity exercising rights under this License who has not previously violated the terms of this License with respect to the Work, or who has received express permission from the Licensor to exercise rights under this License despite a previous violation.
"Publicly Perform" means to perform public recitations of the Work and to communicate to the public those public recitations, by any means or process, including by wire or wireless means or public digital performances; to make available to the public Works in such a way that members of the public may access these Works from a place and at a place individually chosen by them; to perform the Work to the public by any means or process and the communication to the public of the performances of the Work, including by public digital performance; to broadcast and rebroadcast the Work by any means including signs, sounds or images.
"Reproduce" means to make copies of the Work by any means including without limitation by sound or visual recordings and the right of fixation and reproducing fixations of the Work, including storage of a protected performance or phonogram in digital form or other electronic medium.
Fair Dealing Rights. Nothing in this License is intended to reduce, limit, or restrict any uses free from copyright or rights arising from limitations or exceptions that are provided for in connection with the copyright protection under copyright law or other applicable laws.
License Grant. Subject to the terms and conditions of this License, Licensor hereby grants You a worldwide, royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in the Work as stated below:
to Reproduce the Work, to incorporate the Work into one or more Collections, and to Reproduce the Work as incorporated in the Collections; and,
to Distribute and Publicly Perform the Work including as incorporated in Collections.
The above rights may be exercised in all media and formats whether now known or hereafter devised. The above rights include the right to make such modifications as are technically necessary to exercise the rights in other media and formats, but otherwise you have no rights to make Adaptations. Subject to 8(f), all rights not expressly granted by Licensor are hereby reserved, including but not limited to the rights set forth in Section 4(d).
Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:
You may Distribute or Publicly Perform the Work only under the terms of this License. You must include a copy of, or the Uniform Resource Identifier (URI) for, this License with every copy of the Work You Distribute or Publicly Perform. You may not offer or impose any terms on the Work that restrict the terms of this License or the ability of the recipient of the Work to exercise the rights granted to that recipient under the terms of the License. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties with every copy of the Work You Distribute or Publicly Perform. When You Distribute or Publicly Perform the Work, You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License. This Section 4(a) applies to the Work as incorporated in a Collection, but this does not require the Collection apart from the Work itself to be made subject to the terms of this License. If You create a Collection, upon notice from any Licensor You must, to the extent practicable, remove from the Collection any credit as required by Section 4(c), as requested.
You may not exercise any of the rights granted to You in Section 3 above in any manner that is primarily intended for or directed toward commercial advantage or private monetary compensation. The exchange of the Work for other copyrighted works by means of digital file-sharing or otherwise shall not be considered to be intended for or directed toward commercial advantage or private monetary compensation, provided there is no payment of any monetary compensation in connection with the exchange of copyrighted works.
If You Distribute, or Publicly Perform the Work or Collections, You must, unless a request has been made pursuant to Section 4(a), keep intact all copyright notices for the Work and provide, reasonable to the medium or means You are utilizing: (i) the name of the Original Author (or pseudonym, if applicable) if supplied, and/or if the Original Author and/or Licensor designate another party or parties (for example a sponsor institute, publishing entity, journal) for attribution ("Attribution Parties") in Licensor's copyright notice, terms of service or by other reasonable means, the name of such party or parties; (ii) the title of the Work if supplied; (iii) to the extent reasonably practicable, the URI, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work. The credit required by this Section 4(c) may be implemented in any reasonable manner; provided, however, that in the case of a Collection, at a minimum such credit will appear, if a credit for all contributing authors of Collection appears, then as part of these credits and in a manner at least as prominent as the credits for the other contributing authors. For the avoidance of doubt, You may only use the credit required by this Section for the purpose of attribution in the manner set out above and, by exercising Your rights under this License, You may not implicitly or explicitly assert or imply any connection with, sponsorship or endorsement by the Original Author, Licensor and/or Attribution Parties, as appropriate, of You or Your use of the Work, without the separate, express prior written permission of the Original Author, Licensor and/or Attribution Parties.
For the avoidance of doubt:
Non-waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme cannot be waived, the Licensor reserves the exclusive right to collect such royalties for any exercise by You of the rights granted under this License;
Waivable Compulsory License Schemes. In those jurisdictions in which the right to collect royalties through any statutory or compulsory licensing scheme can be waived, the Licensor reserves the exclusive right to collect such royalties for any exercise by You of the rights granted under this License if Your exercise of such rights is for a purpose or use which is otherwise than noncommercial as permitted under Section 4(b) and otherwise waives the right to collect royalties through any statutory or compulsory licensing scheme; and,
Voluntary License Schemes. The Licensor reserves the right to collect royalties, whether individually or, in the event that the Licensor is a member of a collecting society that administers voluntary licensing schemes, via that society, from any exercise by You of the rights granted under this License that is for a purpose or use which is otherwise than noncommercial as permitted under Section 4(b).
Except as otherwise agreed in writing by the Licensor or as may be otherwise permitted by applicable law, if You Reproduce, Distribute or Publicly Perform the Work either by itself or as part of any Collections, You must not distort, mutilate, modify or take other derogatory action in relation to the Work which would be prejudicial to the Original Author's honor or reputation.
Representations, Warranties and Disclaimer UNLESS OTHERWISE MUTUALLY AGREED BY THE PARTIES IN WRITING, LICENSOR OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU.
Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Termination
This License and the rights granted hereunder will terminate automatically upon any breach by You of the terms of this License. Individuals or entities who have received Collections from You under this License, however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive any termination of this License.
Subject to the above terms and conditions, the license granted here is perpetual (for the duration of the applicable copyright in the Work). Notwithstanding the above, Licensor reserves the right to release the Work under different license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and effect unless terminated as stated above.
Miscellaneous
Each time You Distribute or Publicly Perform the Work or a Collection, the Licensor offers to the recipient a license to the Work on the same terms and conditions as the license granted to You under this License.
If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this License, and without further action by the parties to this agreement, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent.
This License constitutes the entire agreement between the parties with respect to the Work licensed here. There are no understandings, agreements or representations with respect to the Work not specified here. Licensor shall not be bound by any additional provisions that may appear in any communication from You. This License may not be modified without the mutual written agreement of the Licensor and You.
The rights granted under, and the subject matter referenced, in this License were drafted utilizing the terminology of the Berne Convention for the Protection of Literary and Artistic Works (as amended on September 28, 1979), the Rome Convention of 1961, the WIPO Copyright Treaty of 1996, the WIPO Performances and Phonograms Treaty of 1996 and the Universal Copyright Convention (as revised on July 24, 1971). These rights and subject matter take effect in the relevant jurisdiction in which the License terms are sought to be enforced according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law. If the standard suite of rights granted under applicable copyright law includes additional rights not granted under this License, such additional rights are deemed to be included in the License; this License is not intended to restrict the license of any rights under applicable law.
© BalaSys IT Ltd.
Send your comments to: support@balasys.hu