Messages in this thread | | | Date | Thu, 30 Oct 1997 23:49:38 -0500 (EST) | From | linux kernel account <> | Subject | Re: Linux Kernels |
| |
Theres a solotion, it's userspace, I know what it is but I'm gonna whine on the kernels list insted..
Whilst I post as root and complane about security.
Not to burst your buble, but thats userspace and it needs no kernel changes..
On Thu, 30 Oct 1997, eraserX wrote:
> > Hi, > I'm new to kernel hacking, but not to linux. I personally feel linux > kernels could be much improved, i would like to do so, but i am not > exactly any good at .c programming. I have only really used linux 2.0.30 > since that is the only version that seems to be stable. I feel there is a > lack of networking options in the kernel. I want a kernel version that has > many networking options, such as improved logging, better protect again > certain denial of service attacks. (yes i know about ipfwadm, but i dont > like using it). Also, about ipfwadm, i think linux kernel's should come > with their own ipfwadm type program, cept its much easier to use. I'd > prefer having a /etc/packet.deny file kinda like login.access, like: > <+/->:<icmp/udp/tcp/ALL/etc>:<ip address/ALL>:<port/ALL> . > Something like that, it looks similar to the syntax of ipfwadm, but I feel > that this method would be 90 times easier then ipfwadm with the 300 diff > -options and its much easier to access/change the list then ipfwadm. I > think the program should be run like inetd.conf, where u need to kill -HUP > <whatever ps> to refresh it. > I'd just like something similar or better then this implemented in > an upcoming *stable* kernel version. Send me your comments/suggestions... > > | Slackware __ 3.2 > | / / __ _ _ _ _ __ __ > eraserX | / /__ / / / \// //_// \ \/ / > (mikec@shaw.wave.ca) | /____/ /_/ /_/\/ /___/ /_/\_\ > | ...because win95 causes impotence... > >
| |