Is it possible to support more than just MIT’s pgp server? Other mirrors
might be more reliable.

On Sat, Feb 9, 2019 at 07:07, Shane Curcuru <[email protected]> wrote:

> Can;'t type enough for code yet, but miss coding, so... ideas:
>
> When verifying zig, you want workbench to:
>
> - IF we get here: (i.e. there was an error gettign key)
>
> https://github.com/apache/whimsy/blob/master/www/secretary/workbench/views/actions/check-signature.json.rb#L40
>
> - And if
>     err.include? "gpg: Can't check signature: No public key" or
>     err.include? "gpg: Can't check signature: public key not found"
>
> - Then Do: enable the action that sends pubkey.erb (so you can push the
> button - or do you want it to automatically send that upload email)?
>
> - ELSE: (other error like proxy/timeout)
>   - Disable the pubkey.erb
>   - Allow the Secretary to re-process the check sig action.
>
> Do you want it to simply give you the button to immediately re-chceck
> for the key, or do you want to leave this whole msg and come back later?
>
> --
>
> - Shane
>   Director & Member
>   The Apache Software Foundation
>
> Craig Russell wrote on 2/8/19 8:18 PM:
> > Hi,
> >
> > When a document has an associated .asc file, whimsy automatically tries
> to download the public key in order to verify the signature.
> >
> > But the key server is often busy and just cannot service the request
> timely.
> >
> > The current behavior of whimsy does not distinguish among at least three
> cases:
> >
> > No key found
> > Timeout
> > Proxy error
> >
> > No key found is the only case where the secretary should send the
> "upload public key" message to the submitter.
> >
> > In the other two cases, the secretary should retry (later) until a
> definitive No key found error is received or the public key is downloaded.
> >
> > Can the actual error be extracted from the message to avoid confusion?
> >
> > Thanks,
> >
> > Craig
> >
> > Craig L Russell
> > Secretary, Apache Software Foundation
> > [email protected] http://db.apache.org/jdo
> >
>
> --
Matt Sicker <[email protected]>

Reply via email to