KeyWEn.com  
 
 
 
Setuid       Article     History   Tree Map
  Encyclopedia of Keywords > Root User > Setuid   Michael Charnine

Keywords and Sections
CERTAIN SETUID BINARY
SETUID BIT
PROCESSES
PROCESS
ACCESS CONTROL
KEY POINT
USER
PROGRAM
SET
SETUID ROOT
QUAKE
STICKY BIT
STICKY
TRACEROUTE
PERMISSIONS
USERS
EXECUTING
SYSTEMS
SCRIPTS
EXECUTABLE
ROOT
ROOT USER
SETUID
Review of Short Phrases and Links

    This Review contains major "Setuid"- related terms, short phrases and links grouped together in the form of Encyclopedia article.

Certain Setuid Binary

  1. Or an attacked would have to convince users to run certain setuid binary files.

Setuid Bit

  1. The setuid bit adds 4 to the total, The setgid bit adds 2 to the total, and The sticky bit adds 1 to the total.

Processes

  1. For obvious reasons this doesn't apply to processes spawned from setuid and setgid binaries.

Process

  1. In some cases a process can affect the various UID and GID values; see setuid(2), seteuid(2), setreuid(2), and the Linux-unique setfsuid(2).
  2. This protection can be bypassed by first obtaining a descriptor to a process you own then let that process execve() a setuid binary.

Access Control

  1. Access control doesn't work with my setuid applications Note: This only applies to mSQL version 1.0.10 and previous versions.

Key Point

  1. Key point: Windows doesn't have the concept of setuid.

User

  1. The server creates a separate process to serve each session, and uses system calls setuid and setgid to accord permissions logged in user.
  2. If setuid bit is set, when the file will be executed by a user, the process will have the same rights as the owner of the file being executed.

Program

  1. A clever user could exploit a bug or security hole in a setuid program to gain root access to your system.
  2. The icmp protocol requires that the program be run as root or that it be setuid to root.

Set

  1. The setuid and setgid bits are normally set with the command chmod by setting the high-order octal to 4 or 2 (or 6 to set both).
  2. But chmod command executed from the shell gives you an ability to set also setuid, setgid and sticky bits.
  3. When a program is executed, and its file has its setuid or setgid bit set, the process' EUID or EGID (respectively) is usually set to the file's value.

Setuid Root

  1. To use FTP on the standard port (21), your DBA has to chown the TNS listener to setuid ROOT rather than setuid ORACLE.
  2. Since inndstart is setuid root, it is extremely restrictive about who can run it and what it is willing to do.
  3. By default, Mandrake Linux ships linuxconf as setuid root in versions 7.2 through 8.2.

Quake

  1. See Running X and GL games without setuid in the Tips and Tricks section below for information on running Quake II without root permissions.
  2. If you plan to only run Quake II with the GL or X renderers, your quake2 doesn't need to be setuid root.

Sticky Bit

  1. The x will be an s if the setuid or setgid bit is also set, and in the third, it will be a t if the sticky bit is set.
  2. The sticky bit can be set using the chmod command and can be set using its octal mode 1000 or by its symbol t (s is already used by the setuid bit).
  3. New files always start with a clear sticky bit and clear setuid bit.

Sticky

  1. Special ACL configurations are also used to represent the sticky, setuid and setgid flags which have no real equivalent in Windows.

Traceroute

  1. Unfortunately without the setuid bit, traceroute can not work properly for normal users.
  2. Provide traceroute as a CGI service without using a setuid binary.

Permissions

  1. Some operating systems that may being acting as clients to your KDC do not set the permissions for ksu to be setuid root.
  2. This has the effect of setting the setuid bit in the file permissions.

Users

  1. Similarly, inndstart will always setuid() and setgid() to those users before running innd.
  2. Users of client computers can set the setuid (set-user-identifier-on-execution) bit for a file.
  3. Most users have used setuid executables even if they have not realized it.

Executing

  1. The problem is that there were security problems with traceroute (in 2002) that allowed a local user to cause problems (?) by executing it setuid.

Systems

  1. Suggested topics: volume managers, file systems, files, directories, ls, find, chown, chgrp, chmod, umask, setuid, setgid, device files, ACLs.
  2. Some systems, such as Linux, completely ignore the setuid and setgid bits when executing scripts, which is clearly a safe approach.
  3. Mac OS X v10.6 systems are only affected if the setuid bit has been set on the binary.

Scripts

  1. Since support for setuid scripts varies on Unix-like systems, they're best avoided in new applications where possible.
  2. The scripts used to start and stop Adobe Version Cue are configured with set user id (setuid) root user privileges and do not validate the path names.
  3. As a result, most UNIX kernels will disable users from running scripts as setuid.

Executable

  1. By default the ntop port is installed setuid root and only executable by root and members of the 'wheel' group.
  2. In a normal INN installation, it is installed setuid root and executable only by users in the news group.
  3. An executable file which has the setuid bit set will execute under the user ID of the file's owner, not the user ID of the user who is executing the file.

Root

  1. Look for setuid and setgid files (especially setuid root files) everywhere on your system.
  2. The quake2 executable was installed setuid root so that it can access the graphics devices on your system.
  3. If the user is root or the program is setuid root, special care must be taken.

Root User

  1. The command should be setuid to the root user and have the trusted computing base attribute.
  2. The ioperm() call requires your program to have root privileges; thus you need to either run it as the root user, or make it setuid root.

Setuid

  1. When the executable is setuid to root, it is vital to ensure that it does not extend read and write permissions to its group or to the world.
  2. It must be setuid, because it changes files only root has access to, but yet it must be runnable by users.
  3. Many Unix-like systems, in particular Linux, simply ignore the setuid and setgid bits on scripts to avoid the race condition described earlier.

Categories

  1. Root User
  2. Information Technology > Computers > Operating Systems > Executable
  3. Unix-Like Systems
  4. Executing
  5. Chmod
  6. Books about "Setuid" in Amazon.com

Book: Keywen Category Structure


  Short phrases about "Setuid"
  Originally created: July 17, 2008.
  Please send us comments and questions by this Online Form
  Please click on Move Up to move good phrases up.
0.0191 sec. a=1..