But of course, if your web server isn't a) configured to serve PHP content through a PHP interpreter, or b) configured to do a) on files called "*.php" in your webspace root, you will just get the code of the page.
In other words, you still need a webserver capable of serving PHP.
Whether you'd want to, of course, is a different story.
NB - this isn't an anti-PHP point, more of a "run a webserver on your home PC which is accessible by the world and you have a whole new set of security problems to think about" kind of point.
Possibly the worst thing for the Internet is for a bunch of people without a clue to run their own insecure webservers. If a hacker can buffer-overflow your server and exploit your machine to their own ends, it's an easy zombie to use for attacking other people.
> Whether you'd want to, of course, is a different story.
No offense taken at all -- it's a very valid point you're making. I've run a webserver off my PC in the past, and the logs were always full of script kiddiez and their (attempted) drive-by bombings.
I tend to forget / conveniently ignore that the ability to be on the 'net doesn't necessarily give you any understanding of the risks.
Good idea. I think I will create a podcast of our "ausrufezeichen" readings.
The PHP thing might indeed be a problem. But there are free webproviders who offer unlimited webspace and PHP and mySQL. Only drawback is filesize restrictions. But ín case of literature readings it doesn't really matter,as you can just chop up the MP3s and podcast them in sequence...
Comments 55
In other words, you still need a webserver capable of serving PHP.
Reply
Hell, you can even get PHP running on a Windows install of Apache and serve it up straight from your PC.
Reply
NB - this isn't an anti-PHP point, more of a "run a webserver on your home PC which is accessible by the world and you have a whole new set of security problems to think about" kind of point.
Possibly the worst thing for the Internet is for a bunch of people without a clue to run their own insecure webservers. If a hacker can buffer-overflow your server and exploit your machine to their own ends, it's an easy zombie to use for attacking other people.
Reply
No offense taken at all -- it's a very valid point you're making. I've run a webserver off my PC in the past, and the logs were always full of script kiddiez and their (attempted) drive-by bombings.
I tend to forget / conveniently ignore that the ability to be on the 'net doesn't necessarily give you any understanding of the risks.
Reply
For those looking for more info, it can be found at: http://ipodder.sourceforge.net/index.php
Thanks for mentioning all this, Mistah Ellis. It fits ever-so-nicely into a proto-idea of mine.
Reply
Reply
Reply
The PHP thing might indeed be a problem. But there are free webproviders who offer unlimited webspace and PHP and mySQL. Only drawback is filesize restrictions. But ín case of literature readings it doesn't really matter,as you can just chop up the MP3s and podcast them in sequence...
Reply
Leave a comment