> In the meantime, I guess we're at a standoff.
> "What the fuck, freebsd? Why did you break a system library?"
Until FreeBSD updates their base, include a note in the source
release build docs in big block letters: BUILDING TOR ON FREEBSD...
That caveat and instructions would hopefully registe
> (when I no more could use tor)
You need to update openssl. Check the list archives for this month
about how to successfully do that using either canonical sources or
freebsd ports.
> Right. Unfortunately, it seems that FreeBSD patched openssl in such a way
> that it is entirely impossible for
On Fri, Jan 08, 2010 at 09:41:56PM +0100, Sebastian Hahn wrote:
> On Jan 8, 2010, at 6:45 PM, Luis Maceira wrote:
> > The well-known TLS renegotiating error which the tor-0.2.1.21
> > version was supposed to address persists on FreeBSD-8.0 updated as
> > of today.The unstable version (0.2.2.6)
On Fri, 8 Jan 2010 21:41:56 +0100 Sebastian Hahn
wrote:
>On Jan 8, 2010, at 6:45 PM, Luis Maceira wrote:
>
>> The well-known TLS renegotiating error which the tor-0.2.1.21 =20
>> version was supposed to address persists on FreeBSD-8.0 updated as =20
>> of today.The unstable version (0.2.2.6)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 8, 2010, at 6:45 PM, Luis Maceira wrote:
The well-known TLS renegotiating error which the tor-0.2.1.21
version was supposed to address persists on FreeBSD-8.0 updated as
of today.The unstable version (0.2.2.6) same thing the error
persi
The well-known TLS renegotiating error which the tor-0.2.1.21 version was
supposed to address persists on FreeBSD-8.0 updated as of today.The unstable
version (0.2.2.6) same thing the error persists (On Linux and using tor-0.2.2.6
the error does not exist -I had this error only on Debian Testing
6 matches
Mail list logo
