On 02/04/13 13:18, [email protected] wrote: > Hi GNOME community, > > I'm part of the people developing the live system called Tails [1]. > Tails has a strong focus on privacy, anonymity, encryption, etc. and of > course includes GNOME and Seahorse. > > We are now preparing a bounties program to help upstream developers work > on important bugs or interesting features for Tails. And we would like > to propose a bounty opportunity for Seahorse. > > We are still in the process of deciding which bounties we can fund > within our budget. So it is only a proposal and there is no amount of > money associated to it yet. If any of you is interested, please send > an email to me or [email protected] and include: > > - A short intro to who you are and the work you've already done in > Seahorse. > - A estimate workload to fulfill the task. > - A budget and calendar proposal. > > Keep in mind that your estimates should include coding, review, > debugging and documentation. Stef Walter from Seahorse volunteered to > support and mentor people working on this. > > SSH Keys in Seahorse > ==================== > > The import of SSH keys in Seahorse doesn't work. > > That's GNOME bug #550736, and still holds on Fedora 18 Live: > > - Importing a SSH public key returns: "Cannot display a file of this > type." error message. > - Importing a SSH private key returns: "No user has logged in." after > being asked for the passphrase and a label. > > https://bugzilla.gnome.org/show_bug.cgi?id=550736 > > As far as I understood, this is a larger scale issue related to > gnome-keyring. Maybe Stef Walter can provide more information on this. > > We propose a bounty to fix this bug.
Any taker?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
