Summary: | =net-misc/tor-0.2.6.7 - crashes with seccomp filter | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sam James <sam> |
Component: | Current packages | Assignee: | Anthony Basile <blueness> |
Status: | RESOLVED FIXED | ||
Severity: | critical | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://trac.torproject.org/projects/tor/ticket/16363 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sam James
2015-05-24 14:57:00 UTC
I didn't forget about this bug, but I wasn't able to reproduce it. I'm going to be rapid stabilizing tor-0.2.6.10 soon (like about one week or so). Can you test again and see if this is still an issue. If you keep hitting it, then its probably something on your system but we'll still want to track it down in case it has deeper implications. (In reply to Anthony Basile from comment #1) > I didn't forget about this bug, but I wasn't able to reproduce it. I'm > going to be rapid stabilizing tor-0.2.6.10 soon (like about one week or so). > Can you test again and see if this is still an issue. If you keep hitting > it, then its probably something on your system but we'll still want to track > it down in case it has deeper implications. I tested with tor-0.2.6.10 and found no issue with seccomp. Can you reopen this if you get more information about how to reproduce. Possibly this has been fixed since 0.2.6.7. (In reply to Anthony Basile from comment #2) > (In reply to Anthony Basile from comment #1) > > I didn't forget about this bug, but I wasn't able to reproduce it. I'm > > going to be rapid stabilizing tor-0.2.6.10 soon (like about one week or so). > > Can you test again and see if this is still an issue. If you keep hitting > > it, then its probably something on your system but we'll still want to track > > it down in case it has deeper implications. > > I tested with tor-0.2.6.10 and found no issue with seccomp. Can you reopen > this if you get more information about how to reproduce. Possibly this has > been fixed since 0.2.6.7. This is fixed in 0.2.6.10. See upstream issue #16363 in the URL above. |