About:
noexec is a package for preventing a process from exec'ing another process. It can be a useful security measure to prevent a user from escaping to a shell. It may be able to prevent some kinds of CGI exploits.

Author:
Valery Reznic [contact developer]

Rating:	reset 1 2 3 4 5 6 7 8 9 10
(not rated)

Homepage:
http://noexec.sourceforge.net/
Tar/GZ:
http://prdownloads.sourceforge.net/noexec/noexec-1.1.0.tar.gz?download
Changelog:
http://noexec.sourceforge.net/noexec/changelog.html
RPM package:
http://sourceforge.net/[..]les.php?group_id=82302&release_id=211747
CVS tree (cvsweb):
http://noexec.cvs.sourceforge.net/noexec/

Trove categories: [change]

[Development Status]		5 - Production/Stable
[Environment]		Console (Text Based)
[Intended Audience]		System Administrators
[License]		OSI Approved :: GNU General Public License (GPL), OSI Approved :: GNU Lesser General Public License (LGPL)
[Operating System]		POSIX :: Linux, POSIX :: SunOS/Solaris
[Programming Language]		C
[Topic]		Security, System :: Systems Administration

Dependencies: [change]
No dependencies filed

 Branches

Branch	Version	Last release	License	URLs
Default	1.1.0	22-Jan-2004	GNU General Public License (GPL)

 Releases

Version	Focus	Date
1.1.0	Minor feature enhancements	22-Jan-2004 14:06
1.0.0	Initial freshmeat announcement	16-Jun-2003 15:07

 Comments

[»] Uhm
by Pelle Johansson - Jan 22nd 2004 06:51:16

I'd like to point out that many if not most buffer overflow
attacks call the syscall for execve directly, which this
won't protect against. Only the kernel can protect
against that.

[reply] [top]

[»] Re: Uhm
by Valery Reznic - Jan 24th 2004 23:10:42


> I'd like to point out that many if not
> most buffer overflow
> attacks call the syscall for execve
> directly, which this
> won't protect against. Only the kernel
> can protect
> against that.
I agree, but "may-be-more-secure" is the only side-effect, noit main feature. Main feature is prevent execve usage.

Valery



[reply] [top]

---