pppoe-server compiled with incorrect path to pppd
Bug #72967 reported by
Net Venture
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rp-pppoe (Debian) |
Fix Released
|
Unknown
|
|||
| rp-pppoe (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: pppoe
SUMMARY: pppoe-server, which is part of the pppoe package tries to invoke /pppd instead of /usr/sbin/pppd.
BACKGROUND:
When it receives an auth request from a pppoe client, the pppoe-server daemon needs to invoke /usr/sbin/pppd.
After the daemon is started, it chdir()'s to "/" and on receiving an auth request, it invokes the "pppd" binary from current dir (which is /). It should actually invoke /usr/sbin/pppd instead.
A bug has been filed in debian but has been left unattended for long. This probably effects dapper too. This forum thread describes one practical instance of this problem:
http://
Debian Bug:
http://
| Changed in rp-pppoe: | |
| status: | Unknown → Unconfirmed |
| Changed in rp-pppoe: | |
| status: | Unconfirmed → Fix Released |
Revision history for this message
| Kai Kasurinen (kai-kasurinen) wrote | #1 |
| Changed in rp-pppoe: | |
| status: | Unconfirmed → Fix Released |
To post a comment you must log in.
Thanks for the bug report.
I'm closing this bug because it has been fixed in Feisty.
rp-pppoe (3.8-1.1) unstable; urgency=high
* Non-maintainer upload.
* Hardcode path to pppd so that pppoe works even when there is no
pppd installed in the compilation chroot. Closes: #380584