| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Mirrors what we have done with the monitor.
|
| |
|
|
|
|
|
| |
Make as much as possible static, and remove use of talloc_reference and
allocation/deallocation of memory when not necessary.
Fix also responder use of rctx->conn, was mistakenly used for both
monitor and dp connections.
|
| |
|
|
|
| |
Rationalize and rename connection names in preparatoin for merging of server and
connection structures.
|
| |
|
|
| |
Simplify code by removing stuff that is never used or redundant.
|
| | |
|
| |
|
|
|
| |
- allow unspecified value in struct pam_data to be NULL
- check if domain structure is initialized in pam_reply
|
| |
|
|
|
|
|
| |
Implement credentials caching in pam responder.
Currently works only for the proxy backend.
Also cleanup pam responder code and mode common code in data provider.
(the data provider should never include responder private headers)
|
| | |
|
| |
|
|
|
|
|
| |
May happen at startup if, for some reason dp is very slow to start and we
receive a request before a reconnection is rescheduled in the responder dp
reconnection code.
This shouldn't happen normally so make it clear with a debug statement.
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
Also move responders under server/responder with shared code
in server/responder/common
Signed-off-by: Simo Sorce <ssorce@redhat.com>
|
