Freelancers Network
 
skill list top cap
Homepage
Join the Freelancer's Network
Update your details
Find a freelancer
Post a project
Find a project
Projects Archive
Post a job
Find a job
Jobs Archive
See Dan's Pages
See Andy's Pages
Link to this site
Resources
Join/Leave Forum
Forum Messages
+Additions+ Adverts
Advertising
Contact Us
Subscribe to our newsletter - enter your email address and hit return
Freelancers.net is owned and operated by Andy Stowell and Dan Winchester
skill list end cap
guru web hostcom

Find me again on Freelancers.net

Re: FN-FORUM: secure sites, encryption etc

date posted 3rd August 2004 18:49

On Tuesday 03 Aug 2004 2:15 pm, nick b wrote:
> nick b wrote:
> > anyone done much work on secure websites - that hold sensitive
> > information? eg government / health / financial / military. I'm

I sysadmin one that handles credit card details - and that's good enough=20
reason to take security very seriously. No way would I call myself an ex=
pert,
but I'll share what I can.

> > looking for a few pointers / tips on best practices, what can be done
> > to lock down and encrypt at a file / database level, probably on a ph=
p
> > & *nix shared or dedicated server environment.

Shared? Secure? Not in the same sentence, or even paragraph, please.

> anyone? please? or perhaps some good books to read about server
> security, file / db encryption - that kind of stuff...

The basic server checklist is to install a firewall, only open up ports t=
hat=20
you absolutely need, and only turn on the services that you absolutely=20
need. Then keep all the stuff that you are running patched and up to=20
date. Don't run BIND if you can possibly help it. Your minimal list of=20
open ports / services is 22 (for SSH), 80 and 443. Use SSH version
2, disallow root login, only allow one username to SSH in, use secure
passwords that you keep rotating. Never login from anything but a=20
system that you keep as secure as the server itself. (That means=20
never ever logging in from a mates Windows box).

Oh, and consider using OpenBSD.

That should be enough for the list's sysadmins to start pointing out=20
where I'm wrong...

comp.risks is good reading. www.catless.ncl.ac.uk has an archive.

It's often said that the best way to prevent hacking is to understand how=
=20
it's done. "Hack Attacks Revealed" & "Hacking Linux Exposed" are books t=
hat
come recommended although I've not read either.

Have you got a specific problem or are you just doing research out of
interest?



Messages by Day
August 31st 2004
August 30th 2004
August 29th 2004
August 28th 2004
August 27th 2004
August 26th 2004
August 25th 2004
August 24th 2004
August 23rd 2004
August 22nd 2004
August 21st 2004
August 20th 2004
August 19th 2004
August 18th 2004
August 17th 2004
August 16th 2004
August 15th 2004
August 14th 2004
August 13th 2004
August 12th 2004
August 11th 2004
August 10th 2004
August 9th 2004
August 8th 2004
August 7th 2004
August 6th 2004
August 5th 2004
August 4th 2004
August 3rd 2004
August 2nd 2004
August 1st 2004


Messages by Month
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004


Messages by Year
2008
2007
2006
2005
2004
2003
2002
2001
2000