File: control

package info (click to toggle)
op 1.32-4
  • links: PTS, VCS
  • area: main
  • in suites: lenny, squeeze
  • size: 716 kB
  • ctags: 360
  • sloc: ansic: 2,272; sh: 800; lex: 447; makefile: 68
file content (32 lines) | stat: -rw-r--r-- 1,103 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
Source: op
Section: admin
Priority: extra
Maintainer: Michael Prokop <mika@grml.org>
Build-Depends: debhelper (>= 5), autotools-dev, flex, libpam0g-dev
Standards-Version: 3.7.2
Homepage: http://swapoff.org/wiki/op
Vcs-git: git://git.grml.org/op.git
Vcs-Browser: http://git.grml.org/?p=op.git

Package: op
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, adduser
Description: sudo like controlled privilege escalation
 The op tool provides a flexible means for system administrators
 to grant access to certain root operations without having to
 give them full superuser privileges. Different sets of users may
 access different operations, and the security-related aspects of
 each operation can be carefully controlled.
 .
 The main attraction of op over sudo is the use of mnemonics
 rather than true commands. This allows an administrator to
 present users with more intuitive commands.
 .
 Other available features are:
 .
  - fine-grained per-command control
  - a really short name
  - host-based access control
  - command expiration
  - variable expansion
  - multi-line arguments