lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 28 Feb 2008 08:19:45 -0800
From:	"Kevin Lloyd" <>
To:	"James Chapman" <>,
	"Dan Williams" <>
Cc:	<>
Subject: RE: Network device driver with PPP

> That seems quite icky to do all in kernel space and a pile of code
> running in the kernel.  What's so wrong with userspace?  Don't you
> to push values to the driver like username/password and get IP config
> out of it (which would involve userspace anyway)?  It just seems like
> there's a different solution to your actual problem here than stuff
> off pppd into kernel space.

Actually we provide a method for the driver to obtain the
username/password information needed for the CHAP authentication so in
theory the driver has the information needed to create the connection.
I'm not sure how it would go about setting the DNS and IP addresses, but
that's a separate issue further down the road.

I understand that typical implementation is to deal with ppp
negotiations in the userspace however are there no devices that have
attempted this in the kernel space / no kernel space modules to aid with
this? Just trying to do a full investigation of all available options,
even if they aren't the best ones.
If not, is there a method for the network driver to launch pppd with a
given set of parameters (not using udev) since the driver would be
determining username/password runtime.

Thanks your help,
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists