Re: ports requiring OpenSSL not honouring OpenSSL from ports

On 01.05.14 16:33, Paul Hoffman wrote:
> On May 1, 2014, at 3:03 AM, Uwe Doering <gemini@geminix.org> wrote:
> 
>> I indeed wondered why this variable hadn't been mentioned so far. Guys,
>> you do have "WITH_OPENSSL_PORT=yes" in your "/etc/make.conf", haven't you?
>>
>> Because otherwise the whole thread might be considered a false alert.
>> The ports system does not link with the ports' OpenSSL of its own
>> accord. Or at least not in a reliable/predictable manner. You have to
>> explicitly tell it what you want.
> 
> Please consider whether it is appropriate to chide people for not knowing about an *undocumented* feature of make.conf.

First of all, I certainly didn't intend to chide anyone, so I apologize
if some of you got the impression. Having worked with FreeBSD and the
ports system for years I was under the impression that this information
would be readily available in the docs.

But on further research it appears to me that this is indeed pretty well
hidden in only some mailing list and forum articles, where I probably
learned it from in the past.

Having realized that, I now wonder how many people run half-broken
systems because they didn't know about this and didn't notice the wrong
and sometimes even mixed linking of the OpenSSL libs.

> I'll turn in a pr for it.

Good idea. I would think that this should be mentioned at least in
"pkg-descr" of the "openssl" port, where it gets displayed by
"portmaster" and perhaps other port management tools after each install.

Best regards,

   Uwe
-- 
Uwe Doering
gemini@geminix.org
_______________________________________________
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"