#46651: openssl @1.0.1k_0: add variants --------------------------+------------------- Reporter: uri@… | Owner: mww@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: openssl | --------------------------+------------------- Comment (by uri@…): Replying to [comment:1 larryv@…]:

The portfile you attached is basically illegible.

My fault. Though I did run "port lint --nitpick openssl", and everything was fine: {{{ $ port lint --nitpick openssl ---> Verifying Portfile for openssl ---> 0 errors and 0 warnings found. }}}

As per [https://guide.macports.org/#project.contributing.updates The Guide], please attach a diff against the current portfile instead.

Attaching file "openssl-port.diff". Hope it is fine now.

What benefit does linking against GMP provide, and are there good reasons why a user might //not// want this?

The benefits would be getting better performance on big number crunching (such as in RSA algorithm) provided by GMP library. The reason not to want this IMHO would be lack of performance gain - if on a given platform OpenSSL native BN (bignum) implementation outperforms GMP.

Same question for enabling the deprecated algorithms.

One benefit would be ability to use those older algorithms when there's a need if there's a need (plus algorithm freaks that just want to be able to use whatever there is whenever they want it :). A reason //not// to want it would be if the user does not have a need for those algorithms - in which case it would be safer to avoid carrying around the weaker code altogether, lest by chance somebody misconfigures it and results in a "product" communication under-protected. Please don't hesitate to ask more, especially if my explanations are less than crisp. -- Ticket URL: <https://trac.macports.org/ticket/46651#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

#46651: openssl @1.0.1k_0: add variants --------------------------+---------------------- Reporter: uri@… | Owner: larryv@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: openssl | --------------------------+---------------------- Changes (by jmr@…): * owner: mww@… => larryv@… * cc: cal@… (removed) * cc: cal@… (added) -- Ticket URL: <https://trac.macports.org/ticket/46651#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X

#46651: openssl @1.0.1k_0: add variants --------------------------+---------------------- Reporter: uri@… | Owner: larryv@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: openssl | --------------------------+---------------------- Comment (by cal@…): You can use a subversion checkout instead of the normal ports tree. That way changes get merged automatically and your local changes don't get overwritten on sync. Obviously, that comes with the occasional merge conflict you'll have to fix manually. wiki:howto/SyncingWithSVN has more info. -- Ticket URL: <https://trac.macports.org/ticket/46651#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X

#46651: openssl @1.0.1k_0: add variants --------------------------+---------------------- Reporter: uri@… | Owner: larryv@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: openssl | --------------------------+---------------------- Comment (by cal@…): Yes, unfortunately that is the case. -- Ticket URL: <https://trac.macports.org/ticket/46651#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

#46651: openssl @1.0.1k_0: add variants --------------------------+---------------------- Reporter: uri@… | Owner: larryv@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: openssl | --------------------------+---------------------- Comment (by uri@…): My apologies - I'm not sure I completely understand. My goal (ideal) is to be able to have Macports deal with all its ports "normally", i.e. having {{{ sudo port selfupdate && sudo port upgrade outdated }}} work as before. For one port - openssl - I want it to both track the main port and to apply my specific patch (at least until I can convince Dr. Henson that supporting a quirk of Apple Certificate Assistant is a good thing :). It looks like the only way to have the openssl port accommodate my patch is using SVN to pull it in. How (if at all) can I accomplish the above - have all (most :) of the Macports-served ports maintained normally, but this one port going through SVN? Thanks! -- Ticket URL: <https://trac.macports.org/ticket/46651#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X

#46651: openssl @1.0.1k_0: add variants --------------------------+---------------------- Reporter: uri@… | Owner: larryv@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: wontfix | Keywords: Port: openssl | --------------------------+---------------------- Changes (by cal@…): * status: new => closed * resolution: => wontfix Comment: attachment:openssl-port.diff references a `patch-null-absent.diff` patchfile that you haven't attached. Additionally: - JPAKE support has been removed upstream - GMP support has been removed upstream - I don't want to provide an option to support outdated algorithms for the same reason we're not providing a variant to re-enable SSLv3. -- Ticket URL: <https://trac.macports.org/ticket/46651#comment:12> MacPorts <https://www.macports.org/> Ports system for macOS