Re: Gedit plugin
- From: Pietro Battiston <me pietrobattiston it>
- To: Stef Walter <stefw gnome org>
- Cc: seahorse-list gnome org
- Subject: Re: Gedit plugin
- Date: Sat, 27 Apr 2013 12:18:50 +0200
Il giorno sab, 27/04/2013 alle 11.24 +0200, Stef Walter ha scritto:
On 27.04.2013 09:35, Pietro Battiston wrote:
[...]
Instead I have another question: of all the keys I get with the
"ListKeys" function of org.gnome.seahorse.Keys, some have a "raw-id"
looking like "04E29C73", some like "B0894B0104E29C73:2". All of my tests
seem to show that those of the first kind are able to encrypt, those of
the second are not
(org.freedesktop.DBus.GLib.UnmappedError.Org.gnome.seahorse.Error.Failed.Code1: Key is not a valid
recipient for encryption). But can I reliably establish that I can drop all keys with the "raw-id" longer
than 8 digits when asking the user for a key to encrypt? Or is there a better method to do this filtering?
Again, looks like a bug to me. It's hard to know how to answer this
question off hand. libcryptui and that DBus interface is really old and
not really in use anymore. But happy to help integrate patches if you do
find the bug.
I'll try to take a look (but again that's not a stopper to me).
But your answer triggers an obvious (possibly final) question: is there
some suggested replacement to "libcryptui and that DBus interface" which
is "not really in use anymore"? Did I make an obvious mistake in relying
on it with newly written code?
Thanks,
Pietro
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]