super
Super allows an admin to control access to files and functions for users. It is similar to sudo, but uses a different approach in the configuration file. Super acts as a SetUID wrapper around system commands to make sure the commands are executed safely, and only by authorized users.
| Licenses | Artistic GPL |
|---|
Recent releases
- 06 Aug 2001 14:46
No changes have been submitted for this release.
- 10 Feb 2001 03:52
Changes: This release includes PAM support, support for shadow passwords in Digital Unix 4.x, fixes for HP-UX 11.0 with tcb enabled, a fix for an error in printing a message when super is not running setuid-root, an option to specify the prompt for passwords, improved description of some envvars, correct processing of "die=message" options, and some minor readability improvements.
- 30 Jan 2001 06:14
Changes: This version features bug fixes, new built-in variables, and the addition of super.init.
- 30 Jan 2001 06:14
Changes: This release fixes some buffer overflow problems with per-user configuration files
- 30 Jan 2001 06:14
Changes: RPMs are now avaiable for super version 3.11.9 which fixes the buffer overflow problem reported last week.
- All comments
Recent commentsRPM package for version 3.16.1 (last stable)
I am using super-3.14.0-1.
I can't found any binary RPM package for version 3.16.1 (lat stable). The RPM URL has version 3.14.0-1 as well (actually I downloaded it from there).
Any friendly souls out there? Thanks!
logfile creation with security problems?
First of all: what a great program!
Now let's get to business :-)
If you specify the global options in the table file:
:global logfile=/path/yourfile loguid=root
and 'yourfile' does not exist, it *could* be created with incorrect permissions/owner. In this example command, the logfile is created with permissions -rw-rw-r-- and owner root:myusergroup.
test/simple "/bin/echo simple test." \
uid=<caller> :users \
info="Test - simple test command. Should always work." \
# end
so, executing: 'super test/simple'
creates the files as described.
In my example, my user's main gid is the same as the uid (symbolically). If the user is me:maingid, the file is owned by root:maingid.
Workaround: 'touching' (creating) the file as root and setting (if needed) permissions/ownership of the file seems to solve it. I' ve set it to root:root and -rw-------
Please fix it!
And/or include more options in order to control/set creation mask and gid of logfiles.
Sorry about this post. Could not found anything useful around there to send this comment. I am sending this to the author as well.
FTP link for rpm should be
The FTP link for rpm should be ftp://ftp.mdtsoft.com/pub/super/super-3.12.1-1.i386.rpm (ftp://ftp.mdtsoft.com/pub/super/super-3.12.1-1.i386.rpm)