{"push_id":2792204353,"size":5,"distinct_size":5,"ref":"refs/heads/secapi","head":"7bd53d5a54b69dda3a00c867323b96d5d3b4197f","before":"c0a71a8ec1e6a76b3a0105f390d3a5b17b5b0673","commits":[{"sha":"3edfde359c5d0466fa49bfc5b51d874bd8e1b0ca","author":{"name":"Jakub Hrozek","email":"1d29819f3dc2f357f8859ebb61f57619f33263ae@redhat.com"},"message":"KCM: Add a new back end that uses libsss_secrets directly\n\nAdd a new KCM back end that stores the ccaches in libsss_secrets\ndirectly by using its API. The back end is only fake-async as all the\nlibsss_secrets functions are synchronous.\n\nRelated:\nhttps://pagure.io/SSSD/sssd/issue/3685","distinct":true,"url":"https://api.github.com/repos/jhrozek/sssd/commits/3edfde359c5d0466fa49bfc5b51d874bd8e1b0ca"},{"sha":"5b47421bff2f4929204d8f39129b0460d9e7b4e6","author":{"name":"Jakub Hrozek","email":"1d29819f3dc2f357f8859ebb61f57619f33263ae@redhat.com"},"message":"TESTS: Get rid of KCM_PEER_UID\n\nIn normal operation, libsss_secret only allows root to write to the KCM\nnamespace. This was impractical in tests, because the identity of the\nclient is read from the socket and even with the socket and uid\nwrapping, still the real UID was used. So we #define-d the client ID to\nsomething else during tests.\n\nBut this is also problematic for tests that do not use the secrets\nresponder, but only the libsecrets, beacause there the ID of the caller\nis root, because of uid_wrapper.\n\nThis patch changes the approach so that the secrets responder tests\npreload getsockopt_wrapper() and any communication to the secrets socket\nrewrites the client credentials to be root. In combination with\nuid_wrapper which pretends to libsss_secrets that the caller is root, we\ncan get rid of test-specific #define in the code.\n\nRelated:\nhttps://pagure.io/SSSD/sssd/issue/3685","distinct":true,"url":"https://api.github.com/repos/jhrozek/sssd/commits/5b47421bff2f4929204d8f39129b0460d9e7b4e6"},{"sha":"9191d9af6fc7a669057b5696c446bcb6dc5e7480","author":{"name":"Jakub Hrozek","email":"1d29819f3dc2f357f8859ebb61f57619f33263ae@redhat.com"},"message":"TESTS: Add tests for the KCM libsss_secrets back end\n\nRelated:\nhttps://pagure.io/SSSD/sssd/issue/3685","distinct":true,"url":"https://api.github.com/repos/jhrozek/sssd/commits/9191d9af6fc7a669057b5696c446bcb6dc5e7480"},{"sha":"fc4e8a1662440d692b431226f810de7761057d91","author":{"name":"Jakub Hrozek","email":"1d29819f3dc2f357f8859ebb61f57619f33263ae@redhat.com"},"message":"KCM: Change the default ccache storage from the secrets responder to libsecrets\n\nRelated:\nhttps://pagure.io/SSSD/sssd/issue/3685","distinct":true,"url":"https://api.github.com/repos/jhrozek/sssd/commits/fc4e8a1662440d692b431226f810de7761057d91"},{"sha":"7bd53d5a54b69dda3a00c867323b96d5d3b4197f","author":{"name":"Jakub Hrozek","email":"1d29819f3dc2f357f8859ebb61f57619f33263ae@redhat.com"},"message":"BUILD: Do not build the secrets responder by default\n\nThe secrets responder is now built only conditionally and defaults to\n'do not build'. However, libsss_secrets.so is built whenever either KCM\nor secrets are selected.\n\nThe KCM secrets responder tests are skipped if the secrets responder is\nnot built.\n\nThis patch also avoids two BuildRequires in the default set,\nlibcurl-devel and http-parser-devel are no longer required by SSSD.\n\nRelated:\nhttps://pagure.io/SSSD/sssd/issue/3685","distinct":true,"url":"https://api.github.com/repos/jhrozek/sssd/commits/7bd53d5a54b69dda3a00c867323b96d5d3b4197f"}]}
{"actor":{"display_login":"jhrozek"}}