Date: Sat, 26 Oct 2002 03:02:00 -0700 From: Maxime Henrion <mux@freebsd.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Brooks Davis <brooks@one-eyed-alien.net>, Bakul Shah <bakul@bitblocks.com>, freebsd-current@FreeBSD.ORG Subject: Re: pppd not working on latest current 2002-10-20 Message-ID: <20021026100200.GT26605@elvis.mu.org> In-Reply-To: <3DB9F885.D0A59E87@mindspring.com> References: <20021025152221.A8479@Odin.AC.HMC.Edu> <200210260034.UAA03676@tonnant.cnchost.com> <20021025175921.A2761@Odin.AC.HMC.Edu> <3DB9F885.D0A59E87@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert wrote: > Brooks Davis wrote: > > This isn't going to have an effect on the ability to use kernel ppp for > > other things. The tty orientation of pppd and the outdated, unmodular > > design on ppp(4) have taken care of that. This patch gives people > > the functionality they want (pppd just working) without any major > > entanglements (the whole function is <20 lines). If someone > > wants to make pppd work on arbitrary devices we can deal with that when > > it happens and I frankly doubt it's ever going to since we've got > > netgraph to do that with. > > Depending on the value of "sysctl kern.module_path", if the "if_ppp" > module does not exist, and one of the path components is writeable, > then this would permit you to abuse the pppd to load arbitrary modules > into the kernel. > > So I understand Bakul's complaint. > > But by the same token, "mount" and "ifconfig" have the same problems; > on the other hand, unlike pppd, they are not suid root. Just for the record, mount(8) does not load any kernel module anymore. The kernel will attempt to load the corresponding filesystem module at mount(2) time if it does not find support for it though. Maxime To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021026100200.GT26605>