Make tor_check_port_forwarding handle incomplete lines
The code for parsing the output of tor-fw-helper uses fgets() on a non-blocking file descriptor to fetch each line of output. This appears to not handle incomplete lines properly. Rather than buffering data until a complete line is returned, fgets will return an incomplete line and set errno to be EAGAIN. fgets() should be replaced with something which can handle incomplete lines.
Issue was originally raised by nickm in bug #1903 (moved) and there is some further discussion in that ticket.
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Steven Murdoch changed milestone to %Tor: 0.3.1.x-final
changed milestone to %Tor: 0.3.1.x-final
Trac:
Milestone: N/A to Tor: 0.2.3.x-final- Author
There is a corresponding problem in Windows, with log_from_handle(). A fix to this bug should also be applied to fix the Windows case too.
Trac:
Actualpoints: N/A to N/A
Points: N/A to N/A - Author
Trac:
Status: new to accepted - Author
Trac:
Status: accepted to assigned - Author
My progress on this can be found in https://trac.torproject.org/projects/tor/ticket/2045
Currently it doesn't compile (and is incomplete), so needs squashing before being merged.
Wait, the link you provided here points back to this page. Where did you really want to link to?
- Author
Replying to Sebastian:
Wait, the link you provided here points back to this page. Where did you really want to link to?
Oops, I meant https://gitweb.torproject.org/sjm217/tor.git/shortlog/refs/heads/bug2045
Trac:
Parent: #1775 (moved) to N/A
Milestone: Tor: 0.2.3.x-final to Tor: 0.2.4.x-finalTrac:
Keywords: N/A deleted, tor-relay addedTrac:
Component: Tor Relay to TorTrac:
Milestone: Tor: 0.2.4.x-final to Tor: 0.2.5.x-finalTrac:
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.???- Author
I'm unlikely to have time in the near future to do this. Sorry.
Trac:
Status: assigned to new Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.
Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecifiedRemove an old triaging keyword.
Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A addedI think we fixed this when we fixed #21654 (moved)
Trac:
Cc: N/A to ahf
Milestone: Tor: unspecified to Tor: 0.3.1.x-final
Resolution: N/A to fixed
Status: new to closedReplying to sjmurdoch:
There is a corresponding problem in Windows, with log_from_handle(). A fix to this bug should also be applied to fix the Windows case too.
Did the #21654 (moved) fix resolve the Windows log_from_handle() case too?
Opened #22380 (moved) to handle that case.
(edited to fix bug number)
- Trac closed
closed
- Steven Murdoch mentioned in issue #2046 (moved)
mentioned in issue #2046 (moved)
- cypherpunks mentioned in issue #12503 (moved)
mentioned in issue #12503 (moved)
- Alexander Hansen Færøy mentioned in issue #21654 (moved)
mentioned in issue #21654 (moved)
- Nick Mathewson mentioned in issue #21757 (moved)
mentioned in issue #21757 (moved)
- Nick Mathewson mentioned in issue #22380 (moved)
mentioned in issue #22380 (moved)
- Trac moved to tpo/core/tor#2045 (closed)
moved to tpo/core/tor#2045 (closed)
- Trac mentioned in issue tpo/core/tor#12503 (closed)
mentioned in issue tpo/core/tor#12503 (closed)
- Trac mentioned in issue tpo/core/tor#22380 (closed)
mentioned in issue tpo/core/tor#22380 (closed)