Opened 4 years ago

Closed 5 weeks ago

#24107 closed enhancement (invalid)

Inclusion of OpenSSL, stage 1

Reported by: charpent Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: packages: standard Keywords: openssl
Cc: gh-timokau, vbraun, dunfield Merged in:
Authors: Reviewers: Matthias Koeppe, Samuel Lelièvre
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by charpent)

This has been discussed and voted on sage-devel.

A request for advice has also been posted on sage-devel. Discussions on what to do should be kept there, using this ticket for technical issues only.

Change History (10)

comment:1 Changed 4 years ago by charpent

  • Description modified (diff)

comment:2 Changed 3 years ago by gh-timokau

  • Cc gh-timokau added

comment:3 follow-up: Changed 3 years ago by slelievre

OpenSSL versioning and license: 2018-11-28 news on the OpenSSL blog.

This will help once OpenSSL 3.0.0 is released under the new license.

comment:4 in reply to: ↑ 3 Changed 3 years ago by charpent

Replying to slelievre:

OpenSSL versioning and license: 2018-11-28 news on the OpenSSL blog.

This will help once OpenSSL 3.0.0 is released under the new license.

For now, it's just a statement of intent, which makes us as much good as a campaign promise...

comment:5 follow-up: Changed 3 years ago by slelievre

  • Cc vbraun added

Python 2.7.16 was released 2019-03-04, and the page for that release:

https://www.python.org/downloads/release/python-2716/

has the following note about OpenSSL:

Attention macOS users: As of 2.7.16, all current python.org macOS installers ship with builtin copies of OpenSSL and Tcl/Tk 8.6. See the installer README for more information.

If Python does it, can we also ship OpenSSL with our macOS binaries?

comment:6 in reply to: ↑ 5 Changed 3 years ago by slelievre

Replying to slelievre:

If Python does it, can we also ship OpenSSL with our macOS binaries?

Similar question asked and answered on sage-devel as follows:

Dima wrote:

As Python.org now ships 2.7.16 with pre-build openssl, then why don't we do the same?

Volker replied:

Because Python is not GPL licensed, of course

comment:7 Changed 17 months ago by dunfield

  • Cc dunfield added

comment:8 Changed 6 weeks ago by mkoeppe

  • Milestone changed from sage-8.1 to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

Outdated, should close

comment:9 Changed 6 weeks ago by slelievre

  • Reviewers set to Matthias Koeppe, Samuel Lelièvre
  • Status changed from needs_review to positive_review

comment:10 Changed 5 weeks ago by mkoeppe

  • Resolution set to invalid
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.