diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2018-02-11 13:04:56 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2018-02-11 13:04:56 +0000 |
| commit | 0a7251045255a3e41bad384738a5c5296750d061 (patch) | |
| tree | 3c39b752201ad8754e5d3c8928d0c45f53d11a3f | |
| parent | 95744799b696198aa9eb358d4f8fbaa002b34ef9 (diff) | |
| download | pamela-0a7251045255a3e41bad384738a5c5296750d061.tar.xz | |
doc: conversation clarification
| -rw-r--r-- | doc/building.html | 6 | ||||
| -rw-r--r-- | doc/index.html | 6 |
2 files changed, 10 insertions, 2 deletions
diff --git a/doc/building.html b/doc/building.html index fdd0cd8..ff25de1 100644 --- a/doc/building.html +++ b/doc/building.html @@ -122,8 +122,10 @@ solution is to rewrite these modules so they communicate the change they wish to make via the official PAM API, and have the application perform the change itself. PAM provides a way to do this: the <em>conversation function</em>, which exchanges data -between PAM and the application. pamela fully supports custom -conversation functions. +between PAM and the application. Currently, only four types of +messages are officially specified by PAM, but the mechanism is +easily extensible and was designed for this. pamela fully supports +customized conversation functions with any message type. </p> </body> diff --git a/doc/index.html b/doc/index.html index 3c2f58c..b7cd020 100644 --- a/doc/index.html +++ b/doc/index.html @@ -48,6 +48,12 @@ for privilege elevation. <hr /> +<ul> +<li> <a href="building.html">How to build an application with pamela</a> </li> +</ul> + +<hr /> + <h2> Installation </h2> <h3> Requirements </h3> |