On Fri, Oct 4, 2013 at 7:13 AM, Tom Cocagne <[email protected]> wrote:
> ==== Begin ZMQ Cert ==== > uuid: 9af3d710-e762-4cf4-a9cb-e5a5899bf3c8 > public_key: 81A...BF > [org.cocagne.home_network] > name: cool_zmq_app_server > webserver_port: 1234 > [zmq.rfc1034] > dns_name: org.cocagne.home_network.cool_zmq_app_server > http_port: 1234 > client_authentication_required: True > [signatures] > ... > ==== End ZMQ Cert ==== OK, this is great, and goes on my whiteboard as the first strawman for a certificate format. - begin/end markers so multiple certs can be sent in an email - unique UUID to... to allow unique identification - RFC-specific sections with defined fields What problem do the endpoint sections address? -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
