Hello,
Thanks for taking the time to look into this. But let's assume that in
immediate future we can't change kppp that drastically - all we can do
are packaging tricks to try to get it to work, with reasonable security
and a minimum of user configuration as root.
Given these limitations, what do you think of the patches posted before?
Is the idea of an /etc/ppp/peers/kppp-options containing "noauth" or
"#noauth" reasonable? Is there some better way, not requiring users to
change config files as root, again without re-writing kppp itself?
Thanks,
Christopher Martin
On May 14, 2004 10:06, Marco d'Itri wrote:
> kppp should probably write a complete peers file with everything needed
> to call the peer.
>
> It should also use the passwordfd pluging instead of messing with
> {pap,chap}-secrets.
