On 12/31/09, J.C. Roberts <[email protected]> wrote: > On Wed, 30 Dec 2009 17:56:03 -0500 nixlists <[email protected]> wrote: > >> On 12/30/09, Tasmanian Devil <[email protected]> wrote: >> >>> Changes in version 0.2.1.21 - 2009-12-21 >> >> >> >> Downloaded, installed - same exact problem. Tried -alpha as well. >> >> Same problem. I assumed alpha worked... >> > >> > You're right! It seems I did give you bad advice. I'm sorry about >> > that! >> > >> > I tried on a patched 4.6 machine, and my tor-0.2.2.6-alpha port >> > which works fine on -current doesn't work on a patched 4.6. So the >> > only options I see to run Tor on 4.6 at the moment is either not to >> > patch OpenSSL or to upgrade to -current. >> > >> > Tas. >> >> Can't I use OpenSSL version from -current and force tor to use those >> libraries on 4.6 instead of the system libcrypto/libssl somehow? How >> would one go about doing that? > > Mixing and matching -CURRENT with -STABLE or -RELEASE is pure evil. > > Every overly curious person on this list has made this mistake, at > least once. You will learn from this mistake/experiment, because you > will make a serious mess. > > The right answer is backup your data, and do a fresh install of the > most recent -CURRENT snapshot.
I don't want to do that on this particular machine.... Oh well
