Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use mbedTLS binaries shipped with Julia 0.5 #54

Closed
wildart opened this issue Jul 18, 2016 · 19 comments
Closed

Use mbedTLS binaries shipped with Julia 0.5 #54

wildart opened this issue Jul 18, 2016 · 19 comments

Comments

@wildart
Copy link
Member

wildart commented Jul 18, 2016

Julia 0.5 will be shipped with mbedTLS 2.2.1 binaries, it would be better to use them in the future versions.

@tkelman
Copy link
Contributor

tkelman commented Jul 18, 2016

were there any API changes? if the bundled binaries pass the validation tests, this should happen automatically

@wildart
Copy link
Member Author

wildart commented Jul 18, 2016

No, it's the same version 2.2.1. I guess BinDeps would detect julia provided libs and setup package against them.

@tkelman
Copy link
Contributor

tkelman commented Jul 18, 2016

The package is using 2.1.1 at the moment - https://github.com/JuliaWeb/MbedTLS.jl/blob/master/deps/build.jl

I'm pretty sure that's insecure and needs to be updated for the sake of 0.4 though.

@wildart
Copy link
Member Author

wildart commented Jul 18, 2016

I misread it. Sure update is required. Hopefully, it would be easy with julia shipped binaries.

@tkelman
Copy link
Contributor

tkelman commented Jul 18, 2016

The validation here should be a lot stricter if there are potential API changes and binaries coming from Julia as well as previously-built (or downloaded) binaries of older versions around. Why didn't your libgit2 work use 2.3.0?

@wildart
Copy link
Member Author

wildart commented Jul 18, 2016

When I wrote patch to libssh2 when 2.2.1 was the last version. As I understand 2.1.5 is a maintenance release now. And it looks like we would require to use it or 2.3.* because of fixes to bignum API.

I prefer 2.3.* as it has better custom configuration build support.

@tkelman
Copy link
Contributor

tkelman commented Jul 18, 2016

are there api changes between 2.2 and 2.3, does your patch for libssh2 need changing at all, or should it be a simple version bump and replacing the checksums? if it's the latter I can add it to JuliaLang/julia#17475

@wildart
Copy link
Member Author

wildart commented Jul 18, 2016

version bump should work

@malmaud
Copy link
Contributor

malmaud commented Aug 14, 2016

Are there any action items for me?

@tkelman
Copy link
Contributor

tkelman commented Aug 14, 2016

it isn't doing this correctly yet, so yes - get it working

@malmaud
Copy link
Contributor

malmaud commented Aug 14, 2016

Have we figured out why bindeps isn't automatically finding the bundled binaries? Maybe I'll just add custom logic to build.jl.

@tkelman
Copy link
Contributor

tkelman commented Aug 14, 2016

Are your bindings up to date with the 2.3 API? Does 2.3 pass your validation checks?

@malmaud
Copy link
Contributor

malmaud commented Aug 14, 2016

Looking at https://github.com/ARMmbed/mbedtls/blob/development/ChangeLog, there were no API changes between 2.1 and 2.3, so it should be as simple as making sure bindeps picks up the binary.

@malmaud
Copy link
Contributor

malmaud commented Aug 14, 2016

Hmm, so as far as I can tell, the library in julia/usr/lib passes the validation test. Are we sure that path is checked by BinDeps?

@tkelman
Copy link
Contributor

tkelman commented Aug 14, 2016

Maybe not. Try a provides(Binaries or something? be sure you use the relative paths for a binary install of julia, not a source install.

@malmaud
Copy link
Contributor

malmaud commented Aug 14, 2016

I can't actually find where they are in the binary install of Julia, at least on OS X. At least they are not in Julia-0.6.app/Contents/Resources/julia/lib.

@malmaud
Copy link
Contributor

malmaud commented Aug 14, 2016

Oh, NM.

@malmaud
Copy link
Contributor

malmaud commented Aug 14, 2016

Alright, #66 is my attempt at closing this.

@quinnj
Copy link
Member

quinnj commented Dec 1, 2016

Implemented in #81

@quinnj quinnj closed this as completed Dec 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants