Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 08 Nov 2016 18:59:30 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 203014] security/tor and security/tor-devel: Update and fix a few problems
Message-ID:  <bug-203014-13-wm0q4bMrAW@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203014-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-203014-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203014

Vin=C3=ADcius Zavam <egypcio@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #176119|0                           |1
        is obsolete|                            |

--- Comment #36 from Vin=C3=ADcius Zavam <egypcio@googlemail.com> ---
Created attachment 176798
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D176798&action=
=3Dedit
[PATCH] security/tor-devel: r425755

(In reply to Yuri Victorovich from comment #35)

Yuri,
hi.

Please take a look at this new patch when you have some time. It also updat=
es
security/tor-devel to version 0.2.9.5-alpha.

This one is pretty much close to the best practices described by the Porter=
's
Handbook, and let the user chose between 'ssl=3Dbase' or any other from por=
ts.
There's also the considerations pointed by brnrd@ (I think), to set USES+=
=3Dssl
only when we try to compile Tor using ports' openssl/libressl from ports.

I added/merged your warning about Tor2Web, as reported (and solved) on #210=
389.

KR,
Vin=C3=ADcius

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203014-13-wm0q4bMrAW>