master password gsoc project

[Felipe Contreras]

2008/5/9 Richard Laager <rlaager at wiktel.com>:
> On Fri, 2008-05-09 at 01:25 +0200, Vivien Bernet-Rollande wrote:
>>  - secure memory handling
>
> This one is going to be tricky to handle properly. And frankly, I'm not
> sure it's that big of a deal. I would focus on other goals first.
>
>> The modifications to libpurple would be :
>>  - register used signals on startup
>>  - when a pass is needed, emit signal, if no reply, use "normal" prompt
>>  - when a pass is stored, emit signal, get a return value, and if no
>> one wants it, put it in xml
>
> Using signals is one way to do it. Another would be to implement it like
> logging (and our SSL support as well): The core would have pluggable
> password storage back-ends. It would also provide one such back-end
> (which would use plain-text in accounts.xml).
>
> Gary, Sadrul, etc.: As far as GObjectification goes, would it be better
> for this feature to use signals or a struct with function callbacks?

I don't think GObject's signals are meant to reply.

Best regards.

-- 
Felipe Contreras