All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: yocto@yoctoproject.org
Subject: Re: yassl recipe in the yocto project
Date: Wed, 28 Mar 2012 09:54:46 +0100	[thread overview]
Message-ID: <4F72D1D6.3060405@communistcode.co.uk> (raw)
In-Reply-To: <ADD6A3980E8C39419A432FF422031B4C0137E190@ORSMSX106.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

On 28/03/12 01:53, Kamble, Nitin A wrote:
>
> Hi Chris,
>
>   Here is the recipe we have in yocto-project for openssl projects to 
> be incorporated into embedded Linux distributions.
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-connectivity/openssl
>
> Please visit www.yoctoproject.org <http://www.yoctoproject.org> for 
> more information on the Yocto Project.
>
> It would be nice to get yassl recipe also in there as an alternative 
> to openssl.
>
> Context for others: I came across Chris at ESC, He works for yassl 
> .com which provides GPLv2  ssl solution like openssl which is smaller 
> compared to openssl and targeted for embedded solutions.
>
> Thanks,
>
> Nitin
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Just a heads up but I've also heard good things about PolarSSL, 
http://polarssl.org/ - choice is everything right ;)

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--


[-- Attachment #2: Type: text/html, Size: 4065 bytes --]

  parent reply	other threads:[~2012-03-28  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  0:53 yassl recipe in the yocto project Kamble, Nitin A
2012-03-28  2:32 ` Chris Conlon
2012-03-28  8:54 ` Jack Mitchell [this message]
2012-03-29 14:30 ` Koen Kooi

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=4F72D1D6.3060405@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=yocto@yoctoproject.org \
    /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.