Hi, According to: http://upstream-tracker.org/versions/libselinux.html we broke compatibility with libselinux 2.3 as a side effect of the security_context_t removal patch (commit 9eb9c93). The issue is that we replaced the previously erroneous const security_context_t == char *const arguments with const char * (the original intent when the const was first added) so we lose constness on the pointer. As per the binary compatibility report from the above site: "Type of 1st parameter ctx has been changed from security_context_t const to char const* (removed const qualifier). This function may change parameter ctx, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications." At the moment I don't think any harm results as we have not changed the functions and thus they should not modify any of the previously const pointers, but I'm wondering if we need to switch them all to const char *const to avoid future incompatibility? _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
