Hello,
Yes, I took the kdenetwork source, modified it, and built and tested kppp.
Of course, further testing wouldn't hurt, but there isn't anything in
these packaging changes that should break anything. Users who already
have kppp working, having edited /etc/ppp/options to set "noauth",
shoul
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, wha
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.
--
ciao, |
Marco | [6281 prochPlS76pE2]
Hello,
Well, no response from Marco yet. I've incorporated your suggestion,
however, and made "noauth" in /etc/ppp/peers/kppp-options commented out
by default. I've also documented this change.
While kppp will require root intervention to get "noauth", this is still
an improvement, in terms of
Hello,
A bunch of us are struggling with the issue of how to make KPPP work for
users with a minimum of configuration. One stumbling block is the need
for the "noauth" option to be set for KPPP to establish most connections.
Currently, we instruct the users to edit /etc/ppp/options and change
On Wednesday 05 May 2004 19:59, Christopher Martin wrote:
> Hello,
>
> To deal with the problems users are having configuring KPPP, I've put
> together some small patches (based on the ideas, not my own, discussed in
> Bug #126406) that should resolve these issues. The patches are attached
> to
Hello,
To deal with the problems users are having configuring KPPP, I've put
together some small patches (based on the ideas, not my own, discussed in
Bug #126406) that should resolve these issues. The patches are attached
to the e-mail I sent to [EMAIL PROTECTED], which for some reason
hasn't
7 matches
Mail list logo
