Curtis Rey wrote:
This is why, as a year old penguin myself, I desparately need an interface that will help me understand how to make a secure firewall without A) leaving blatant holes waiting to be exploited, and/or B) impliment rules that lock my network interface down so much I might as well unplug my RJ-45. Another thing this newbie would really appreciate is a realtime monitor that would give me information/alerts when something tries to send or receive when it wasn't initiated by me. Just a thought or two.
Cheers. Curtis
On Tuesday 05 June 2001 04:20 am, Oliver Maunder wrote:
Flaws in WinXP create a perfect environment for DoS attacks, according to article, which is also a fascinating look into the world of the hacker attacker.
Monday, June 04, 2001, 10:55:32 PM, S. Bulterman wrote:
SB> Read the article and thought it was a compliance issue with the Unix Socket SB> standaard. SB> Windows Me and lower were not 100% compliant with this standards, so no flooding SB> with SB> TCP SYN and TCP ACK. Windows 2000 and XP are now 100% compliant and are capable SB> of sending TCP SYN and TCP ACK attacks..........
Exactly - the quote was:
"When those insecure and maliciously potent Windows XP machines are mated to high-bandwidth Internet connections, we are going to experience an escalation of Internet terrorism the likes of which has never been seen before."
<flamebait> Surely positioning Linux as a consumer OS is going to cause exactly the same problem? Already, the worst DoS attacks come from unsecured Linux boxes with broadband connections. Surely this problem will get worse as consumer Linux usage increases. </flamebait>
Discuss ;-)
Olly
tail -f /var/log/messages tail -f /var/log/firewall ctr-c to exit tail -f Maybe setup snort and crontab to send you snort stuff. Hope that helps. Matt