specifies the further execution of a server process when receiving bad packets from a possibly malicious client.
The server process continues execution. The database server may be subject to a Denial of Service (DoS) if bad packets continue to be sent by a malicious client.
The client experiences a delay of integer seconds before the server process accepts the next request from the same client connection. Malicious clients are prevented from excessive consumption of server resources while legitimate clients experience a degradation in performance but can continue to function.
The server forcefully terminates the client connection after integer bad packets. The server protects itself at the expense of the client (for example, a client transaction may be lost). The client may reconnect and attempt the same operation.
specifies the number of authentication attempts that can be made by a client on a connection to the server process. After the specified number of failure attempts, the connection will be automatically dropped by the server process.
specifies the action that the database should take when bad packets are received from a possibly malicious client.
The database server ignores the bad packets and does not generate any trace files or log messages.
A detailed trace file is generated when bad packets are received, which can be used to debug any problems in client/server communication.
A minimal log message is printed in the alert logfile and in the server trace file. A minimal amount of disk space is used.
An alert message is sent to a DBA or monitoring console.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/8747612/viewspace-1974729/，如需转载，请注明出处，否则将追究法律责任。