[volunteers] server security - portscan results for svlug.org

Rick Moen rick at linuxmafia.com
Sun Dec 3 22:27:56 PST 2006


Alvin Oga wrote:

> so again, i'm asking..
> 
> - is there a security policy and faq about how the svlug.org machines
> will be maintained and backed up ??

Hey, three questions packed into one!  You're on a roll, Alvin.

FAQ:  There really can't be a FAQ, because there haven't been anything
even remotely like _frequently asked questions_, right?  Am I missing
something?  I don't think "frequently asked question" is synonymous with
"Alvin has asked this idle question, of nobody in particular, twice."

Backup:  Tentatively[0], we're going to have a backup-target machine
inside Via.net that has rotated backups sets network-delivered from
others.  Backups will be cron-driven, with transport over SSH using a
process-locked keypair[1].  

The command used to pick up the files on the source host really doesn't
matter a lot.  Here are examples of suitable command strings that could
be written into the cronjob script:

 (sleep 10; cd olddirectory && tar Sczpf - . ) | ssh username at newhost \ 
 'cd newdirectory && tar Sxvzpf -'

 rsync -e ssh -avz olddirectory username at newhost:newdirectory

We're in the middle of preparing a replacement machine that will be a
functional exact replacement for the current SVLUG host[2], so we'll then
be able to turn around and redeploy the current host (with some of our
spare hard drives) as a backup target.  The backup target will of course
be more heavily protected than are our other hosts.

Security policy:  Hey, you don't ask for _much_, do you?  A reasonably
_comprehensive_ written security policy would take a long time to write
and debug, and I'm more than a bit busy at the moment.  It would
encompass prevention, detection, damage reduction, defence in depth,
hardening, identification of threats, and recovery.  It would discuss
security auditing, the design and testing of backup systems, automatic
and manual log analysis, handling of dialup access, physical security
for the network, and disaster recovery and costing, among other things.

That would be basically what we call "network consulting".  If I were a
cynic, I'd suspect you of wanting me to tutor you for free on that
subject -- and, moreover, to provide you with a text.

So, anyway, what exactly do you want, Alvin, that I can reasonably write
in some short period of time, that would have some near-term utility,
and that is more important than other crucial tasks I'm spending time
on?


>> - We made an informed decision to reverse a small number of recent
>> administrative changes that were made to the server, specifically in
>> the hosts.allow and hosts.deny files.
>
> since backups used to run across NFS w/ ssh .. 
> and that nfs is now removed, i assume you guyz have another
> plan for backups of the server

Hey, you're pretty smart!

> nmap is mostly useless in my view.

Your view is duly noted and given all due consideration.

> host.deny should always have by default to disallow everything ( all:
> all )

Your view is duly noted and given all due consideration.



[0] That word reflects very little uncertainty, but rather mostly the
fact that the machine is still being constructed, and not yet deployed.

[1] http://linuxmafia.com/faq/Security/ssh-publickey-process.html

[2] Except with much better hardware and maintainable software.





More information about the volunteers mailing list