|
LEVI 0.4
|
|
Hits: 8 |
|
Date added: 03/21/2007 |
|
LEVI is code profiling tool for Windows NT-2000 which monitors imported and inline code constructs. |
|
|
|
|
|
Lidstools v2.2.7.2
|
|
Hits: 1 |
|
Date added: 08/06/2007 |
|
LIDS is an enhancement for the Linux kernel written by Xie Huagang and Philippe Biondi. It implements several security features that are not in the Linux kernel natively. Some of these include: mandatory access controls (MAC), a port scan detector, file protection (even from root), and process protection. |
|
|
|
|
|
Linux sysmask v1.08
|
|
Hits: 4 |
|
Date added: 08/03/2007 |
|
Sysmask is a security solution designed for Linux systems. It can protect
the system integrity against vulnerabilities in the great majority of codes,
whether known or unknown, patched or non-patched, in user programs,
libraries or the kernel.
Sysmask can be configured to restrict the access of a process or a user to
system resources: files, sockets, devices, system calls, disk space, memory
usage. The restriction policy can be defined with great precision, sometimes
contextual. Processes with tightly restricted access rights may continue to
do their normal work as before, but if they are compromised, the malicious
code that gets run will be unable to harm the system except for the job that
is assigned to the compromised process.
A fully deployed sysmask can protect the system against any vulnerability
except those in a small portion of the kernel, which is historically very
solid, plus those in the sysmask package itself.
With respect to other security solutions, several novel features have been
introduced in sysmask.
1. It offers protection against most kernel vulnerabilities that occur or
will occur in practice, by allowing selective closure of unused system
calls and activities for untrusted processes or users.
2. Using configuration definitions with a simple user-friendly syntax,
interactive security reactions can be defined in various ways, leading to
flexible and highly customizable security schemes without the need to
recompile existing softwares nor even to modify their configurations.
Custom interactive reactions greatly enhance the security level, as the
system behavior becomes unpredictable to outside attackers with no knowledge
of these reactions.
3. It can protect against both system level risks (unauthorized accesses
etc.) and user level risks (viruses etc.), and includes efficient resource
consumption limitations that overcome the shortcomings of traditional rlimit
setups.
4. It supports runtime reconfiguration with a menu-based user interface that
accepts feedback configuration.
Sysmask introduces only minimal or negligeable performance overhead, except
for a few programs under special conditions and requiring highly selective
protection.
The package of sysmask is also very simple and compact, with its critical
parts independent of outside codes (libraries), minimizing the probability
of bugs contained in the package itself.
Sysmask allows you to radically reduce the need to update your system
components for security reasons, because you can now live with
vulnerabilities without being hurt. Traditional anti-virus scanners are no
longer needed, let alone the need to update them, because sysmask can
prevent any virus from being installed. |
|
|
|
|
|
|
ListDLLs Alpha
|
|
Hits: 2 |
|
Date added: 01/26/2005 |
|
Download ListDLLs-Alpha |
|
|
|
|
|
|
ListDLLs x86
|
|
Hits: 4 |
|
Date added: 01/26/2005 |
|
A question that I often get asked is Do you know of a utility that will show me which DLLs are loaded on Windows 9x or NT? . The answer I gave up until recently was no , until I discovered a tool in the Windows NT Resource Kit called tlist that does show this information. I decided to write a free-ware version, ListDLLs. Unlike tlist, however, ListDLLs is able to show you the full path names of loaded modules - not just their base names. In addition, ListDLLs will flag loaded DLLs that have different version numbers than their corresponding on-disk files (which occurs when the file is updated after a program loads the DLL), and can tell you which DLLs were relocated because they are not loaded at their base address. |
|
|
|
