9eb9c93275
In attempting to enable building various part of Android with -Wall -Werror, we found that the const security_context_t declarations in libselinux are incorrect; const char * was intended, but const security_context_t translates to char * const and triggers warnings on passing const char * from the caller. Easiest fix is to replace them all with const char *. And while we are at it, just get rid of all usage of security_context_t itself as it adds no value - there is no true encapsulation of the security context strings and callers already directly use string functions on them. typedef left to permit building legacy users until such a time as all are updated. This is a port of Change-Id I2f9df7bb9f575f76024c3e5f5b660345da2931a7 from Android, augmented to deal with all of the other code in upstream libselinux and updating the man pages too. Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov> Acked-by: Eric Paris <eparis@redhat.com>
23 lines
634 B
Groff
23 lines
634 B
Groff
.TH "security_check_context" "3" "1 January 2004" "russell@coker.com.au" "SELinux API documentation"
|
|
.SH "NAME"
|
|
security_check_context \- check the validity of a SELinux context
|
|
.
|
|
.SH "SYNOPSIS"
|
|
.B #include <selinux/selinux.h>
|
|
.sp
|
|
.BI "int security_check_context(char * "con );
|
|
.sp
|
|
.BI "int security_check_context_raw(char * "con );
|
|
.
|
|
.SH "DESCRIPTION"
|
|
.BR security_check_context ()
|
|
returns 0 if SELinux is running and the context is valid, otherwise it
|
|
returns \-1.
|
|
|
|
.BR security_check_context_raw ()
|
|
behaves identically to
|
|
.BR \%security_check_context ()
|
|
but does not perform context translation.
|
|
.
|
|
.SH "SEE ALSO"
|
|
.BR selinux "(8)"
|