* [sup-talk] gpg-options.rb: how to set always_trust
@ 2011-01-23 8:25 Sebastian Lipp
2011-01-23 12:17 ` Michael Stapelberg
[not found] ` <AANLkTimJZiRE31R5KJBdqZv5L17qhKeLjbO4fWM5LfD2@mail.gmail.com>
0 siblings, 2 replies; 7+ messages in thread
From: Sebastian Lipp @ 2011-01-23 8:25 UTC (permalink / raw)
To: sup-talk
Hi.
I've just 'git pull'ed so my always_trust setting for GnuPG isn't
working any more. I tried to set it by just putting
{:always_trust => true}
into gpg-options.rb but it doesn't work. I bet I have to put something
like
if(operation == encrypt)
always_trust = 1;
into the file. The Problem is that I have got no clue about Ruby.
Any assistance in putting the right code snipped here would be
appreciated.
--
basti
Government is a disease that masquerades as its own cure
-- Robert Lefevre
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [sup-talk] gpg-options.rb: how to set always_trust
2011-01-23 8:25 [sup-talk] gpg-options.rb: how to set always_trust Sebastian Lipp
@ 2011-01-23 12:17 ` Michael Stapelberg
[not found] ` <AANLkTimJZiRE31R5KJBdqZv5L17qhKeLjbO4fWM5LfD2@mail.gmail.com>
1 sibling, 0 replies; 7+ messages in thread
From: Michael Stapelberg @ 2011-01-23 12:17 UTC (permalink / raw)
To: sup-talk
Hi Sebastian,
Excerpts from Sebastian Lipp's message of 2011-01-23 09:25:58 +0100:
> Any assistance in putting the right code snipped here would be
> appreciated.
See the wiki at http://sup.rubyforge.org/wiki/wiki.pl?GPG, it has examples for
hooks for sup >= 0.12.
Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [sup-talk] gpg-options.rb: how to set always_trust
[not found] ` <AANLkTimJZiRE31R5KJBdqZv5L17qhKeLjbO4fWM5LfD2@mail.gmail.com>
@ 2011-01-23 22:09 ` Sebastian Lipp
2011-01-24 9:15 ` Shadowfirebird
2011-01-30 23:04 ` Hamish
0 siblings, 2 replies; 7+ messages in thread
From: Sebastian Lipp @ 2011-01-23 22:09 UTC (permalink / raw)
To: sup-talk
Excerpts from Hamish D's message of So Jan 23 11:47:32 +0100 2011:
> > I've just 'git pull'ed so my always_trust setting for GnuPG isn't
> > working any more. I tried to set it by just putting
> > {:always_trust => true}
> > into gpg-options.rb but it doesn't work.
>
> This may be slightly obscure,
I expected it would, but as I said I have no clue about ruby. ;)
> if operation == "encrypt"
> options.merge({:always_trust => true})
> end
> options
That is exactly what I was looking for. Thanks.
But another problem popped up. Now I can't sign any message. It makes no
difference if gpg-options.rb is there or not. There is also no difference in
choosing sign or sign and encrypt. There are no messages about that in
the log even with debugging turned on. Have I found a bug?
--
basti
The Web should be like a white sheet of paper: ready to be written on,
with no control over what is written.
-- Tim Berners-Lee
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [sup-talk] gpg-options.rb: how to set always_trust
2011-01-23 22:09 ` Sebastian Lipp
@ 2011-01-24 9:15 ` Shadowfirebird
[not found] ` <AANLkTimrPK4Bt7z+uN5AkShp3uJSw3OdbR2A-R0p4RoA@mail.gmail.com>
2011-01-30 23:04 ` Hamish
1 sibling, 1 reply; 7+ messages in thread
From: Shadowfirebird @ 2011-01-24 9:15 UTC (permalink / raw)
To: sup-talk
> But another problem popped up. Now I can't sign any message. It makes no
> difference if gpg-options.rb is there or not. There is also no difference in
> choosing sign or sign and encrypt. There are no messages about that in
> the log even with debugging turned on. Have I found a bug?
I've just upgraded to 0.12. On reading your post I tried signing a message and sending it to myself' it worked fine. So I hazard to guess that it might be a problem with your hooks (or rather, with how the new Sup is reading your existing hook code.) I only have a before-add-message and a mime-view hook set, so that would appear to be the likely difference between you and me.
Hope that helps. Maybe you need to post your gpg-related hooks here...
--
"It's not just a computer -- it's your ass."
-- Cal Keegan
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [sup-talk] gpg-options.rb: how to set always_trust
[not found] ` <AANLkTimB43mBbe-3EvRxZHCK_n9-Xy0mL1MHRGSO6MTf@mail.gmail.com>
@ 2011-01-24 10:34 ` Hamish D
2011-01-25 14:32 ` Sebastian Lipp
0 siblings, 1 reply; 7+ messages in thread
From: Hamish D @ 2011-01-24 10:34 UTC (permalink / raw)
To: Shadowfirebird; +Cc: sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 483 bytes --]
Interesting ... it may well be a bug. As well as your hooks, could you let
me know:
* your gpg key type, including whether you have a separate sub key for
signing. If your key is on public keyservers then the key ID could also be
useful.
* whether you use the gpgkey option in .sup/config.yaml
I'll look into it in the next few days. I might even try constructing a gpg
test suite for sup ...
Hamish Downer
On 24 Jan 2011 09:15, "Shadowfirebird" <shadowfirebird@gmail.com> wrote:
[-- Attachment #1.2: Type: text/html, Size: 632 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [sup-talk] gpg-options.rb: how to set always_trust
2011-01-24 10:34 ` Hamish D
@ 2011-01-25 14:32 ` Sebastian Lipp
0 siblings, 0 replies; 7+ messages in thread
From: Sebastian Lipp @ 2011-01-25 14:32 UTC (permalink / raw)
To: sup-talk
Excerpts from Hamish D's message of Mo Jan 24 11:34:28 +0100 2011:
> * your gpg key type, including whether you have a separate sub key for
> signing. If your key is on public keyservers then the key ID could also be
> useful.
A750401F
> * whether you use the gpgkey option in .sup/config.yaml
Yes, I do. I tried to delete this option and moved all my GPG-related
hooks out of sup's reach. The last thing I just tried was pulling again.
Nothing helped.
In my last mail I told that I can't sign. That's not true (anymore). I
can sign but when I choose sign and encrypt there is no signature. Can't
say whether this was a misinformation by me or is related to the latest
pull.
All I can tell is that it worked like a charm since I use sup. It might
be related to the change to GPGME.
--
basti
Die Zwingburg des Privateigentums wird fallen und auf ihren Trümmer wird
sich der Tempel des Kommunismus erheben.
Alle Festungen des Staates werden kapitulieren müssen, und in herrlicher
Gestalt wird sich zeigen der Genius der Anarchie.
Wer diesen Idealen zuzuschreiten entschlossen ist, der reiche uns die
Hände!
-- Johann Most
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [sup-talk] gpg-options.rb: how to set always_trust
2011-01-23 22:09 ` Sebastian Lipp
2011-01-24 9:15 ` Shadowfirebird
@ 2011-01-30 23:04 ` Hamish
1 sibling, 0 replies; 7+ messages in thread
From: Hamish @ 2011-01-30 23:04 UTC (permalink / raw)
To: sup-talk
Excerpts from Sebastian Lipp's message of Sun Jan 23 22:09:01 +0000 2011:
> Excerpts from Hamish D's message of So Jan 23 11:47:32 +0100 2011:
> > if operation == "encrypt"
> > options.merge({:always_trust => true})
> > end
> > options
>
> That is exactly what I was looking for. Thanks.
I've discovered that it actually needs to be
if operation == "encrypt"
options.merge!({:always_trust => true})
end
options
I've updated the wiki aswell. The difference is using merge! rather than
merge - I discovered this while tracking down your other issue:
> But another problem popped up. Now I can't sign any message. It makes no
> difference if gpg-options.rb is there or not. There is also no difference in
> choosing sign or sign and encrypt. There are no messages about that in
> the log even with debugging turned on. Have I found a bug?
This bug is now fixed in the next branch (and the gpgme branch). Someone
should hopefully merge this into master soon.
http://rubyforge.org/pipermail/sup-devel/2011-January/000965.html
Hamish Downer
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-01-30 23:22 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-23 8:25 [sup-talk] gpg-options.rb: how to set always_trust Sebastian Lipp
2011-01-23 12:17 ` Michael Stapelberg
[not found] ` <AANLkTimJZiRE31R5KJBdqZv5L17qhKeLjbO4fWM5LfD2@mail.gmail.com>
2011-01-23 22:09 ` Sebastian Lipp
2011-01-24 9:15 ` Shadowfirebird
[not found] ` <AANLkTimrPK4Bt7z+uN5AkShp3uJSw3OdbR2A-R0p4RoA@mail.gmail.com>
[not found] ` <AANLkTimB43mBbe-3EvRxZHCK_n9-Xy0mL1MHRGSO6MTf@mail.gmail.com>
2011-01-24 10:34 ` Hamish D
2011-01-25 14:32 ` Sebastian Lipp
2011-01-30 23:04 ` Hamish
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox