Linked by Thom Holwerda on Sun 15th Jan 2006 23:29 UTC
Internet & Networking "One of the biggest issues involved with becoming a web publisher is the question of hosting. With an internet clogged with false hosting review sites, hosting companies trying to rip you off, and hosting companies run by 14 year olds, the majority of web publishers are at the mercy of random chance when it comes to finding a quality host. To solve this huge problem and to grant freedom to all, we have come up with 75 extremely specific steps that will get you up and running with a *nix box (running FreeBSD), along with the most recent versions of Apache, Perl, PHP, and MySQL."
Thread beginning with comment 86086
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Slightly odd article I thought
by superbenk on Mon 16th Jan 2006 02:08 UTC in reply to "Slightly odd article I thought"
superbenk
Member since:
2005-12-04

That and the fact that it's often illegal according to the End User Licsense Agreement you sign with your broadband provider. If you upgrade to a business account you are probably *legal* but even then some agreements don't allow you to run a web server yourself.

Reply Parent Bookmark Score: 2

ariel Member since:
2005-07-06

Right... but some ISP just block the http port (80), thats the way they protect the End User License Agreement.

Reply Parent Bookmark Score: 1

howard Member since:
2006-01-08

Violating the your provider's Terms of Service (not EULA, that applies to software, not services) is not illegal. They may cancel your account and refuse to do business with you, but that is a far cry from the police hauling you off to jail.

If you don't understand the difference between laws and contracts you probably shouldn't be publishing anything, anyway.

Changing topics, I agree with the other posters that running a web server is easy. Running a server securely is more challenging. The article enabled SSH, but failed to disable root logins, failed to disable passwords, failed to describe setting up key pairs, and that's just for remote access. Where's the logging? The firewall setup? And so on...

Reply Parent Bookmark Score: 3

superbenk Member since:
2005-12-04

Ok, I'll concede that EULA was the wrong term, but come on! Just because you might not get caught doesn't make it right. The practice of knowingly breaking rules to which you agreed to operate by should not be condoned and is very much the reason why providers start making life so miserable by locking things down. I think it's one thing to have a web server for *personal* access only on a home ISP account that forbids web services for commercial purposes, but that's not what's being talked about here. The article specifically talks about being a web developer and having a secure space to host sites which implies (to me) public access sites. If I misread, I apologize.

I definately wouldn't judge anyone for doing this, but I don't think it should be publically condoned. And people wonder why ISPs start blocking ports! It's because people abuse them.

Reply Parent Bookmark Score: 1