-
July 13th, 2004, 12:48 PM
#1
Member
-
July 13th, 2004, 01:28 PM
#2
The basic answer to your question is that there's nothing you can do, for the simple reason that you don't have access to the server itself: it's NTL's responsibility to keep the server-software up to date, to patch it, to secure it...
I don't know if you want those pictures to be publicly accessible, but if you don't you might want look into .htaccess and .htpasswd to prevent unauthorized access to those files.
-
July 13th, 2004, 01:30 PM
#3
You don't have to secure that site as it hosted on your isp's server. Only if you want to host a site on your own computer you have to deal with security. Well secure coding is always important but this is clearly not an issue as the content is limited to html.
The above sentences are produced by the propaganda and indoctrination of people manipulating my mind since 1987, hence, I cannot be held responsible for this post\'s content - me
www.elhalf.com
-
July 13th, 2004, 01:49 PM
#4
Member
Negative, el-half,
Thanks very much for your replies. I guess as NTL will have total control over my site's security I will have to consider a few things. First I'll have to look for information on their track record security wise, and second if I want to take total control over the security aspect of my site it seems as though I will have to go the whole hog and look into hosting it myself.
As I don't know anything about hosting, am I best off just doing a google search to learn about what is involved ? Or are there any A/O tutorials/other info available that I could have a look at ?
-
July 13th, 2004, 01:59 PM
#5
There are different types of hosting you can choose from.
The cheapest is basicly the same as you have now. A hosting provider will supply you with some (limited) webspace. The provider will take care of securing the box. Some providers (with/out extra costs) will also supply you with a database backend (MySQL, MS-SQL etc) so you can create dynamic content.
The most expensive is dedicated hosting. With this you can rent a server or put up your own. Then you have total control over the security, content and configuration of the site and the server.
Oliver's Law:
Experience is something you don't get until just after you need it.
-
July 13th, 2004, 02:03 PM
#6
Here are some things you might want to consider:
- Is hosting it yourself worth it? Are you willing to sacrifice a machine, and bandwith?
- Do you think you could do a better job securing your server than the people at NTL do with their own servers?
- Since most (if not all) of your content is going to be HTML, there's no code to exploit.
- Are you willing to pay for a domain name? For a static IP? Are you willing to sacrifice your family's comfort by redirecting them from IP to IP? ...
It's not worth it at all, imo.
-
July 13th, 2004, 02:39 PM
#7
I want to take total control over the security aspect of my site it seems as though I will have to go the whole hog and look into hosting it myself.
Well let me tell you this it isn't an easy task. I have both hosted my own and used (still use) hosting.
I know how you feel, you want to start out doing everything youself. Well let me tell you alittle hint that will help you. First Rome wasn't built in a day and secondly get good at one thing before you try and move onto another aspect of computing. It is all about baby steps and building upon your growing knowledge.
- MilitantEidolon
Yeah thats right........I said It!
Ultimately everyone will have their own opinion--this is mine.
-
July 13th, 2004, 04:16 PM
#8
Member
Thanks again to everyone that has posted, just this quick series of discussions has already boosted my knowledge of the subject. I agree it appears the amount of effort involved in actually physically hosting my own site will be excessive as opposed to simply uploading files to webspace.
One comment that made my ears ***** up was this:
Originally posted here by el-half
Well secure coding is always important but this is clearly not an issue as the content is limited to html.
This leads me to a few more questions:
1) What represents "well secure coding" ?
2) What sort of site content would necessitate "well secure coding" ?
Cheers again everyone
Dom
-
July 14th, 2004, 04:17 PM
#9
Originally posted here by domtheboy
2) What sort of site content would necessitate "well secure coding" ?
Any site that uses one of the scripting languages (asp, php ie.) to serve dynamic content.
Especially if you use a database backend to collect/modify the data that makes up the dynamic content.
It's the one thing that bites nearly every newbie (no offence ) website developer.
Google for SQL-injection if you want to know more about it.
Oliver's Law:
Experience is something you don't get until just after you need it.
-
July 14th, 2004, 04:28 PM
#10
If there is no executable content on it, and no private data, your main concern should be local security on the machines you use to update it. It look like you have that sorted.
Once you start to use server-side stuff like PHP, then the interesting bit starts (as stated by other posters).
I don't believe Bolton is that sunny, BTW.
Slarty
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|