RE: Securing a webserver through reverse proxy?

[Alisson Leite de Morais Veras]

Hi there,

continuing on this thread

That's a implementation I was wondering to do, but interacting with SNORT,
to make changes in the destination address (squid or iptables routing). If
an attack were detected, it would redirect the traffick to another server or
some king of honneypot.

Anybody know if it's OK? Is it too hard to do?

Thanks
Alisson Leite de Morais Veras
Sao Paulo - Brazil

Windows x Linux

[Alisson Leite De Morais Veras]

Hi guys,

I'm doing a research about safety/security of Windows and Linux

I don't want to make a mistake (like count the same bug in several 
distributions) so, I decided to make the Linux analysis against only on 
linux distribution, RedHat Linux.

I need some information like these to complete my work:

MS02-017: (Microsoft Security Bulletin)
 Year: 2002
 Bulletin: 017
 Date: MM/DD/2002

Okay, I can find these in MIcrosoft Home-Page, but there is a very 
importante information they don't provide The date the bug was 
discovered. It's very important to know the frequency of bugs and the 
time they spend to release a patch to the problem. (I'm sure Linux is 
the winner here... so, this is the most important information I have to 
count!)

RHSA-2002:035-18 (RedHat Security Advisor)
 Year: 2002
 Bulletin: x (?)
 Date: MM/DD/2002

In RedHat, I have the same problem to know that information and those 
dates...

I was thinking in follow threads in a recognized site in the community, 
like security focus, but I'm having problems to track the advisores...

Is there any place where I can find a relation of bug discovered - 
bug advisor?

Anyone can help me?

Any help will be very appreciated...

Alisson