Don't make assumptions about how pgpDig allocates things
authorPanu Matilainen <pmatilai@redhat.com>
Wed, 9 Nov 2011 07:19:48 +0000 (09:19 +0200)
committerPanu Matilainen <pmatilai@redhat.com>
Wed, 9 Nov 2011 07:23:26 +0000 (09:23 +0200)
commit9e9761caa885dfe5f588b9322cce9eaf03168510
treee4d7131088f9398e5e4aed61192e2f36b628730e
parent917a5c4f6b78174e3c7387fc7fb56e2900f2543e
Don't make assumptions about how pgpDig allocates things

- Only call pgpDigGetParams() on the public key once we've at least
  tried to fetch it via rpmKeyringLookup(). This way we dont assume
  things about how pgpDig internal allocation is done - currently
  it does return what's essentially a static pointer into pgpDig,
  but this is not a reasonable assumption for an opaque type.
  No functional changes.
lib/signature.c