[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Recommended combinations tor/ssl/libevent
- To: or-dev@xxxxxxxxxxxxx
- Subject: Re: Recommended combinations tor/ssl/libevent
- From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
- Date: Mon, 8 Nov 2010 16:21:39 -0500
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-dev-outgoing@xxxxxxxx
- Delivered-to: or-dev@xxxxxxxx
- Delivery-date: Mon, 08 Nov 2010 16:21:47 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=LvNWEwtlL3FwL/5RyRsDpcfCSpJ0Cthkqayae6Oekk8=; b=mktd6EycE4r/MgFEum1hUdXs5S/eqF6Orp+f7xuTvJ0kWIfnpZyhYJ1xeYrIkQGVxk hYr3Aj4Ki7oYnm/qIC/fvLN3Bbe5UteEMIRUVWILARYkzXYA10GoZ9lj+YokUU31FquP jGQeLT8vu99TGQ31Pm5sX6WeEhsNVRiIGMG5M=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=mSGd8SrUD9bAhfIxgPj6nes/OrdKwmdKv15swELYhsmrwro9sBnxeD/q4bU6LdfQin cvbhRMX1kB+2yIR4QT3K3BdkF0O6BA9eP90BVIxYwhuWsvASWnNu2oYQ+Eb7AoErLqr9 YivqYy3bVzBknC714F4VO5EdHmxeBiTgiv0rI=
- In-reply-to: <20101108151530.GA93101@tabulara>
- References: <20101108151530.GA93101@tabulara>
- Reply-to: or-dev@xxxxxxxxxxxxx
- Sender: owner-or-dev@xxxxxxxxxxxxx
On Mon, Nov 8, 2010 at 10:15 AM, Hans Schnehl <torvallenator@xxxxxxxxx> wrote:
>
> Hi all,
>
> see exempt from coredump of a v0.2.2.12-alpha-dev, which was happily
> running until 5 days ago.
> Which versions of libevent, openssh , tor itself are known to be co-working
> nicely nowadays ?
I'd guess that your problem there is the Tor version: The latest
0.2.2.x alpha code, or the latest maint-0.2.2 git head, should be much
better than anything from back in April. If you're going to use alpha
releases, you should probably try to keep up-to-date: knowing that
there was a bug in 0.2.2.12-alpha at this point doesn't really help us
much unless we know whether it is also a bug in the latest 0.2.2.x.
This goes doubly for "-dev" versions (versions based on the state of
the Git repository between releases): if you want to checkpoint the
state of Tor development then ignore it for half a year, I'd strondly
suggest checkpointing at an actually released version that works for
you.
For Libevent, I personally recommend the latest 2.0.x, or at least
1.4.12-stable or later. 1.3e should work in a pinch too, if you
really must.
Tor doesn't use openssh; it uses openssl. Most vendor versions should
work assuming they claim to be 0.9.7x or later. If you can't use your
vendor's shipped version, I personally recommend the latest 0.9.8x
release or the latest 1.0.0x release.
(These are my recommended versions, not an exhaustive list of
known-to-work versions. To the best of my knowledge, nobody has
compiled such a list.)
--
Nick