Re: [tor-bugs] #21369 [Core Tor/Tor]: Tor crashes with tor_assertion_failed_() [Assertion buf->datalen < INT_MAX failed in write_to_buf at ../src/or/buffers.c:832]

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#21369: Tor crashes with tor_assertion_failed_() [Assertion buf->datalen < INT_MAX
failed in write_to_buf at ../src/or/buffers.c:832]
-------------------------------------------+-------------------------------
 Reporter:  svengo                         |          Owner:  nickm
     Type:  defect                         |         Status:  needs_review
 Priority:  Very High                      |      Milestone:  Tor:
                                           |  0.3.0.x-final
Component:  Core Tor/Tor                   |        Version:  Tor: 0.2.9.9
 Severity:  Critical                       |     Resolution:
 Keywords:  029-backport, review-group-16  |  Actual Points:
Parent ID:                                 |         Points:
 Reviewer:                                 |        Sponsor:
-------------------------------------------+-------------------------------

Comment (by svengo):

 Replying to [comment:4 nickm]:
 > How is this Tor configured?  Is it a relay, a hidden service, a client?
 Can you paste the torrc (or as much of it as is not private)?

 Eriador is a simple, no exit relay. Here is my configuration:

 {{{
 sven@arnor:~$ cat /var/run/tor-instances/eriador.defaults
 DataDirectory /var/lib/tor-instances/eriador
 PidFile /var/run/tor-instances/eriador/tor.pid
 RunAsDaemon 0
 User _tor-eriador
 SyslogIdentityTag eriador

 ControlSocket /var/run/tor-instances/eriador/control GroupWritable
 RelaxDirModeCheck
 SocksPort unix:/var/run/tor-instances/eriador/socks WorldWritable

 CookieAuthentication 1
 CookieAuthFileGroupReadable 1
 CookieAuthFile /var/run/tor-instances/eriador/control.authcookie

 Log notice syslog
 }}}


 {{{
 sven@arnor:~$ cat /etc/tor/instances/eriador/torrc
 # This is the tor configuration file for tor instance eriador.
 #
 # To start/reload/etc this instance, run "systemctl tor@eriador start" (or
 reload, or..).
 # This instance will run as user _tor-eriador; its data directory is
 /var/lib/tor-instances/eriador.
 #
 # Append to the list of socks interfaces configured via
 # /usr/share/tor/tor-service-defaults-torrc-instances
 # which is unix:/var/run/tor-instances/eriador/socks

 +SocksPort auto

 #ControlPort 9051
 HashedControlPassword
 16:CBBCB54F3924BCA06001CFBFE8C15F7D8DDB768CE9B34E567E6A36303B
 ORPort 4051
 Nickname eriador
 ContactInfo hwertiout695@xxxxxxxxxxxxx
 DirPort 4951
 ExitPolicy reject *:* # no exits allowed
 NumCPUs 2
 EntryStatistics 1
 ConnDirectionStatistics 1
 HiddenServiceStatistics 1
 DirReqStatistics 1
 MyFamily 9FBEB75E8BC142565F12CBBE078D63310236A334

 # IPv6
 ORPort [2001:41d0:1:8989::1]:4051
 DirPort [2001:41d0:1:8989::1]:4951 NoAdvertise
 }}}

 The bug has not occurred since then. The machine has many free resources
 (4 cpu cores), so this cannot be the problem:

 {{{
 sven@arnor:~$ uptime
  16:28:00 up 12 days, 12:27,  1 user,  load average: 0,41, 0,46, 0,45
 sven@arnor:~$ free
               total        used        free      shared  buff/cache
 available
 Mem:       16337668      822700    13083000      183580     2431968
 14917912
 Swap:       1046524           0     1046524
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21369#comment:12>
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