>| But are we saying that we have no >| one in this list who is capable of securing a simple dynamic site? >\--
>... with time to promptly respond to queries and maintain it, because >they are busy with a day-job? What do you propose as the plan of action for tracking apache vulnerabilities, OS vulnerabilities and so on? Are you saying that there is going to be NO vulnerabilities in the system if you remove MySQL and PHP (if you are using a LAMP stack and running a PHP-based opensource CMS)? If you aren't willing to get someone to at least look at the website occasionally, then you shouldn't be getting into hosting anything - static or not. Also, what makes you think it is dramatically less time consuming to maintain a static html website where you have to edit links manually, archive content manually and so on? Do you think it takes a lot less effort to track changes in subversion, deciding what is moved over to the production site, managing branches, managing merges, managing user rights to different parts of the website, applying patches and then deciding on what content is moved *manually* to archives and so on? And at the end of the day you will have a website which does not even support searches? If you think that is an advancement, I don't know what else to say. >... provided you have a *dedicated* list of people who can maintain >it? There has been many a time when I couldn't show the URL of ILUG-C >when talking to students because the website has been filled with >spam, or the site itself has been down. >We can do better! How is this a fault of the software? What is preventing the maintainers from setting up basic moderation for comments? Would that require huge effort? Regards, Prem _______________________________________________ To unsubscribe, email [email protected] with "unsubscribe <password> <address>" in the subject or body of the message. http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
