MrHotFire

Ecodesoft Keylogger will let you monitor what people you share your computer with type when you are away. Working in the background, Ecodesoft Keylogger will record every keystroke a user makes in every application and save it to a text file. In Stealth mode, the program is totally invisible to other people who are not aware their computer activity is monitored. Now, below is will show you how to use Ecodsoft Keylogger esaily step by step! First, please download Ecodesoft Keylogger from http://1337x.org/torrent/149957/Ecodsoft-Keylogger-v3-5-8-By-Adrian-Dennis/ and install it. Ecodsoft Keylogger starts before user login on Widows system in background. It will not be detected by your Firewall or anti-virus software and No one know it is running and monitoring. If you want to see the main window, you need press hotkey and input password. So, the first run this software, you need to set the password. used to unhide Ecodsoft Keylogger. And please keep the password in mind. http://http://www.ecodsoft.com/images/1.jpg After click "Save" button, the software will run in background. If you want to see the software, you may press hotkey - "Ctrl+Shift+Alt+Z" to show the Ecodsoft keylogger main window. Please enter your password just set in the beginning. http://http://www.ecodsoft.com/images/2.jpg Now, you can click the "start" button on the top-left of the main page of it to record everything with Ecodsoft Keylogger. Tips: If you quit the software, now the hotkey will have no function. You must reset your computer and then press the hotkey to show the main window. http://http://www.ecodsoft.com/images/3.jpg Click"Status" button It shows what programs could be monitored by Ecodsoft Keylogger, such as: Keyboard, Screenshot, Websites, Clipboard, CD-Rom, MSN Chat, Yahoo, Skype, Facebook , Twitter ect. And the number which constantly changing on the top right of each program icon is the number of operating procedures. For example, if you chat with two people using MSN, then the number on the right top of MSN Chat will be changed to "2". After with the upgrade software, the number of programs could be monitored will continually increase and the list will be changed, even after will be paged. Click "Setting" button. It will enable screenshots to be sent through email. And you can set the e-mail account used to save logs and how frequently let it send logs to you in "Email and password" configuration tab. You can also send a test email. Firstly, you may check the box before "Enable Email Logs Features" Secondly, you may select how frequently let it send logs. The default time is “5 minutes”. Then, you need fill the email message ( "Send To", "Send From", "SMTP Sever", "Server Username", "Server Password" ) and at last click "Apply" button. http://http://www.ecodsoft.com/images/setting.jpg Click "Screenshot" button You can view both sides of a chat conversation by setting Ecodsoft Keylogger's screenshot "Capture Interval" (The minimum time is 1 minute), "Capture Scale" and "Capture Quality". And you also can set several "Trigger" words or phrases in "Smart Sense Capture Setting" column. Whenever these words are typed Ecodsoft Keylogger will capture the current screen and save it to log instantly. http://http://www.ecodsoft.com/images/screenshot.jpg Click" Log" button. Select a specific day of log and then click "View Log" button to view or manage the according log http://http://www.ecodsoft.com/images/log.jpg For example, Select "April 15th", and Click "View Log" button. Then it will start "Ecodsoft Log Manager". You could select the Start date and the End date and click the "Generate Log" button. The logs will list in the log-tree-list and you can view the logs on specific date or time span; http://http://www.ecodsoft.com/images/logscreen.jpg Tips: When you are browsing logs, you can just Right Click on the specific log then you'll see the Delete-Log menu. Here you can select specific type log or all logs on that day. Credits Olympus,Me and Mostly->EcodSoft

:p ty

