Localhost question

blaisen6

New Member
I know you can install on localhost, but won't Jelsoft/PirateReports warn you for installing a nulled copy on it?

I've never done it myself, but anyone here ever done so?

Would the .htaccess trick mentioned in another thread stop them or not?

Just posting this out of interest and curiosity, nothign more! ;)
 
localhost is like your own server. Of course they will, well if they find it anyway. but if you have an offshore host (yey me :) ) then they can't stop u :)

Never seen an .htaccess trick.

Hope this is what u were looking for.
 
micky13 said:
localhost is like your own server. Of course they will, well if they find it anyway. but if you have an offshore host (yey me :) ) then they can't stop u :)

Never seen an .htaccess trick.

Hope this is what u were looking for.

What if the localhost is not accessible from the Internet due to another server on the same IP address (it does happen!) but you can access it on your computer only? Surely they wouldn't find you, theoretically?

As for the .htaccess trick, see http://www.vbteam.info/how/18176-protecting-yourself-jelsoft.html

One question, as for offshore hosts, where are there good free ones??

Not that I'm advocating this, just wondering about the theory of it all.
 
Localhost is usually the "internal" name of the server and its IP address is usually 127.0.0.1

THAT is NOT the address that Jelsoft sees. They see the PUBLIC Domain address. The callbacks tell Jelsoft what the Domain Name and IP is for the PUBLIC Internet address that is being used on the Internet. Even if the callbacks reported localhost or 127.0.0.1 to Jelsoft, it is meaningless and can not be traced to a real IP address on the Internet, same thing with IP addresses inside and Intranet behind a firewall. Almost ALL intranets have the same "private" IP addresses, like 192.168.1.x. These addresses are not allowed on the real Internet usually and if they accidentally or deliberately get put out on the public internet, the either don't work or wreak havoc and get shutdown usually. If you install ANY version of vBulletin on a private intranet behind a firewall or router like many home systems have, none of the computers inside that router are visible to the internet directly including vBulletin installations to anyone in the public internet. The only reason that makes sense is if you are running a private forum inside a firewall for a specific reason/group or you are using it to do testing and development on vBulletin or any other software for that matter that contains callbacks and license checks.

For example you can install Apache Server on your local system behind a firewall/router and ANY software that you have installed on your live site and it will work correctly as a local install that can not be seen from the Internet but will run just like it runs on the public server so its ideal for doing testing and development with out the risk of taking down your main site.

Aside from the fact that Jelsoft is mega - paranoid (for good reason) about people running nulled versions of their software, they are not nice people either so you should understand that if you install vBulletin on the internet and its not licensed, you run a risk of them finding out about your site and coming down with some ferocity like killing a fly with a sledgehammer. They have no manners and are not good guys by any means so expect that they will totally suck if they catch you.
 
Thanks for the clarification.

I'd never install an unlicensed version on the Internet anyway; but software piracy is a big issue, and controversial to say the least. However, it doesn't stop some people.

As for my XAMPP, it's not publically accessible due to it being on 192.168.2.104 - I use this to test out my PHP scripts and CMS scripts I download to test safely in a development environment.

The public IP runs a Linux server, so the external IP address wouldn't see the Apache/XAMPP server anyway. It just redirects to a router's login page at the public IP level.

Hope this clarifies it!
 
Back
Top