From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [GSoC] project proposal Date: Wed, 22 Apr 2015 15:43:22 +0200 Message-ID: <5537A57A.3040209@redhat.com> References: <5509AAEE.8010307@redhat.com> <5509E748.9000501@redhat.com> <553659BC.2090508@redhat.com> <20150422082024.GA6581@stefanha-thinkpad.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: "MA..." To: Catalin Vasile , Stefan Hajnoczi Return-path: Received: from mail-wi0-f177.google.com ([209.85.212.177]:36601 "EHLO mail-wi0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756881AbbDVNn1 (ORCPT ); Wed, 22 Apr 2015 09:43:27 -0400 Received: by wizk4 with SMTP id k4so178555655wiz.1 for ; Wed, 22 Apr 2015 06:43:26 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 22/04/2015 10:51, Catalin Vasile wrote: > If we want a mainstream userspace backend that could interact with a > lot of crypto engines, we could use OpenSSL (it can actually use > cryptodev and AF_ALG as engines). > For now, until mid June (my diploma project presentation) I still want > to use vhost as a backend for the sole purpose of having a finished > backend which now I have a good grasp upon. > If the finished work would be good enough work to be merged upstream > will be talked later. > As a GSoC project, OpenSSL as a backend would continue the > virtio-crypto development, as it's not uncommon to have multiple types > of backends. > The current work on virtio-crypto qemu and guest module is pretty > backend agnostic, and could allow future development(use of other > backends and other features). OpenSSL's license is not compatible with QEMU, hence the suggestion of using gnutls. Paolo