#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