Example #1 Splitting the result set into pages ... and making superusers (PostgreSQL) <?php $offset = $argv[0]; // beware, no input validation! $query = "SELECT id, name FROM products ORDER BY name LIMIT 20 OFFSET $offset;"; $result = pg_query($conn, $query); ?> Normal users click on the 'next', 'prev' links where the $offset is encoded into the URL. The script expects that the incoming $offset is a decimal number. However, what if someone tries to break in by appending a urlencode()'d form of the following to the URL 0; insert into pg_shadow(usename,usesysid,usesuper,usecatupd,passwd) select 'crack', usesysid, 't','t','crack' from pg_shadow where usename='postgres'; -- If it happened, then the script would present a superuser access to him. Note that 0; is to supply a valid offset to the original query and to terminate it. Note: It is common technique to force the SQL parser to ignore the rest of the query written by the developer with -- which is the comment sign in SQL. A feasible way to gain passwords is to circumvent your search result pages. The only thing the attacker needs to do is to see if there are any submitted variables used in SQL statements which are not handled properly. These filters can be set commonly in a preceding form to customize WHERE, ORDER BY, LIMIT and OFFSET clauses in SELECT statements. If your database supports the UNION construct, the attacker may try to append an entire query to the original one to list passwords from an arbitrary table. Using encrypted password fields is strongly encouraged. Example #2 Listing out articles ... and some passwords (any database server) <?php $query = "SELECT id, name, inserted, size FROM products WHERE size = '$size'"; $result = odbc_exec($conn, $query); ?> The static part of the query can be combined with another SELECT statement which reveals all passwords: ' union select '1', concat(uname||'-'||passwd) as name, '1971-01-01', '0' from usertable; -- If this query (playing with the ' and --) were assigned to one of the variables used in $query, the query beast awakened. SQL UPDATE's are also susceptible to attack. These queries are also threatened by chopping and appending an entirely new query to it. But the attacker might fiddle with the SET clause. In this case some schema information must be possessed to manipulate the query successfully. This can be acquired by examining the form variable names, or just simply brute forcing. There are not so many naming conventions for fields storing passwords or usernames. Example #3 From resetting a password ... to gaining more privileges (any database server) <?php $query = "UPDATE usertable SET pwd='$pwd' WHERE uid='$uid';"; ?> But a malicious user sumbits the value ' or uid like'%admin% to $uid to change the admin's password, or simply sets $pwd to hehehe', trusted=100, admin='yes to gain more privileges. Then, the query will be twisted: <?php // $uid: ' or uid like '%admin% $query = "UPDATE usertable SET pwd='...' WHERE uid='' or uid like '%admin%';"; // $pwd: hehehe', trusted=100, admin='yes $query = "UPDATE usertable SET pwd='hehehe', trusted=100, admin='yes' WHERE ...;"; ?> A frightening example how operating system level commands can be accessed on some database hosts. Example #4 Attacking the database hosts operating system (MSSQL Server) <?php $query = "SELECT * FROM products WHERE id LIKE '%$prod%'"; $result = mssql_query($query); If attacker submits the value a%' exec master..xp_cmdshell 'net user test testpass /ADD' -- to $prod, then the $query will be: <?php $query = "SELECT * FROM products WHERE id LIKE '%a%' exec master..xp_cmdshell 'net user test testpass /ADD' --%'"; $result = mssql_query($query); ?> MSSQL Server executes the SQL statements in the batch including a command to add a new user to the local accounts database. If this application were running as sa and the MSSQLSERVER service is running with sufficient privileges, the attacker would now have an account with which to access this machine. Avoidance Techniques While it remains obvious that an attacker must possess at least some knowledge of the database architecture in order to conduct a successful attack, obtaining this information is often very simple. For example, if the database is part of an open source or other publicly-available software package with a default installation, this information is completely open and available. This information may also be divulged by closed-source code - even if it's encoded, obfuscated, or compiled - and even by your very own code through the display of error messages. Other methods include the user of common table and column names. For example, a login form that uses a 'users' table with column names 'id', 'username', and 'password'. These attacks are mainly based on exploiting the code not being written with security in mind. Never trust any kind of input, especially that which comes from the client side, even though it comes from a select box, a hidden input field or a cookie. The first example shows that such a blameless query can cause disasters. Never connect to the database as a superuser or as the database owner. Use always customized users with very limited privileges. Use prepared statements with bound variables. They are provided by PDO, by MySQLi and by other libraries. Check if the given input has the expected data type. PHP has a wide range of input validating functions, from the simplest ones found in Variable Functions and in Character Type Functions (e.g. is_numeric(), ctype_digit() respectively) and onwards to the Perl compatible Regular Expressions support. If the application waits for numerical input, consider verifying data with ctype_digit(), or silently change its type using settype(), or use its numeric representation by sprintf(). Example #5 A more secure way to compose a query for paging <?php settype($offset, 'integer'); $query = "SELECT id, name FROM products ORDER BY name LIMIT 20 OFFSET $offset;"; // please note %d in the format string, using %s would be meaningless $query = sprintf("SELECT id, name FROM products ORDER BY name LIMIT 20 OFFSET %d;", $offset); ?> If the database layer doesn't support binding variables then quote each non numeric user supplied value that is passed to the database with the database-specific string escape function (e.g. mysql_real_escape_string(), sqlite_escape_string(), etc.). Generic functions like addslashes() are useful only in a very specific environment (e.g. MySQL in a single-byte character set with disabled NO_BACKSLASH_ESCAPES) so it is better to avoid them. Do not print out any database specific information, especially about the schema, by fair means or foul. See also Error Reporting and Error Handling and Logging Functions. You may use stored procedures and previously defined cursors to abstract data access so that users do not directly access tables or views, but this solution has another impacts. Besides these, you benefit from logging queries either within your script or by the database itself, if it supports logging. Obviously, the logging is unable to prevent any harmful attempt, but it can be helpful to trace back which application has been circumvented. The log is not useful by itself, but through the information it contains. More detail is generally better than less. ... <?php $login = mysql_query("select f_uname, f_passwd from t_user where MD5(f_uname) = '".md5($uname)."' and MD5(f_passwd)='".md5($passwd)."'"); ?> The injected requests will be crushed and it will become much more difficult to obtain data in the database. Use both sides of the hash result in a comparison of hash, not the execution of the injected queries. Unfortunately, it probably does not work with other types of queries. Pangolin:Pangolin is an automatic SQL injection penetration testing tool developed by NOSEC. Its goal is to detect and take advantage of SQL injection vulnerabilities on web applications. Once it detects one or more SQL injections on the target host, the user can choose among a variety of options to perform an extensive back-end database management system fingerprint, retrieve DBMS session user and database, enumerate users, password hashes, privileges, databases, dump entire or user"s specific DBMS tables/columns, run his own SQL statement, read specific files on the file system and more. Exists many ways to prevent SQL Injections..etc...but I am tired to write. Credits:Olympus,kirby4 & Me.

All this stuff for such an silly thing.:p thanks

Excellent share. p.s at the univecity they are going to kill us.

Top spammer&top 'sharer'.:p

No worlds to describe it.:) Awesome.

I love PHP. ty

Your friend must be happy.:)

o.O I don't understand why you shared this.

Wow.You must have spent a lot of time to do this.

okap ty.

bump

bump

bump

Working perfectly.

E3aisio.

Thanks!

Nic share.Thanks.

Romeo or any moderator plz transfer it. Wrong section! Soz.

An friend of mine is looking for this items not me. 1x+20 db focus 1xElite Light +4 4x+20 db no focus PM me or right here your prices.Thanks.

Impressive DDoS Protection.

bump