Signing events

[Bob Denny]

My work is far more than a "point of view"...

The Dakota broker/sender/receiver package (cross platform,
http://www.ivoa.net/Documents/Notes/DakotaBroker/)
<http://www.ivoa.net/Documents/Notes/DakotaBroker/>fully supports digisig
access-authentication and integrity checking per the VOEvent Transport 1.0 IVOA
Note
(http://www.ivoa.net/Documents/Notes/VOEventTransport/20090805/NOTE-VOEventTransport-1.1-20090805.html).
Dakota is a production package for Mac, Linux and Windows
(http://voevent.dc3.com/).

Dakota has command line tools for sending, receiving, and checking VOEvent
messages. It also has a full-up broker that will run as a daemon on any of the
above three operating systems.

We operate a broker here (voevent.dc3.com) and can arrange to receive signed
events from you and validate the signature, as well as allow publishing based on
the presence of your signature. I would just need your GPG public key.
Unfortunately, due to the fragmented nature of VOEvent message transport, the
only people who will receive your events are the others tied to my broker. Right
now that's AAVSO Net and several amateur and low-visibility university
observatories that are getting CBAT and NASA/Swift feeds.

  -- Bob

Rob S Said:
> Hi John,
>
> I believe both remain valid points of view.  What the WG had decided - at least for v2.0 - was not to include explicit hooks for the signatures in the schema itself, but this shouldn't strongly impact any of the options.  Few of the many and varied transient alert projects have had strong immediate signing requirements.  Do you have a specific project need here?
>
> Rob

John Said:
> Dear all,
>
> Forgive me ignorance, but I'm trying to get up to speed on previous discussions about signing VOEvents. I've seen Bob Denny's proposal at <http://www.ivoa.net/Documents/latest/VOEventDigiSig.html> and Steve Allen's publication (Astron. Nach., 329, 298-300, 2008). Both of those are a few years old now, though, and I'm wondering if either of them have gained community support/acceptance or if they state of the art has moved on to something different.
>
> I've had quick browse through the mailing list archives, but can't seen anything very conclusive. Any thoughts or references on current best practice?
>
> Thanks!
>
> John
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/voevent/attachments/20120124/245bbcb4/attachment.html>