> On Nov 12, 2019, at 3:14 AM, Tomas Mraz <tm...@redhat.com> wrote: > > Could it be a padding issue? I.E. use DH_compute_key_padded() instead.
Do we have an open issue to document DH_compute_key_padded(3)?
It should be documented right next to DH_compute_key(3), with
some words to suggest that the caller needs to know whether
the peer expects a key octet string that is fixed width (same
as "p") or stripped of inessential leading zero octets.
--
Viktor.
