Diffstat (limited to 'doc/man/pam_fail_delay.3')
1 files changed, 134 insertions, 0 deletions
diff --git a/doc/man/pam_fail_delay.3 b/doc/man/pam_fail_delay.3
new file mode 100644
@@ -0,0 +1,134 @@
+.\" Title: pam_fail_delay
+.\" Generator: DocBook XSL Stylesheets v1.73.1 <http://docbook.sf.net/>
+.\" Date: 04/16/2008
+.\" Manual: Linux-PAM Manual
+.\" Source: Linux-PAM Manual
+.TH "PAM_FAIL_DELAY" "3" "04/16/2008" "Linux-PAM Manual" "Linux-PAM Manual"
+.\" disable hyphenation
+.\" disable justification (adjust text to left margin only)
+pam_fail_delay - request a delay on failure
+.BI "int pam_fail_delay(pam_handle_t\ *" "pamh" ", unsigned\ int\ " "usec" ");"
+function provides a mechanism by which an application or module can suggest a minimum delay of
+micro\-seconds\. The function keeps a record of the longest time requested with this function\. Should
+fail, the failing return to the application is delayed by an amount of time randomly distributed (by up to 25%) about this longest value\.
+Independent of success, the delay time is reset to its zero default value when the PAM service module returns control to the application\. The delay occurs
+all authentication modules have been called, but
+control is returned to the service application\.
+When using this function the programmer should check if it is available with:
+#endif /* HAVE_PAM_FAIL_DELAY */
+For applications written with a single thread that are event driven in nature, generating this delay may be undesirable\. Instead, the application may want to register the delay in some other way\. For example, in a single threaded server that serves multiple authentication requests from a single event loop, the application might want to simply mark a given connection as blocked until an application timer expires\. For this reason the delay function can be changed with the
+item\. It can be queried and set with
+respectively\. The value used to set it should be a function pointer of the following prototype:
+void (*delay_fn)(int retval, unsigned usec_delay, void *appdata_ptr);
+The arguments being the
+return code of the module stack, the
+micro\-second delay that libpam is requesting and the
+that the application has associated with the current
+\fIpamh\fR\. This last value was set by the application when it called
+or explicitly with
+\fBpam_set_item\fR(3)\. Note, if PAM_FAIL_DELAY item is unset (or set to NULL), then no delay will be performed\.
+It is often possible to attack an authentication scheme by exploiting the time it takes the scheme to deny access to an applicant user\. In cases of
+timeouts, it may prove possible to attempt a
+dictionary attack \-\- with an automated process, the attacker tries all possible passwords to gain access to the system\. In other cases, where individual failures can take measurable amounts of time (indicating the nature of the failure), an attacker can obtain useful information about the authentication process\. These latter attacks make use of procedural delays that constitute a
+of useful information\.
+To minimize the effectiveness of such attacks, it is desirable to introduce a random delay in a failed authentication process\. Preferable this value should be set by the application or a special PAM module\. Standard PAM modules should not modify the delay unconditional\.
+For example, a login application may require a failure delay of roughly 3 seconds\. It will contain the following code:
+ pam_fail_delay (pamh, 3000000 /* micro\-seconds */ );
+ pam_authenticate (pamh, 0);
+if the modules do not request a delay, the failure delay will be between 2\.25 and 3\.75 seconds\.
+However, the modules, invoked in the authentication process, may also request delays:
+module #1: pam_fail_delay (pamh, 2000000);
+module #2: pam_fail_delay (pamh, 4000000);
+in this case, it is the largest requested value that is used to compute the actual failed delay: here between 3 and 5 seconds\.
+.SH "RETURN VALUES"
+Delay was successful adjusted\.
+A NULL pointer was submitted as PAM handle\.
+.SH "SEE ALSO"
+function is an Linux\-PAM extension\.