|
L0phtCrack 5
|
|
Hits: 36 |
|
Date added: 10/08/2005 |
|
LC5 is the newest and best version of LophtCrack. LC5 cracks
Windows and Unix passwords. You can Install Admin-Pro-Con version. Best Pass Recovery Tool. |
|
|
|
|
|
Kutty
|
|
Hits: 16 |
|
Date added: 11/29/2006 |
|
The World's Smallest PE Portable Executable. Its only 513 bytes in size!! Tested in Win98SE WinXP. |
|
|
|
|
|
|
KeY Tweak
|
|
Hits: 7 |
|
Date added: 12/05/2005 |
|
KeyTweak is a simple utility that allows users to redefine their keyboard input
signals. Works on Windows 2000 and Windows XP.Change your Key Boards Key arrangement. |
|
|
|
|
|
|
Junction
|
|
Hits: 4 |
|
Date added: 03/01/2005 |
|
Win2K's version of NTFS supports directory symbolic links, where a directory serves as a symbolic link to another directory on the computer. For example, if the directory D:SYMLINK specified C:WINNTSYSTEM32 as its target, then an application accessing D:SYMLINKDRIVERS would in reality be accessing C:WINNTSYSTEM32DRIVERS. Directory symbolic links are known as NTFS junctions in Win2K. Unfortunately, Win2K comes with no tools for creating junctions - you have to purchase the Win2K Resource Kit, which comes the linkd program for creating junctions. I therefore decided to write my own junction-creating tool: Junction. Junction not only allows you to create NTFS junctions, it allows you to see if files or directories are actually reparse points. Reparse points are the mechanism on which NTFS junctions are based, and they are used by Win2K's Remote Storage Service (RSS), as well as volume mount points.
If you want to view reparse information, the usage for Junction is the following:
Usage: junction [-s] <directory or file name>
-s Recurse subdirectories.
If you want to create or delete a junction, use Junction like this:
Usage: junction [-d] <junction directory> [<junction target>]
To delete a junction specify the -d switch and the junction name.
-Source code:
http://www.sysinternals.com/files/jnctnsrc.zip |
|
|
|
|
|
Iron Bars Shell Source v0.3e
|
|
Hits: 1 |
|
Date added: 07/25/2007 |
|
Iron Bars Shell - restricted system shell for Linux/Unix
Iron Bars SHell, or short ibsh is my first attempt to create a restricted working environment for Linux/Unix. I'm sure that many system administrators wish or have wished for a way to lock some/all users into a safe dungeon, where they can only do harm to their own files. Even more important is the protection against users reading sensitive files, for example the /etc/passwd file, which is accessible for any person with an unrestricted shell. But many system files may be listed here. Users could easily gain information, that could help malicious hackers to compromise the system, the network, the company.
Many attempts have already been made to fix this problem. Menu-based and other interactive shells have been created, but they were not able to completely satisfy worried system administrators. The amount of documents available at various security sites about how to bypass restrictions, how to hack through these shells and gain full access, shows, that ANY experienced Linux user is able to cause big problems.
I don't say, that IBSH is the ultimate restricted shell, the final frontier, the only tool you'll ever need, absolutely bugfree and secure. It is also obvious, that one software is not enough to grant security. But i try to create a system here objectively, without thinking that whoever will use it is incompetent, without leaving any hole unfixed, without leaving any chance to anybody to abuse a bug. Bugs in the software are not as dangerous as bugs in the planning, in the thinking, in the design. And this is only the first step. A big step nonetheless. To create a functional, workable environment, additional tools are needed. Text editors, mail clients, browsers, etc. All posing huge threats, all easily abusable, and all already abused a number of times to bypass restrictions. So, while i continue developing the main project, ibsh, i will also try to create restricted tools or restricted tool environments. These will allow users to actually use the shell account for something sensible.
|
|
|
|
