Opened 14 years ago

#9 closed defect (Fixed)

Client MMTP timeouts don't really work

Reported by: weasel Owned by: nickm
Priority: Low Milestone:
Component: Mixminion-Client Version: unspeficied
Severity: Keywords:
Cc: weasel Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

[Moved from bugzilla]
Reporter: nickm@… (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.



This has been fixed by the MMTP rewrite in 0.0.7.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (1)

comment:1 Changed 14 years ago by weasel

flyspray2trac: bug closed.

Note: See TracTickets for help on using tickets.