Package: ppp Version: 2.4.4rel-10.1 Severity: important In a default out of the box setup (which didnt autoinstall gnomeppp, had to manually add it, but that's a different bug..) auth_required = 1 seems to be set in my case as well. This is a very virgin system so I am sure it's not from me messing around deep in config files.
Anyone who is wired to a network already will confusingly not be able to use PPP at all. This is a more serious bug than normal priority. The person who was actually using this box expert and proclaimed at me "told you linux doesnt work out of the box for a regular user.". Took me (an 'expert') about 10 minutes to figure out how to solve this (force noauth in peer conf, and read about this bug report). Nigh impossible for an unsophisticated user. Not sure of the rationale behind the code as it is now - most ppp client boxen will have ip forwarding off (laptop/desktop, etc), so I dont see how routing packets through to an existing default route would be a common risk requiring this protection. If there's a default route already AND ip forwarding is on, perhaps a warning should be raised to the user - but if ip forwarding IS on, then we should assume a sophisticated user and merely log a warning to syslog (and not construct hooks to issue a dialog box or something else to warn the user). Sophisticated users can then firewall or turn off noauth defaults in PPP or the like to limit access between the networks. Unless Im not grokking something here... /kc -- Ken Chase - k...@heavycomputing.ca - 416 897 6284 Heavy Computing - Clueful Server Colocation at 151 Front St. W Toronto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
