mirror of
https://github.com/topjohnwu/selinux.git
synced 2025-01-09 12:40:12 +00:00
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>
17 lines
516 B
Groff
17 lines
516 B
Groff
.TH "selinux_check_securetty_context" "3" "1 January 2007" "dwalsh@redhat.com" "SELinux API documentation"
|
|
.SH "NAME"
|
|
selinux_check_securetty_context \- check whether a SELinux tty security context is defined as a securetty context
|
|
.
|
|
.SH "SYNOPSIS"
|
|
.B #include <selinux/selinux.h>
|
|
.sp
|
|
.BI "int selinux_check_securetty_context(char * "tty_context );
|
|
.
|
|
.SH "DESCRIPTION"
|
|
.BR selinux_check_securetty_context ()
|
|
returns 0 if tty_context is a securetty context,
|
|
returns < 0 otherwise.
|
|
.
|
|
.SH "SEE ALSO"
|
|
.BR selinux "(8)"
|