Initialization of secure memory ( Problem might be with libgcrypto )

SHREE DUTH AWASTHI shreeduth.awasthi at
Fri Apr 12 11:08:09 CEST 2013

Hello Werner,

Thanks a lot for your time.

But I still doubt that the problem is with libcrypto ( seeing the
below log

 _gcry_log_bug (fmt=0x48e0 <Address 0x48e0 out of bounds>)

Can you please eloborate your observation.

Thanking you in anticipation.

Thanks and Regards,
Shree Duth Awasthi

On Thu, Apr 11, 2013 at 1:57 PM, Werner Koch <wk at> wrote:

> On Wed, 10 Apr 2013 21:44, shreeduth.awasthi at said:
> > # virsh -c qemu+tls://localhost/system version
> > error: authentication failed: TLS handshake failed A TLS packet with
> > unexpected length was received.
> > error: failed to connect to the hypervisor
> You should ask the maintainer of virsh for help.  This list is about
> libgcrypt.  It seems that virsh does not make proper use of libgcrypt or
> gnutls.  In fact, Libgcrypt tells you what has been done wrong.
> Salam-Shalom,
>    Werner
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20130412/2fcd36ea/attachment.html>

More information about the Gcrypt-devel mailing list