Re: irq 11: nobody cared
Jeff Garzik wrote: Read REPORTING-BUGS. We can't do much of anything with this report. Tell us what's on irq 11, for starters Righto. While doing that I found that my udev is out of date for the 2.6.13-rc6 kernel. Is there a chance that upgrading will kill my current 2.6.7-rc3 setup? If not I'll go ahead and upgrade that and run some more tests before posting a full report. n - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
irq 11: nobody cared
Hail, I posted a report a while back, no answer. Who should I be talking to wrt to the irq 11: nobody cared issue? I'm happy to provide as much info as possible but need to know what info is required. I'm happily running 2.6.7, tried the latest and greatest (2.6.12) and found the problem, then started by looking at 2.6.8 and found the problem there too. It happens on boot, is a showstopper and I'm wondering what, if anything useful I can provide you guys. Throw me a bone... Nige - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
irq 11: nobody cared
Hail, I posted a report a while back, no answer. Who should I be talking to wrt to the irq 11: nobody cared issue? I'm happy to provide as much info as possible but need to know what info is required. I'm happily running 2.6.7, tried the latest and greatest (2.6.12) and found the problem, then started by looking at 2.6.8 and found the problem there too. It happens on boot, is a showstopper and I'm wondering what, if anything useful I can provide you guys. Throw me a bone... Nige - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: irq 11: nobody cared
Jeff Garzik wrote: Read REPORTING-BUGS. We can't do much of anything with this report. Tell us what's on irq 11, for starters Righto. While doing that I found that my udev is out of date for the 2.6.13-rc6 kernel. Is there a chance that upgrading will kill my current 2.6.7-rc3 setup? If not I'll go ahead and upgrade that and run some more tests before posting a full report. n - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.12 Boot Hang Disabled IRQ 11
Hi all, I downloaded and compiled 2.6.12 yesterday, I am currently running 2.6.7-rc3. The boot eventually hangs (irq 11, nobody cared) but since the disks aren't mounted yet I have no dmesg output. So, before I can provide a decent report I need some way of getting this output, is there a better way than simply copying it down from the terminal? Ta, n - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.12 Boot Hang Disabled IRQ 11
Hi all, I downloaded and compiled 2.6.12 yesterday, I am currently running 2.6.7-rc3. The boot eventually hangs (irq 11, nobody cared) but since the disks aren't mounted yet I have no dmesg output. So, before I can provide a decent report I need some way of getting this output, is there a better way than simply copying it down from the terminal? Ta, n - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Open source firewalls
Vinay Venkataraghavan wrote: Hello, Hello, *devil's advocate hat on* I have implemented an bare bones Intrusion detection system that currently detects scans like open, bouce, half open etc and a host of other tcp scans. As an aside, why, we have snort? I would like to develop this into a full blown IDS which is capable of detecting buffer overflow attacks, sql injection etc. I know how to implement buffer overflow attacks. But how would an intrusion detection system detect a buffer overflow attack. My question is at the layer that the intrusion detection system operates, how will it know that a particular string for exmaple is liable to overflow a vulnerable buffer. Erm, if you know how some buffer overflow attacks work then surely the answer is "it depends on the application". To tell if an application is vulnerable you would have to audit it in some manner. Either by checking the source or doing some black-box testing on it. Even if you did have a great big database of apps and had identifed which of them had possible vulnerabilities it would be easier to simply fix them rather than get an external system to disallow such inputs. And not forgetting that you would have to have some way for your IDS to tell what app was running behind a specific port. Thought about that yet? Are there other open source firewall implementations other than snort? Snort isn't a firewall. Don't mix apples and oranges. Snort is an IDS. The current de-facto "firewall" for linux is the iptables suite. Cheers, n - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Open source firewalls
Vinay Venkataraghavan wrote: Hello, Hello, *devil's advocate hat on* I have implemented an bare bones Intrusion detection system that currently detects scans like open, bouce, half open etc and a host of other tcp scans. As an aside, why, we have snort? I would like to develop this into a full blown IDS which is capable of detecting buffer overflow attacks, sql injection etc. I know how to implement buffer overflow attacks. But how would an intrusion detection system detect a buffer overflow attack. My question is at the layer that the intrusion detection system operates, how will it know that a particular string for exmaple is liable to overflow a vulnerable buffer. Erm, if you know how some buffer overflow attacks work then surely the answer is it depends on the application. To tell if an application is vulnerable you would have to audit it in some manner. Either by checking the source or doing some black-box testing on it. Even if you did have a great big database of apps and had identifed which of them had possible vulnerabilities it would be easier to simply fix them rather than get an external system to disallow such inputs. And not forgetting that you would have to have some way for your IDS to tell what app was running behind a specific port. Thought about that yet? Are there other open source firewall implementations other than snort? Snort isn't a firewall. Don't mix apples and oranges. Snort is an IDS. The current de-facto firewall for linux is the iptables suite. Cheers, n - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
