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

Tons of warnings #7

Open
ghost opened this issue Mar 6, 2013 · 8 comments
Open

Tons of warnings #7

ghost opened this issue Mar 6, 2013 · 8 comments

Comments

@ghost
Copy link

ghost commented Mar 6, 2013

I'm building for 10.7 SDK on 10.8 if that helps.

Screen Shot 2013-03-06 at 2 15 26 PM

@glebd
Copy link
Owner

glebd commented Mar 7, 2013

Use no_openssl branch.

Best regards,
Gleb

On 6 Mar 2013, at 20:17, sdegutis [email protected] wrote:

I'm building for 10.7 SDK on 10.8 if that helps.


Reply to this email directly or view it on GitHub.

@ghost
Copy link
Author

ghost commented Mar 7, 2013

This means I'll have to ditch the commit ba49865 that's only on master.. but that's probably fine.. right?

@glebd
Copy link
Owner

glebd commented Mar 7, 2013

That commit is OpenSSL-specific, so you don't want it.

On 7 Mar 2013, at 03:20, sdegutis [email protected] wrote:

This means I'll have to ditch the commit ba49865 that's only on master.. but that's probably fine.. right?


Reply to this email directly or view it on GitHub.

@ghost ghost closed this as completed Mar 7, 2013
@ghost
Copy link
Author

ghost commented Mar 7, 2013

Sold.

@ghost
Copy link
Author

ghost commented Mar 7, 2013

Actually, this only solves a few of these deprecation warnings. SHA1 and BIO_[etc] all still raise warnings.

@ghost ghost reopened this Mar 7, 2013
@ghost
Copy link
Author

ghost commented Mar 7, 2013

(Plus the no_openssl branch gives me false-successes on verification.)

@ghost ghost closed this as completed Mar 7, 2013
@ghost ghost reopened this Mar 7, 2013
@js
Copy link

js commented Apr 12, 2013

Any update on this? What's the status of the no_openssl branch? at a glance it look fine…

Running the tests (+ adding tests for invalid licence codes) doesn't give any false-positives. @sdegutis

@glebd
Copy link
Owner

glebd commented Apr 12, 2013

I'm using the no_ssl branch myself for a Lion-only app. Seems OK.

On 12 Apr 2013, at 12:01, Johan Sørensen [email protected] wrote:

Any update on this? What's the status of the no_openssl branch? at a glance it look fine…

Running the tests (+ adding tests for invalid licence codes) doesn't give any false-positives. @sdegutis


Reply to this email directly or view it on GitHub.

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

2 participants