[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [PATCH] kppp without suid
From:       Harri Porten <porten () froglogic ! com>
Date:       2009-05-23 12:49:47
Message-ID: Pine.LNX.4.64.0905231443320.6894 () greco ! froglogic ! com
[Download RAW message or body]

Hello Thadeu,

thanks for getting involved. Maybe I can soon pass on the baton of 
maintainership to someone else? :)

On Fri, 22 May 2009, Thadeu Lima de Souza Cascardo wrote:

> I've hit a problem recently when using an installation of kppp in SuSE.
> Instead of using some recommended solutions, like setting it suid or
> giving the required permissions into /etc/ppp/ directory. Setting the
> password manually into chap.secrets and pap.secrets was out of the
> question, since this should be easy to the end user.
>
> So, I decided to use the passwordfd plugin. First, I realized it was not
> possible to establish a connection but kppp did not tell me so. So, the
> fist patch I prepared returned an error when it was not possible to
> write into the mentioned files. The only drawback I see for this patch
> is that, in the case the user has written the files himself, kppp will
> not call pppd, but give him an error instead. The solution would be to
> let the user tell kppp he has already set the password. If that's
> required, I may prepare this patch too.

Nevertheless the patch makes sense. I marked it as reviewed. Only time 
will tell whether such an option is required. Might have to wait until the 
first distributions ship an installation (with their specific security and 
network setup).

I cannot say anything about the passwordfd related code, yet. It's a 
feature that didn't exist when I wrote the original code.

> The following bugs and reviewer requests were opened/submitted to (I've
> picked up myself as reviewer since I could not find porten there):

I've registered such an account now. Thanks for the reminder.

Harri.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]