Search results

From SELinux Wiki
Jump to: navigation, search

Page title matches

  • = SELinux Users = ...e generally groups or classes of user. For example all the standard system users could be assigned an SELinux user name of <tt>user_u</tt> and administratio
    1 KB (214 words) - 13:21, 7 December 2014

Page text matches

  • ...ty Enhanced Linux (SELinux) project page. Here you will find resources for users, administrators, vendors and developers. SELinux is a security enhancement to Linux which allows users and administrators more control over access control.
    2 KB (244 words) - 01:12, 30 November 2017
  • organizers/packagers, and power users. The format will be a set of
    3 KB (385 words) - 21:59, 16 July 2008
  • ...otection from broken software or malware running as a normal user or root. Users can grant risky levels of access to files they own. ...under SELinux allows you to provide granular permissions for all subjects (users, programs, processes) and objects (files, devices). In practice, think of s
    3 KB (500 words) - 06:24, 24 May 2008
  • == Administrators and users ==
    461 B (50 words) - 13:17, 2 December 2009
  • be consistent across all users of the interface. Thus
    1 KB (210 words) - 14:14, 29 October 2009
  • * users/dpquigl/lnfs * users/dpquigl/lnfs-patchset
    11 KB (1,725 words) - 13:02, 5 October 2010
  • ...www.slideshare.net/PaulWay/selinux-for-everyday-users SELinux for Everyday Users] (Slides by Paul Wayper) ...ing-policy-for-confined-selinux-users/ Writing policy for confined SELinux users] Red Hat Magazine article by Dan Walsh.
    9 KB (1,259 words) - 07:26, 27 June 2019
  • reseptionist_printer_t? Allow users of email clients to specify
    15 KB (2,267 words) - 10:18, 13 May 2008
  • This is a resource for new users, it explains in very broad terms what SELinux does, how to get it and so on ...curity goals of the system regardless of whether applications misbehave or users act carelessly.
    5 KB (714 words) - 09:07, 7 April 2017
  • ** Lock down users * Document Confined Users
    3 KB (472 words) - 20:29, 27 November 2009
  • documentation, users will also be able to make more use of the MAC An example of this would be to safely allow different users on the
    10 KB (1,342 words) - 02:20, 11 August 2008
  • The network users are mapped between the Kerberos, NFS, and LDAP * PAM is used to authenticate users, which is configured to use Kerberos.
    5 KB (832 words) - 18:24, 11 December 2008
  • The client component of the demonstration utilizes these services to provide users with login access. Automated installation scripts allow clients to be rapi users to access their files from anywhere within the demo enterprise
    10 KB (1,566 words) - 16:46, 6 January 2009
  • ...a password change before it can be changed again. Without a minimum time, users can change their password multiple times and overflow the history (see belo
    12 KB (1,806 words) - 15:15, 12 December 2008
  • # Users can change their shell, anyone else can see it Now 2 nodes need to be added; one for groups and one for users. Create <code>/tmp/usernodes.ldif</code>
    11 KB (1,819 words) - 15:26, 12 December 2008
  • sefos:/ /mnt/nfs4 nfs4 users,sec=krb5 0 0
    8 KB (1,230 words) - 15:53, 15 December 2008
  • = Adding Users = * The GUI 'system-config-users' can also be used.
    11 KB (1,726 words) - 14:16, 11 December 2008
  • users. The format will consist of brief presentations, moderated discussion
    3 KB (341 words) - 22:17, 26 July 2009
  • *Users/Groups **Configure one of the virtual hosts to allow sharing of files from users's public_html directories
    8 KB (1,241 words) - 15:29, 30 September 2009
  • ...ing the Apache HTTP Server to execute scripts can be a security risk. Some users require the Apache HTTP Server to execute CGI scripts. To allow this, first
    2 KB (388 words) - 18:28, 31 August 2010
  • FTP servers read and write objects on behalf of remote users that connect to FTP servers using FTP Clients. ...w the FTP server to read the files that are required to authenticate Linux users.
    7 KB (1,237 words) - 18:30, 31 August 2010
  • * Add export option to NFSv4 to allow users to specify xattr=(xattr name)
    11 KB (1,827 words) - 21:31, 20 October 2009
  • in refpolicy. Certain policy components, like users and object classes, are
    6 KB (979 words) - 17:05, 13 October 2009
  • ...controls allow an administrator of a system to define how applications and users can access different resources such as files, devices, networks and inter-p Though we feel that most users should leave SELinux enabled, especially because it can help mitigate zero-
    6 KB (1,017 words) - 13:56, 16 October 2009
  • Users and vendors who are interested in developing SELinux policy should go to th
    3 KB (494 words) - 14:49, 1 November 2018
  • ...used and that we need to present at more general conferences to reach more users. The schedules and slides are preserved on the SELinux Symposium site for p
    2 KB (246 words) - 15:33, 20 October 2009
  • to support such users, and that MLS support in SELinux can serve as an attractive to ordinary users. Labeled printing was cited as an
    32 KB (5,168 words) - 15:15, 20 October 2009
  • While users sometimes may be trusted to import data directly, a more secure system woul ...essfully make their way through the pipeline will be available inside of a users home directory, specifically, <code>~/inbox</code> and should all have type
    8 KB (1,184 words) - 20:20, 31 August 2010
  • = Users = ...h as the root Linux user and the root SELinux user. By convention, SELinux users that are generic have the suffix "_u", such as ''user_u''.
    3 KB (544 words) - 18:35, 19 November 2009
  • Mult-Category Security (MCS) is an optional addition in SELinux that allows users to add categories to processes and files. This adds the additional constra
    2 KB (365 words) - 14:27, 18 November 2009
  • | Users | Users
    27 KB (3,568 words) - 12:33, 11 December 2014
  • Next we call the two macros from our .if file to allow the respective users run svn and svnadmin under our domains. Running svnserve without transition == Separation of users and repos ==
    13 KB (2,263 words) - 18:22, 13 March 2010
  • ...es. The statement also allows an optional MLS level and range to control a users security level. It is also possible to add SELinux user id's outside the po |The users default MLS security level that has been previously declared with a level S
    4 KB (601 words) - 14:10, 11 December 2014
  • ...no corresponding role_transition rules. This is because the policy expects users to either keep the same role as when they logged onto the system, or use th
    6 KB (951 words) - 15:43, 29 November 2009
  • ...by using boolean expressions covering: source and target types, roles and users as described in the examples. ...ses by using boolean expressions covering: source and target types, roles, users and security levels as described in the examples.
    14 KB (1,999 words) - 15:02, 13 December 2014
  • ...nux GUI (supplied in the polycoreutils-gui rpm) can also be used to manage users, booleans and the general configuration of SELinux as it calls '''semanage' ...x-aware applications. These files and directories should not be updated by users (the majority are read only anyway), however they can be read to check vari
    10 KB (1,516 words) - 15:06, 8 December 2014
  • ...nd '''load_policy'''(8) will read the local customisation for booleans and users. ...ies to ignore (separated by '<tt><nowiki>;</nowiki></tt>') when setting up users home directories. This is used by some distributions to stop labeling <tt>/
    15 KB (2,389 words) - 15:35, 8 December 2014
  • ...cause these keywords are used to identify entries that are associated to a users home directory area. These lines may also have the ROLE keyword declared. ...xts.homedirs entries are created by <tt>genhomedircon</tt> for the SELinux users extracted from the [[#modules/active/seusers.final and seusers Files | seus
    29 KB (4,718 words) - 14:28, 25 September 2015
  • ...users (as defined in the <tt>user</tt> / <tt>passwd</tt> files) to SELinux users (defined in the policy). A typical login sequence would be: ...ning context to be used as the security context, read the <nowiki>contexts/users/[seuser_id]</nowiki> file file. If this file is not present, then:
    39 KB (6,357 words) - 16:47, 10 December 2014
  • * Will the system load, allow users to logon and run applications in permissive mode - If yes then: * Log out users and log in again (as now in enforcing mode, the login may fail), if okay th
    16 KB (2,461 words) - 17:04, 14 March 2010
  • : <tt>'''users'''
    53 KB (8,172 words) - 14:48, 7 May 2018
  • ...y the priviledges they need (e.g. admin users, sales staff users, HR staff users etc.). This again will confine/limit any damage or leakage of data. ...(as there are many ways they could be introduced (including by legitimate users), however it should limit the damage or leaks they cause.
    6 KB (969 words) - 12:45, 24 April 2017
  • ...also governs the ability of subjects to access objects, however it allows users to make policy decisions. The steps in the decision making chain for DAC an
    3 KB (479 words) - 09:08, 7 April 2017
  • It is possible to add constraints on users, roles, types and MLS ranges, for example within a TE environment, the way It is possible to add bounds to users, roles and types, however currently only types are enforced by the kernel u
    5 KB (848 words) - 13:30, 25 September 2015
  • ...makes use of role-based access control (RBAC). This feature allows SELinux users to be associated to one or more roles, where each role is then associated t
    1 KB (167 words) - 13:04, 25 September 2015
  • ...Linux user id of the creating process. It is possible to add contraints on users within policy based on their object class (an example of this is the Refere
    5 KB (831 words) - 13:13, 7 December 2014
  • ...e labeling of objects is managed by the system and generally unseen by the users (until labeling goes wrong !!). As processes and objects are created and de
    12 KB (1,880 words) - 13:36, 25 September 2015
  • ...a greater number of confined daemons and can also confine other areas and users. Red Hat pre-configure MCS support within this policy. : standard - supports confined daemons and can also confine other areas and users (this is an amalgamated version of the older 'targeted' and 'strict' versio
    14 KB (2,128 words) - 13:51, 25 September 2015
  • ...instantiated. If the list is preceded with an '~' character, then only the users in the list will have polyinstantiated directories.
    8 KB (1,268 words) - 14:55, 6 December 2014
  • ...m_namespace.so</tt> module used to manage polyinstantiated directories for users. : <tt>'''pam_selinux_permit.so'''</tt> - Allows pre-defined users the ability to logon without a password provided that SELinux is in enforci
    5 KB (874 words) - 15:45, 6 December 2014

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)