Thanks Thorsten. Is there any legitimate need for CommonCrypto then?

On Dec 8, 2016 3:30 PM, "Thorsten Alteholz" <allj...@alteholz.de> wrote:

>
>
> On Thu, 8 Dec 2016, Josh Spain wrote:
>
> @Alexey,
>> It is not clear to me what the difference is between ComonCrypto and
>> CRYPTO=buildin, when CRYPTO=buildin uses common/crypto/builtin
>>
>> Is it the same thing?
>>
>
> As far as I understand CommonCrypt is a replacement library for openssl
> made by Apple and is only available on Darwin. CRYPTO=builtin is another
> implementation of Alljoyns crypto functions, lives in common/crypto/builtin
> and can be used on every platform.
>
>   Thorsten
>
>
>
>
>
>> [Affinegylogo201450px.format_png.resize_200x.png#logo]
>> Josh Spain
>> Director of Engineering Affinegy, Inc.
>> t.512-535-1700 x1006
>> a. 1705 S Capital of Texas Hwy, Suite 310, Austin, TX 78746 USA
>> Website Email
>> [linkedin.png]  [twitter.png]
>> [twitter.png] Latest Tweet: "In the physical world, advances are
>> constrained by physics." Silicon Valley Stumbles in World Beyond Software -
>> WSJ https://t.co/DCX4w5E7W8
>> Read More [twitter-white.png]
>>
>> On Thu, Dec 8, 2016 at 12:15 PM, Krystian Zlomek <kzlo...@affinegy.com>
>> wrote:
>>       Can we reach some conclusion on this?
>>
>> Should I abandon https://git.allseenalliance.org/gerrit/#/c/7825/ or
>> someone is going to work on this?
>>
>> On Thu, Nov 24, 2016 at 8:41 AM, Alexey Solovyov <alex...@affinegy.com>
>> wrote:
>>       Why we need to use CommonCrypto? CRYPTO=buildin works well, and we
>> will use it as default in build_core/SConscript for Apple platforms
>>       (see https://git.allseenalliance.org/gerrit/#/c/9341/)
>>
>> ps
>> CRYPTO=buildin uses:
>>
>> external/sha1/
>> external/sha2/
>> common/crypto/builtin/
>>
>>
>> ---
>> Alexey
>>
>>       24 нояб. 2016 г., в 4:20, Josh Spain <jsp...@affinegy.com>
>> написал(а):
>>
>> @Jorge, Olga or Alexey, can you determine if we already have support for
>> CommonCrypto? If not would one of you review this changeset? It requires a
>> rebase.
>>
>> Thanks,
>> Josh
>>
>>
>> On Nov 23, 2016 4:14 PM, "Kevin Kane via Alljoyn-core" <
>> alljoyn-core@lists.alljoyn.org> wrote:
>>
>>       I restored the change (actually https://git.allseenalliance.or
>> g/gerrit/#/c/7825/) but there’s a merge conflict with the current head of
>>       master so it can’t be rebased automatically. Is someone available
>> to take a look at this?
>>
>>
>>
>>       From: alljoyn-core-boun...@lists.alljoyn.org [mailto:
>> alljoyn-core-boun...@lists.alljoyn.org] On Behalf Of Brad Kemp
>>       Sent: Wednesday, November 23, 2016 11:23 AM
>>       To: Krystian Zlomek <kzlo...@affinegy.com>
>>       Cc: Mathew Martineau <allseen-c...@lists.allseenalliance.org>; Way
>> Vadhanasin <wayakorn.vadhana...@microsoft.com>
>>
>>
>>       Subject: Re: [Alljoyn-core] OpenSSL 1.1.0
>>
>>
>>
>> Here is the checkin
>>
>> https://git.allseenalliance.org/gerrit/#/c/7849/
>>
>> Have at it.
>>
>> Regards
>>
>> Brad
>>
>>
>>
>>       On Nov 23, 2016, at 2:07 PM, Krystian Zlomek <kzlo...@affinegy.com>
>> wrote:
>>
>>
>>
>> Brad, do you have a link to Gerrit with your CommonCrypto change? We
>> could evaluate it and possibly fix the Windows build problem.
>>
>>
>>
>> On Wed, Nov 23, 2016 at 7:38 PM, Brad Kemp <b...@beechwoods.com> wrote:
>>
>>       We have been using the CommonCrypto internally instead of SSL.
>>
>>       Brad
>>
>>
>>
>>             On Nov 23, 2016, at 1:37 PM, Brad Kemp <b...@beechwoods.com>
>> wrote:
>>
>>
>>
>> Marcello closed them because they sat un-attend for too long.  The change
>> broke the windows debug build. We don’t have windows
>> machines here and could not figure out why a change in the MAC build
>> cause windows breakage
>>
>> Brad
>>
>>
>>
>>       On Nov 23, 2016, at 1:33 PM, Krystian Zlomek <kzlo...@affinegy.com>
>> wrote:
>>
>>
>>
>> Strange, ASACORE-2957 and it's duplicate ASACORE-1826 are closed but Jira
>> shows 0 git commits linked to that.
>>
>>
>>
>>
>>
>> On Wed, Nov 23, 2016 at 5:25 PM, Josh Spain <jsp...@affinegy.com> wrote:
>>
>>       According to ASACORE-2957 this has been completed already. It is
>> closed.
>>
>>
>>
>> On Tue, Nov 22, 2016 at 4:12 PM, Brad Kemp <b...@beechwoods.com> wrote:
>>
>>       Look at ASACORE 2957 we submitted it, but somehow it broke the
>> Windows builds and we could never
>>       figure out why.
>>
>>       This removes SSL from the MAC and replaces it with CommonCrypto
>>
>> Brad
>>
>>
>>
>>
>>
>>       On Nov 22, 2016, at 4:56 PM, Josh Spain <jsp...@affinegy.com>
>> wrote:
>>
>>
>>
>> Okay, since we still support it (and esp. since it's default on Linux and
>> ARM) we need to track this.
>> @Thorsten, can you log a JIRA issue about this?
>>
>>
>>
>> Thanks,
>>
>> Josh
>>
>> [Affinegylogo201450px.format_png.resize_200x.png]
>>
>> Josh Spain
>> Director of Engineering Affinegy, Inc.
>> t.512-535-1700 x1006
>> a. 1705 S Capital of Texas Hwy, Suite 310, Austin, TX 78746 USA
>> Website Email
>>
>> [linkedin.png]  [twitter.png]
>>
>> [twitter.png] Latest Tweet: Building the buzz for their IPO ...This is
>> Snapchat’s new Spectacles store
>> in New York City https://t.co/AG1u809qRL via @techcrunch
>>
>> Read More
>>
>> [twitter-white.png]
>>
>>
>>
>> On Tue, Nov 22, 2016 at 3:34 PM, Kevin Kane <kk...@microsoft.com> wrote:
>>
>>       Based on build_core\SConscript, it’s still the default for Linux
>> and Darwin on ARM. It’s
>>       an option for all platforms.
>>
>>
>>
>>       From: Way Vadhanasin
>>       Sent: Tuesday, November 22, 2016 1:26 PM
>>       To: Josh Spain <jsp...@affinegy.com>; Thorsten Alteholz <
>> allj...@alteholz.de>; Krystian
>>       Zlomek <kzlo...@affinegy.com>; Kevin Kane <kk...@microsoft.com>
>>       Cc: allseen-c...@lists.allseenalliance.org
>>       Subject: RE: [Alljoyn-core] OpenSSL 1.1.0
>>
>>
>>
>> I thought Linux is using it, but Kevin probably knows for sure.
>>
>>
>>
>> From: Josh Spain [mailto:jsp...@affinegy.com]
>> Sent: Tuesday, November 22, 2016 12:02 PM
>> To: Thorsten Alteholz <allj...@alteholz.de>; Krystian Zlomek <
>> kzlo...@affinegy.com>; Way
>> Vadhanasin <wayakorn.vadhana...@microsoft.com>
>> Cc: allseen-c...@lists.allseenalliance.org
>> Subject: Re: [Alljoyn-core] OpenSSL 1.1.0
>>
>>
>>
>> Krystian or Way,
>>
>>
>>
>> Do either of you know if OpenSSL is mandatory or default for any
>> platform? Do you know if it is
>> still supported as an option? I'm pretty sure we removed it from iOS and
>> Android.
>>
>>
>>
>> Thanks,
>>
>> Josh
>>
>> [Affinegylogo201450px.format_png.resize_200x.png]
>>
>> Josh Spain
>> Director of Engineering Affinegy, Inc.
>> t.512-535-1700 x1006
>> a. 1705 S Capital of Texas Hwy, Suite 310, Austin, TX 78746 USA
>> Website Email
>>
>> [linkedin.png]  [twitter.png]
>>
>> [twitter.png] Latest Tweet: Building the buzz for their IPO ...This is
>> Snapchat’s new Spectacles
>> store in New York City https://t.co/AG1u809qRL via @techcrunch
>>
>> Read More
>>
>> [twitter-white.png]
>>
>>
>>
>> On Tue, Nov 22, 2016 at 1:23 PM, Thorsten Alteholz <allj...@alteholz.de>
>> wrote:
>>
>>
>>
>>       On Mon, 21 Nov 2016, Josh Spain wrote:
>>
>>             Someone please correct me if I'm wrong, but I don't think
>> we're using
>>             OpenSSL on any platform any longer.
>>
>>
>>       Hmm, according to [1] the default_crypto in the master branch is
>> set to 'openssl' on
>>       Linux and Darwin (at least for non-x86).
>>       According to [2] one can use the latest version of OpenSSL for
>> cryptographic
>>       functions.
>>       So are these information outdated and the builtin stuff shall be
>> better used? Is
>>       this also true for older versions or just for 16.10 and later?
>>
>>         Thorsten
>>
>>
>>       [1] https://cgit.allseenalliance.org/core/alljoyn.git/tree/build
>> _core/SConscript
>>       [2]
>>       https://allseenalliance.org/framework/documentation/develop/
>> building/linux/build-source
>>
>>
>>
>>
>>       _______________________________________________
>>       Alljoyn-core mailing list
>>       Alljoyn-core@lists.alljoyn.org
>>       https://lists.alljoyn.org/mailman/listinfo/alljoyn-core
>>
>>
>>
>>
>>
>> _______________________________________________
>> Alljoyn-core mailing list
>> Alljoyn-core@lists.alljoyn.org
>> https://lists.alljoyn.org/mailman/listinfo/alljoyn-core
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Alljoyn-core mailing list
>> Alljoyn-core@lists.alljoyn.org
>> https://lists.alljoyn.org/mailman/listinfo/alljoyn-core
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Alljoyn-core mailing list
>> Alljoyn-core@lists.alljoyn.org
>> https://lists.alljoyn.org/mailman/listinfo/alljoyn-core
>>
>>
>>
>>
>>
>>
>>
_______________________________________________
Alljoyn-core mailing list
Alljoyn-core@lists.alljoyn.org
https://lists.alljoyn.org/mailman/listinfo/alljoyn-core

Reply via email to