b09cd3072153663bfcce902633b5e6f9134e72e0 |
|
29-Mar-2018 |
Fabiano Fidêncio <fidencio@redhat.com> |
KCM: Adjust REPLY_MAX to the one used in krb5
krb5 has its MAX_REPLY_SIZE set as 10*1024*1024, as seen in:
https://github.com/krb5/krb5/blob/master/src/lib/krb5/ccache/cc_kcm.c#L53
Related:
https://pagure.io/SSSD/sssd/issue/3386
Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com>
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com> |
f3a306cf76d4e72688b750a668ee93de3aad2945 |
|
24-Jul-2017 |
Lukas Slebodnik <lslebodn@redhat.com> |
KCM: temporary increase hardcoded buffers
Temporary workaround:
https://pagure.io/SSSD/sssd/issue/3386
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com> |
2b5518eeaacc6245cfa77ee4a7086f16208060fc |
|
27-Mar-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
KCM: Queue requests by the same UID
In order to avoid race conditions, we queue requests towards the KCM
responder coming from the same client UID.
Reviewed-by: Michal Židek <mzidek@redhat.com>
Reviewed-by: Simo Sorce <simo@redhat.com>
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com> |
1ec4198f38d34a1f82a2db55d8c9782a434fb55f |
|
27-Mar-2017 |
Jakub Hrozek <jhrozek@redhat.com> |
KCM: Implement KCM server operations
Implements the actual KCM server operations. On a high level, each
operation unmarhalls the needed data from the input buffer, calls into
the ccache db and marshalls a response.
Only the operations that are also implemented by the MIT client are
implemented by our KCM server.
Resolves:
https://pagure.io/SSSD/sssd/issue/2887
Reviewed-by: Michal Židek <mzidek@redhat.com>
Reviewed-by: Simo Sorce <simo@redhat.com> |