Sunday, 3 June 2012
Keys for Operating Systems & Office
windows Xp service pack1
S/N: YDYQ7-M37FK-JFFPU-QBPBB-44FDM
******************************
Windows XP professional 2003
S/N: QW4HD-DQCRG-HM64M-6GJRK-8K883T
******************************
Windows XP Professional Volume
S/N: V2C47-MK7JD-3R89F-D2KXW-VPK3J
******************************
Windows XP Home Edition Version 2002
S/N: PWXHQ-QRPGD-KF9QM-BVW7F-23J6Q
******************************
Microsoft Office 2003
S/N: xk4bv-38k2b-jpjh9-c4txb-f737b
******************************
Microsoft office professional 2007
V9MTG-3GX8P-D3Y4R-68BQ8-4Q8VD
TP3FH-CVJR2-MR7G7-W2HFW-TJCHD
******************************
Windows 2003 Server Enterprise
S/N: BF2WP-CYWJR-BM8K7-BM8PT-H4KRD
JB88F-WT2Q3-DPXTT-Y8GHG-7YYQY
******************************
Windows 2003 Server Enterprise + Server to Workstation
S/N: DVH7B-VB7YM-CXDPD-D9BQX-J3M76
******************************
Windows 2003 Web Server
S/N: D42X8-7MWXD-M4B76-MKYP7-CW9FD
******************************
Windows 2000 Server
s/n: RBDC9-VTRC8-D7972-J97JY-PRVMG
******************************
Windows 2000 Professional
s/n: RBDC9-VTRC8-D7972-J97JY-PRVMG
******************************
microsoft office 2003
S/N: XK4BV-38K2B-JPJH9-C4TXB-F737B
S/N: K3YFQ-HFJH7-WYG6K-X6WJW-9QTXW
******************************
Windows NT Server 4.0
s/n: 427-5632883
******************************
windows Xp service pack1
S/N: YDYQ7-M37FK-JFFPU-QBPBB-44FDM
******************************
Windows XP professional 2003
S/N: QW4HD-DQCRG-HM64M-6GJRK-8K883T
******************************
Windows XP Professional Volume
S/N: V2C47-MK7JD-3R89F-D2KXW-VPK3J
******************************
Windows XP Home Edition Version 2002
S/N: PWXHQ-QRPGD-KF9QM-BVW7F-23J6Q
******************************
Microsoft Office 2003
S/N: xk4bv-38k2b-jpjh9-c4txb-f737b
******************************
Microsoft office professional 2007
V9MTG-3GX8P-D3Y4R-68BQ8-4Q8VD
TP3FH-CVJR2-MR7G7-W2HFW-TJCHD
******************************
Windows 2003 Server Enterprise
S/N: BF2WP-CYWJR-BM8K7-BM8PT-H4KRD
JB88F-WT2Q3-DPXTT-Y8GHG-7YYQY
******************************
Windows 2003 Server Enterprise + Server to Workstation
S/N: DVH7B-VB7YM-CXDPD-D9BQX-J3M76
******************************
Windows 2003 Web Server
S/N: D42X8-7MWXD-M4B76-MKYP7-CW9FD
******************************
Windows 2000 Server
s/n: RBDC9-VTRC8-D7972-J97JY-PRVMG
******************************
Windows 2000 Professional
s/n: RBDC9-VTRC8-D7972-J97JY-PRVMG
******************************
microsoft office 2003
S/N: XK4BV-38K2B-JPJH9-C4TXB-F737B
S/N: K3YFQ-HFJH7-WYG6K-X6WJW-9QTXW
******************************
Windows NT Server 4.0
s/n: 427-5632883
******************************
Now open keyfinder.exe Click on options and click “change windows key”Now enter this key and you’re done.
******************************
V2C47-MK7JD-3R89F-D2KXW-VPK3J
******************************
How to lock the folder.
You can lock and unlock your folder with this simple trick !
Procedure :
1. Make a folder on the desktop and name it as “folder”
2. Now, open notepad and write ren folder folder.{21EC2020-3AEA-1069-A2D
3. In the ‘save as’ name it as lock.bat and click save ! (Save it on Desktop)
4. Now, again open notepad again and write ren folder.{21EC2020-3AEA-1069-A2D
5. In the ‘save as’ name it as key.bat and click save ! (Save it on Desktop)
6. Now, double click lock.bat to lock the folder and now if you open your folder, control panel will open up !
7. Now, double click key.bat to open the folder and now if you open
your folder, you can access your data inside the folder again !
8. Lock your folder and hide the key.bat somewhere else on your hard disk !
9. Whenever you want to open your folder just paste the key.bat on desktop and open your folder using it !
Key for Macromedia Dreamweaver Mx 2004
WPD700-55505-18294-24343
WPD700-58202-88194-29915
WPD700-55303-93994-94030
DWD700-55753-32200-90586
DWD700-59557-38400-14388
DWD700-51359-91800-15900
DWD700-52856-62700-61021
CATCH LINUX SYSTEM INTRUDERS .. ;) ..
There's
no doubt that Linux is a secure operating system. However, nothing is
perfect. Millions of lines of code are churned through the kernel every
second and it only takes a single programming mistake to open a door
into the operating system. If that line of code happens to face the
Internet, that's a backdoor to your server.
The eyes have it
Patches are often released quicker and more often for Linux systems
than they are for proprietary products. This is because anyone can take a
look at the code – and thousands of developers regularly do. This 'many
eyes' approach, which was advanced by Linus Torvalds, means that
problems like back doors are usually found quickly. It also means that
fixes are released just as quickly.
There's been a very vocal
debate on the Linux kernel mailing list recently, with developers
arguing about whether security bugs that are fixed should be formally
announced and documented. Torvalds believes that making a big song and
dance about security patches attracts the attention of miscreants like
bees to honey. Others believe that anything but complete openness goes
against the philosophy of Free Software.
The debate is still
burning, but while the overlords of the Linux kernel are deciding which
way to swing, there's a great deal you can do to protect your system,
even if an Internet facing service is compromised in some way.
Watching for traps with Tripwire
Tripwire generates checksums from all the essential binaries that are
running on your system. Every file has a completely unique checksum. If a
single bit of data changes in the file, the checksum it generates will
be completely different.
These checksums can't be cracked or
duplicated because they rely on a tried and tested method of encryption.
Using this database of checksums, Tripwire will periodically recheck
the value of each binary file in its database. If any file has changed,
the wire is tripped and an alarm is signalled.
This system is
incredibly effective, because the first thing a hacker usually does when
they gain access to your system is replace important system files with
their own version. This is known as a 'rootkit', and it means that the
hacker can always access your system – even after you locate and update
the original 'back door' security problem.
There are various
tools that look for the tell-tale signature of a rootkit installation,
but Tripwire pre-empts these tools by catching changes to the file
system – hopefully before the rootkit can even be used. For this reason,
you can find Tripwire in the package repository of nearly every Linux
distribution we can think of. Just search for it and install.
Tripwire defence has been so successful that a proprietary company has
been launched on the back of the original Tripwire product; both are
confusingly called Tripwire. Thankfully, however, the opensource version
of the software is still popular, despite the fact that, like all Linux
security tools, it takes a considerable effort to get it working.
Most of that effort is to do with editing arcane configuration files.
Choosing Ubuntu or Debian can help with this, as both of these
distributions include a quick setup wizard when you install the
packages. We've used Ubuntu Hardy Heron in the example configuration
below. We've also provided the manual commands for configuration if
you're using a different distribution.
Make sure everything
that needs to be installed is installed. If you add more packages after
the Tripwire installation, you'll have to go through a rather convoluted
reconfiguration routine. For this reason, it's more straightforward to
install Tripwire after you've configured and set up the server exactly
as you need it.
Configuration
After installing the
Tripwire packages, you'll be presented with the Tripwire configuration
wizard. The first question asks whether you want to create or use your
site passkey. This is the unique encryption key that's used to generate
the checksum information for your files, and Tripwire uses two – one for
files that are only going to be used on the installation machine (such
as the Tripwire configuration files themselves), and another for files
that may be accessed and used on other machines across a network. The
next page of the wizard will ask you for these.
However, there
is a caveat. If someone else has a copy of the same keys, they can
potentially create files that appear authentic. There's a slight
security risk with keys generated by the Debian installer, so if you're
in any doubt about the security of your system, you should generate the
keys manually (see the next paragraph for how to do this). Otherwise,
continue with the next page of the wizard, enter long phrases that you
can easily remember for both configuration keys and let the set-up
wizard generate the configuration file.
To generate both the
local and server keys manually, open a terminal and switch to using the
System Administrator's account. Type the following (Ubuntu users should
precede both lines with 'sudo'):
twadmin -m G -S /etc/Tripwire/site.key
twadmin -m G -L /etc/Tripwire/ hostname-local.key
You should replace 'hostname' in the second command with your machine's
hostname. In Ubuntu, this is the word that comes after the 'username@'
symbol in the command line. In both cases, you'll be asked for a
passphrase to generate the key. You need to use these keys to encrypt
the two configuration files used by Tripwire, both of which reside in
the '/etc/Tripwire' directory in plain text – which is why they have the
'.txt' extension. Encrypt the first by typing the following command:
cd /etc/Tripwire
twadmin -m F -S site.key twcfg.txt
Enter pass phrase:
As you can see in the above commands, you will be asked for your
passkey, and you will need to enter the passphrase that you used to
generate the server-side key earlier. The second configuration file that
we need to encrypt is called 'twpol.txt' . This is Tripwire's policy
file, and it contains all of the policies and rules used by Tripwire to
govern its file protection. Debian/Ubuntu creates a default set of
policies that should be more than adequate for most installations. If
you take a look at the policies themselves, you will see small sections
of code that look like the example given below:
{
rulename = "Critical system boot files",
severity = $(SIG_HI)
}
{
/boot
/lib/modules
}
The syntax above is relatively straightforward, if a little verbose.
The section above is protecting critical system boot files, as explained
in the rule name. You can see which directories specifically in the
lower section.
The boot directory contains both Grub and the
Linux boot loader. A rootkit or trojan that changes any files here could
cause serious damage. The '/lib/modules' directory contains all the
kernel drivers for your system. A subtle change to the modules here
could cause all kinds of subtle and not so subtle havoc. For this
reason, both directories have been given a severity of SIG_HI, which is
the strongest possible signal from Tripwire that something is wrong.
Earlier on in the configuration file, SIG_HI is given a point score of
100. If you have directories and files that aren't part of a standard
Ubuntu installation, and these need to be protected, then you'll need to
create your own policies for those locations. After you've finished
looking at the policy file, it's time to encrypt it as we did the first
one. Just type the following:
twadmin -m P twpol.txt
You will be asked for your passphrase again before the encrypted file
can be generated. And that's all the configuration you need. The next
step is to type 'Tripwire --init' to start building the database from
the locations specified in your configuration file. The time this takes
is dependent on how many directories and files need to be scanned, but
expect to wait long enough for the kettle to boil and the tea to stew.
When you come back to the screen, you'll probably see some error
messages as Tripwire complains about directories specified in the
configuration file that don't exist. You can safely ignore these.
Tripwire is now ready to defend your system.
Testing your
current file system against the copy held in the Tripwire database is as
simple as typing 'Tripwire --check'. After a few minutes, Tripwire will
start to report any detected changes. As an experiment, try editing one
of the files covered by your policy.
You could add a new
group, for example, or change a user's password. Either of these actions
will change a configuration file, making it different from the one held
in the Tripwire database. The generated report will include a useful
table, so that you can see exactly what has changed and what kind of
severity the issue has raised. Below the table, the output goes into
greater detail. Here's a snippet from Tripwire's output if you change a
password:
Rule Name: Security Control (/etc/shadow)
Severity Level : 66
Modified:
"/etc/shadow"
You can see the rule name under which the password files fall under
(shadow is the encrypted file used to store passwords), and you can also
see the severity for the issue. At a security level of 66, it's less
severe than a change detected in the boot files and modules directories,
but it's still notable. Because the output from Tripwire is quite
detailed, you can decide for yourself the likelihood of a compromised
system. The output is stored in an encrypted form in the '/var/lib/
Tripwire/report' directory, and if you take a look at it, you can see a
file for every report you've run.
If you want to make any
discovered changes permanent and flag them as acceptable, type 'Tripwire
--update -r hostnamereport. twr', inserting the name of the report you
want to edit instead of our placeholder. This will decrypt the report's
contents into a Vim editing session (as set in one of the configuration
files). Instructions are embedded within the file, but you generally
just need to remove an 'x' from the files you want to update.
Quitting the editor will run the scan again, with your changes added.
With everything running correctly, you might want to schedule a regular
time interval for Tripwire checks. Running a check at least once every
24 hours is recommended, but this all depends on the vulnerability of
your system. If you know that your system has security issues, try
running Tripwire once every few hours. As long as you check the reports,
you can be completely certain that your system hasn't been compromised.
Update: removed incorrect space in wadmin -m G -S /etc/Tripwire/site.key. Apologies! - Ed.
How to Delete Multiple Friends on Facebook.Now Lets do it wit help of some Scripts
Software Requirements
FireFox 4 or later
Download
Grease Monkey Add On
Download
Start:
First Install FireFox
Then Download Grease Monkey Add On
Install add on and Restart Firefox
Then Grease Monkey Icon will be visible on firefox(If itz not active click icon)
Go to the download page(Click Install Script) and install the script
Install Script ( userscripts.org/scripts/show/
Now a new popup window will ask you to Install Script
Click Install
Installation Ends Here!
Begin Deletion Now!
Go to ur Facebook Profile -> Friends
Wait till script loads
Hover over one of ur friends name(Where Unfrend Really Comes)
Then Refresh the page
Now you will see Check Boxes aginst friends as seen bellow
Select the friends u want to Unfriend
Click on the Arrow Button
Select Highlight Only Button
Now it will begin Deletion
Click here to get Greasemonkey add on
FacebookDeletes for Greasemonkey
The making of a legal hacker
Not
everyone is cut out to be a security analyst; for one thing, it's not
easy to develop that level of professional paranoia. One of the most
famous security analysts, Bruce Schneier, tells a story about how as a
child he realised that a company that sold ant farms (and mailed out
tubes of live ants) could be used to send ants to anyone, anywhere.
That's a very different mindset to that of most of us, and essentially
it means looking at the world to see how it can be broken or subverted. A
security analyst would walk into a shop and think of three different
ways to rob it and another dozen to defraud it. It's a good job that
those minds are on the side of good and serve to help protect us against
their less than honourable counterparts.
Opportunities are everywhere. You might see a USB charging port at an
airport as a quick way of getting your phone or iPod charged between
flights, but a security analyst will be counting the connections in the
port and wondering just how much data someone could steal from an idle
phone using nothing more than a USB connection.
Penetration
tests capitalise on that security mindset. White hat hackers working for
security companies attempt to use their skills (and the tools that the
black hats use) in order to find ways into a business network.
If you're running a big network that carries data that needs to be
secure, you're likely to need certification from one of the big security
consultancies before you'll get any insurance – and that certification
is going to require one or more major penetration tests.
These
tests aren't simply restricted to the computer side of things. Network
security is about people, policy and technology. While you may be
thinking about encrypting your network traffic and using two-factor
authentication, your penetration testers may well be gaming your social
network, tracking down backdoors into your network through staff who
might have forgotten passwords one time too many and tailgating their
way into the office building.
The slightest crack in your
network's armour and all the passwords in the world are rendered next to
useless for keeping that precious data safe.
Subscribe to:
Posts (Atom)