From: Saul Wold <sgw@linux.intel.com>
To: Chris Conlon <chris@yassl.com>
Cc: yocto@yoctoproject.org
Subject: Re: CyaSSL Yocto Recipe
Date: Thu, 06 Sep 2012 15:14:41 -0700 [thread overview]
Message-ID: <50492051.8020109@linux.intel.com> (raw)
In-Reply-To: <A1E9071B-69AC-4306-ADEB-3C24FAC448C6@yassl.com>
On 09/06/2012 02:59 PM, Chris Conlon wrote:
> Adding a direct link to the CyaSSL recipe file for review:
>
> www.yassl.com/files/yocto/cyassl_2.3.0.bb
> <http://www.yassl.com/files/yocto/cyassl_2.3.0.bb>
>
Chris,
On initial inspection of this recipe it looks OK, what package/libraries
does it provide? Are they the same as the openssl package?
You may need RCONFLICTS_${PN} and/or RPROVIDES_${PN}, where the ${PN}
may need to be the package names in openssl, I need to check that.
I would suggest that initially you make this available as a standard
layer, possibly called meta-cyassl, it could be hosted on GitHub. You
can add it to the OpenEmbedded Layer Index. See
http://www.openembedded.org/wiki/LayerIndex
Distributions that want to use this instead of OpenSSL can then use your
layer and select your recipe, if it's setup correctly it will provide
what they need.
I hope this is helpful in moving things forward for you.
Sau!
Yocto Project Component Wrangler
aka Yocto Project User Space Architect
> Best Regards,
> Chris
>
> On Sep 6, 2012, at 10:32 AM, Kamble, Nitin A wrote:
>
>> And here is bit of information about CyaSSL from their
>> website.http://www.yassl.com/yaSSL/Products-cyassl.html
>> The CyaSSL embedded SSL library is a lightweight SSL library written
>> in ANSI C and targeted for embedded and RTOS environments - primarily
>> because of its small size, speed, and feature set. It is commonly
>> used in standard operating environments as well because of its
>> royalty-free pricing and excellent cross platform support. CyaSSL
>> supports industry standards up to the current TLS 1.2 level, is up
>> to20 times smaller than OpenSSL, and offers progressive ciphers such
>> as HC-128, RABBIT, and NTRU. User benchmarking and feedback reports
>> dramatically better performance when using CyaSSL over OpenSSL.
>> Thanks,
>> Nitin
>> *From:*Chris Conlon [mailto:chris@yassl.com]
>> *Sent:*Thursday, September 06, 2012 9:07 AM
>> *To:*yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>> *Cc:*Kamble, Nitin A
>> *Subject:*CyaSSL Yocto Recipe
>>
>> Hi,
>>
>> As per discussions with a few of the Yocto members, we have put
>> together a Yocto Project recipe for the CyaSSL embedded SSL library.
>> I have attached the recipe here for review and comments.
>>
>> Thanks,
>>
>> Chris Conlon
>> www.yassl.com <http://www.yassl.com>
>> chris@yassl.com <mailto:chris@yassl.com>
>> Skype: chris_conlon_07
>> +1 406 209 0601
>>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2012-09-06 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 16:06 CyaSSL Yocto Recipe Chris Conlon
2012-09-06 16:32 ` Kamble, Nitin A
2012-09-06 21:59 ` Chris Conlon
2012-09-06 22:14 ` Saul Wold [this message]
2012-09-06 22:38 ` Chris Conlon
2012-09-06 22:53 ` Richard Purdie
2012-09-07 19:55 ` Chris Conlon
2012-10-09 20:26 ` Chris Conlon
2012-12-12 15:30 ` Richard Purdie
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=50492051.8020109@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=chris@yassl.com \
--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.