Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Why circumventing software activation is a bad idea if you don't know what you're doing!
- Here presented is a popular way to circumvent te activation procedures of Adobe CS 5.5
- However, sneaky little internet terrorists, modified the file and spread it with extra holes.
- # Copyright (c) 1993-2009 Microsoft Corp.
- #
- # This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
- #
- # This file contains the mappings of IP addresses to host names. Each
- # entry should be kept on an individual line. The IP address should
- # be placed in the first column followed by the corresponding host name.
- # The IP address and the host name should be separated by at least one
- # space.
- #
- # Additionally, comments (such as these) may be inserted on individual
- # lines or following the machine name denoted by a '#' symbol.
- #
- # For example:
- #
- # 102.54.94.97 rhino.acme.com # source server
- # 38.25.63.10 x.acme.com # x client host
- # localhost name resolution is handled within DNS itself.
- # 127.0.0.1 localhost
- # ::1 localhost
- 127.0.0.1 secure.tune-up.com
- 127.0.0.1 localhost
- 127.0.0.1 3dns.adobe.com
- 127.0.0.1 3dns-1.adobe.com
- 127.0.0.1 3dns-2.adobe.com
- 127.0.0.1 3dns-3.adobe.com
- 127.0.0.1 3dns-4.adobe.com
- 127.0.0.1 activate.adobe.com
- 127.0.0.1 activate-sea.adobe.com
- 127.0.0.1 activate-sea.adobe.com.* <-- Hello?! Wildcarding a domain on the suffix?! Insane!
- 127.0.0.1 activate-sjc0.adobe.com
- 127.0.0.1 activate.wip.adobe.com
- 127.0.0.1 activate.wip1.adobe.com
- 127.0.0.1 activate.wip2.adobe.com
- 127.0.0.1 activate.wip3.adobe.com
- 127.0.0.1 activate.wip4.adobe.com
- 127.0.0.1 adobe-dns.adobe.com
- 127.0.0.1 adobe-dns-1.adobe.com
- 127.0.0.1 adobe-dns-2.adobe.com
- 127.0.0.1 adobe-dns-3.adobe.com
- 127.0.0.1 adobe-dns-4.adobe.com
- 127.0.0.1 crl.verisign.net <------- NEVER blockout the CERTIFICATE REVOCATION LISTs People can read your e-mail and shop from your bankaccount.
- 127.0.0.1 CRL.VERISIGN.NET.* <---- Well, I guess you don't need to know when VeriSign Certificates have been compromised. This is a MITM-attack waiting to happen.
- 127.0.0.1 ood.opsource.net
- 127.0.0.1 209-34-83-73.ood.opsource.net
- 127.0.0.1 practivate.adobe
- 127.0.0.1 practivate.adobe.* <- Again, wildcarding ?!!
- 127.0.0.1 practivate.adobe.com
- 127.0.0.1 practivate.adobe.newoa
- 127.0.0.1 practivate.adobe.ntp <- This is no common TLD, it's a service. People can walk in and out.
- 127.0.0.1 practivate.adobe.ipp <- same as above
- 127.0.0.1 ereg.adobe.com
- 127.0.0.1 ereg.wip.adobe.com
- 127.0.0.1 ereg.wip1.adobe.com
- 127.0.0.1 ereg.wip2.adobe.com
- 127.0.0.1 ereg.wip3.adobe.com
- 127.0.0.1 ereg.wip4.adobe.com
- 127.0.0.1 wip.adobe.com
- 127.0.0.1 wip1.adobe.com
- 127.0.0.1 wip2.adobe.com
- 127.0.0.1 wip3.adobe.com
- 127.0.0.1 wip4.adobe.com
- 127.0.0.1 www.wip.adobe.com
- 127.0.0.1 www.wip1.adobe.com
- 127.0.0.1 www.wip2.adobe.com
- 127.0.0.1 www.wip3.adobe.com
- 127.0.0.1 www.wip4.adobe.com
- 127.0.0.1 wwis-dubc1-vip60.adobe.com
- 127.0.0.1 installer.nemetschek.net
- 127.0.0.1 piracy.nemetschek.net
- 127.0.0.1 secure.nemetschek.net
- 127.0.0.1 obdev.at
- -------------- Have fun putting up a campaign against these IP-adresses.-------------------
- 127.0.0.1 192.150.18.108 <- What's this? Are we whitelisting a bunch of IP's to come visit?
- 127.0.0.1 192.150.22.40<- What's this? Are we whitelisting a bunch of IP's to come visit?
- 127.0.0.1 192.150.14.69<- What's this? Are we whitelisting a bunch of IP's to come visit?
- 127.0.0.1 192.150.8.118<- What's this? Are we whitelisting a bunch of IP's to come visit?
- 127.0.0.1 192.150.8.100<- What's this? Are we whitelisting a bunch of IP's to come visit?
- 127.0.0.1 192.150.18.101<- What's this? Are we whitelisting a bunch of IP's to come visit?
- 127.0.0.1 192.168.112.207<- What's this? Are we whitelisting a local IP as wel, this get's easier
- 127.0.0.1 194.224.66.48<- What's this? Are we whitelisting a bunch of IP's to come visit?
- 127.0.0.1 199.7.52.190<- What's this? Are we whitelisting a bunch of IP's to come visit?
- 127.0.0.1 199.7.52.190:80<- What's this? Are we whitelisting a bunch of IP's to come visit?
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement