[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #5112 [Tor Client]: Tor fails to bind to socket, SOCK_CLOEXEC unsupported on 2.6.18 kernel

#5112: Tor fails to bind to socket, SOCK_CLOEXEC unsupported on 2.6.18 kernel
------------------------+---------------------------------------------------
 Reporter:  fob         |          Owner:  nickm              
     Type:  defect      |         Status:  accepted           
 Priority:  normal      |      Milestone:  Tor: 0.2.3.x-final 
Component:  Tor Client  |        Version:  Tor: 0.2.3.12-alpha
 Keywords:              |         Parent:                     
   Points:              |   Actualpoints:                     
------------------------+---------------------------------------------------
Changes (by nickm):

  * owner:  => nickm
  * status:  new => accepted
  * milestone:  => Tor: 0.2.3.x-final


Comment:

 As an aside, you're aware of this part, right:
 {{{
 Feb 13 21:06:55.032 [warn] This copy of Tor was compiled to run in a non-
 anonymous mode. It will provide NO ANONYMITY.
 }}}
 ?

 I think most people haven't run into this, because they don't build their
 Tor with one set of kernel headers (supporting SOCK_CLOEXEC), and then try
 to run it on a different kernel.  As a workaround, are you able to compile
 with a set of headers that don't have SOCK_CLOEXEC?

 In any case, we should fix this for 0.2.3.x-final.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5112#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs