Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #9

Closed
Open
Created Nov 14, 2004 by weasel (Peter Palfrader)@weasel

Client MMTP timeouts don't really work

[Moved from bugzilla] Reporter: nickm@alum.mit.edu (Nick Mathewson)

Description: Opened: 2003-10-17 13:28

Right now, client MMTP connections only timeout while the connect(2) call is in progress. But there is no good way (other than alarm(2)) to have blocking TLS connections timeout.

The symptom is: connect to server that accepts a TCP connection, but that never completes any TLS operations. The client will block forever.

For now, I'm implementing alarm() for a quick fix. But that will penalize slow servers, and isn't a good long-term solution.

The real answer is probably to rewrite the client and server connection to both use a common set of nonblocking IO calls.

------- Additional Comments From Nick Mathewson 2004-01-27 01:57 -------

This has been fixed by the MMTP rewrite in 0.0.7.

[Automatically added by flyspray2trac: Operating System: All]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking