Comment 3 for bug 862609

Now, that's interesting. I had a look again and it seems a branch was
created for Gnome 3,
but there are just a lot of translations.

On the other hand, the devs have repeatedly stated that they've got
seahorse-plugins building
against GTK 3:

http://git.gnome.org/browse/seahorse-plugins/commit/?id=17f60f9087970b4b0084cebe1367330bdd5eb634

http://mail.gnome.org/archives/gnome-keyring-list/2010-October/msg00002.html

And Gentoo seem to have successfully built seahorse-plugins for Gnome 3:

http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-crypt/seahorse/seahorse-3.0.2.ebuild

As fas as the security vulnerability is concerned, you're of course
right in the strictest sense of the word.
No system is going to be immediately susceptible to attack because
there's no seahorse-plugins in the repos.
But an increase in the number of unsigned and unauthenticated files
being handled can clearly be no good
security. And with no seahorse-plugins and easy right click, that's what
we're looking at. Precious few
have heard of gpg and bothered to master the command line.

Roger

On 01/10/11 06:33, Jeremy Bicha wrote:
> This is not a security vulnerability.
>
> The seahorse-plugins developers have yet to release even an alpha of a
> GNOME 3 compatible version.
>
> ftp://ftp.gnome.org/pub/GNOME/sources/seahorse-plugins/
>
> ** Tags added: upgrade-software-version
>
> ** This bug is no longer flagged as a security vulnerability
>