On 23/06/2016 10:56 p.m., James Lay wrote:
> Ah...well I went with this repo:
> git clone https://github.com/openssl/openssl.git
> And the errors I posted were where I stoppedunfortunately I've
> already nuked the repo off the drive otherwise I'd give you the exact
> info. I can tell you I
On Thu, 2016-06-23 at 17:47 +1200, Amos Jeffries wrote:
> Yay that you got it going with LibreSSL.
>
> But I'm still interested in why you got the errors in the first place
> with OpenSSL. It is supposed to be the better supported one :-P
>
> So if you have the time to assist my edufication;
>
Yay that you got it going with LibreSSL.
But I'm still interested in why you got the errors in the first place
with OpenSSL. It is supposed to be the better supported one :-P
So if you have the time to assist my edufication;
what version OpenSSL was this exactly that you built against?
("git
It already has :)
Jun 22 09:41:09 gateway (squid-1): 192.168.1.109 - -
[22/Jun/2016:09:41:09 -0600] "CONNECT 31.13.76.84:443 HTTP/1.1"
i.instagram.com - 200 0 TAG_NONE:ORIGINAL_DST
Jun 22 15:09:26 gateway (squid-1): 192.168.1.109 - -
[22/Jun/2016:15:09:26 -0600] "CONNECT 31.13.76.84:443
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I suggest this will not solve your unknown cipher issue. :)
23.06.2016 3:12, James Lay пишет:
> Had zero issues when compiling against libressl-2.4.1. I now have ChaCha
> Poly cipher support...happy
days!
>
> James
>
> On 2016-06-22 13:29,
So yea...git pulled latest ssl, here's my results:
make[3]: Entering directory `/home/nobackup/build/squid-
3.5.19/src/anyp'
depbase=`echo PortCfg.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
/bin/bash ../../libtool --tag=CXX --mode=compile g++
-DHAVE_CONFIG_H -I../.. -I../../include
