Tor 0.2.1.26-1~~lenny+1: segfault with libcryto.so.0.9.8

[Robert Ransom]

On Fri, 19 Nov 2010 09:44:47 +0100
Paul Menzel <paulepanter at users.sourceforge.net> wrote:

> Am Mittwoch, den 17.11.2010, 12:04 -0500 schrieb Roger Dingledine:
> > On Wed, Nov 17, 2010 at 11:45:32AM -0500, Nick Mathewson wrote:
> > > > I noticed that Tor had crashed on my system. I am using Debian Lenny
> > > > with Tor 0.2.1.26-1~~lenny+1. The only thing I could find out about this
> > > > crash is the following line running `dmesg`.
> > > >
> > > Without more information, there's not much info to go on there to
> > > diagnose the problem.  Generally, to debug a segfault, we need a stack
> > > trace.  To get one of those, make sure you're running Tor with
> > > coredumps enabled, and use gdb to get a trace if Tor crashes again.
> > 
> > On Debian, you want to apt-get install tor-dbg, so you get the symbols
> > for the Tor binary.
> 
> I did so now.
> 
> 	sudo aptitude install tor-dbg
> 
> (Aptitude is the recommended package manager by Debian since Lenny.)
> 
> > You might even have a core file already sitting in your datadirectory,
> > which I think is /var/lib/tor/
> 
> Yes, I have. Two of them actually. They are 60 MB and 117 MB big. Is it
> safe to make them publicly available somewhere?

No.  The core dumps contain all session keys and secret keys which Tor
was using at the time, and those must not be disclosed.

>                                                 Are they of use for
> someone since no debug symbols were installed when the core dumps were
> created?

If you have installed the debug symbol package corresponding to the
version of Tor, yes, they are useful.  Use GDB or one of its frontends
to print a traceback from the core.  The traceback should be safe to
disclose.


Robert Ransom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-talk/attachments/20101119/1bb1f2b5/attachment.pgp>