Alan Cox wrote: > There have been at least five holes found in pile that _could_ have been > [speech] > safe is the day you end up hurt. Your specific example of an executable (windows) attachment, not buffer overflows, etc. what what I was replying to. In general, you are correct. Now, how about including that procfs cleanup patch that I sent, and maybe the 64-bit printk patch? :) -M - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: iptables: "stateful inspection?&... Michael Rothwell
- Re: iptables: "stateful inspecti... Michael H. Warfield
- Re: iptables: "stateful ins... Michael H. Warfield
- Re: iptables: "stateful inspection?" Michael H. Warfield
- Re: iptables: "stateful inspection?" Alan Cox
- Re: iptables: "stateful inspection?"... Michael Rothwell
- Re: iptables: "stateful inspection?&... Dax Kelson
- Re: iptables: "stateful inspection?&... Alan Cox
- Laptop system clock slow after suspen... Ian Stirling
- Re: Laptop system clock slow aft... Keith Owens
- Re: iptables: "stateful inspecti... Michael Rothwell
- Re: iptables: "stateful inspection?" George
- Re: iptables: "stateful inspection?" Michael Rothwell

