On Tue, Oct 15, 2013 at 11:28 AM, Pieter Hintjens <[email protected]> wrote:

> The key itself may be encrypted; there may also be metadata that is
> also encrypted. The goal is to allow verification out of band that the
> entire package wasn't replaced by a fraudulent version en-route.


If your goal is to keep the public key confidential, I'd suggest using
either SHA256 or Blake2b.

-- 
Tony Arcieri
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to