From: Wei Liu <wei.liu2@citrix.com>
To: "Xu, Quan" <quan.xu@intel.com>
Cc: Doug Goldstein <cardoe@cardoe.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Wei Liu <wei.liu2@citrix.com>, Steven Haigh <netwiz@crc.id.au>
Subject: Re: Fixation on polarssl 1.1.4 - EOL was 2013-10-01
Date: Fri, 4 Mar 2016 10:09:00 +0000 [thread overview]
Message-ID: <20160304100900.GO5535@citrix.com> (raw)
In-Reply-To: <945CA011AD5F084CBEA3E851C0AB28894B859023@SHSMSX101.ccr.corp.intel.com>
create ^
thanks
On Fri, Mar 04, 2016 at 03:37:10AM +0000, Xu, Quan wrote:
> On February 16, 2016 1:08am, <wei.liu2@citrix.com> wrote:
> > On Mon, Feb 15, 2016 at 10:45:48AM -0600, Doug Goldstein wrote:
> > > On 2/15/16 10:28 AM, Wei Liu wrote:
> > > > On Sun, Feb 14, 2016 at 07:39:35PM +1100, Steven Haigh wrote:
> > > >> Hi all,
> > > >>
> > > >> Just been looking at the polarssl parts in Xen 4.6 and others -
> > > >> seems like we're hard coded to version 1.1.4 which was released on 31st
> > May 2012.
> > > >>
> > > >> Branch 1.1.x has been EOL for a number of years, 1.2.x has been EOL
> > > >> since Jan.
> > > >>
> > > >> It's now called mbedtls and current versions are 2.2.1 released in
> > > >> Jan this year.
> > > >>
> > > >> I'm not exactly clear on what polarssl is used for (and why not
> > > >> openssl?) - but is it time this was shown some loving?
> > > >>
> > > >
> > > > I grep'ed for polarssl in tree and the only user seems to be vtpm.
> > > > I've CC'ed Daniel and Quan for you.
> > > >
> > > > Wei.
> > > >
> > >
> > > Looks like pv-grub has a build dependency on it as well based on the
> > > snippet from stubdom/Makefile.
> > >
> > > .PHONY: grub
> > > grub: cross-polarssl grub-upstream $(CROSS_ROOT)
> > >
> >
> > Oh, yes, you're right.
> >
> > Looking at the source code pv-grub only needs the sha1 function from polarssl
> > which might be easy to dealt with though. On the other hand, if there is no
> > critical bug fix to the sha1 function, I wouldn't bother upgrading polarssl.
> >
> > In fact, I think vtpm also only cares about some crypto algorithms like AES and
> > SHA. We'd better check if there is any critical update to those functions before
> > doing anything.
> >
>
>
> Agreed.
> If you really want to upgrade it, IMO this change would be backward compatible.
> btw, it may be not an easy task to build the test env, and I can help you test your patch.
>
Right.
To be honest the chance of me working on it soon is rather low. To
prevent this issue falling through the crack I've created an entry in
bug tracker.
Wei.
> Quan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-04 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 8:39 Fixation on polarssl 1.1.4 - EOL was 2013-10-01 Steven Haigh
2016-02-15 16:28 ` Wei Liu
2016-02-15 16:45 ` Doug Goldstein
2016-02-15 17:07 ` Wei Liu
2016-03-04 3:37 ` Xu, Quan
2016-03-04 10:09 ` Wei Liu [this message]
2016-03-04 10:15 ` Processed: " xen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160304100900.GO5535@citrix.com \
--to=wei.liu2@citrix.com \
--cc=cardoe@cardoe.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=netwiz@crc.id.au \
--cc=quan.xu@intel.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.