Opened 13 years ago

#11 closed defect (Fixed)

flush command deletes all messages in client queue and doesn't deliver them.

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

Description

[Moved from bugzilla]
Reporter: qumqats@ouDescription:
Opened: 2003-10-19 04:44



the latext CVS trunk code appears to not be able to send messages to
the 0.0.5.1 nodes. and even worst it deletes the messages out of the
client queue when it can't deliver them. these are messages that were
put into the client queue using 0.0.5.1 if I try sending a message
in 0.0.6 I still get an error and the message isn't in the queue.

$ ../bin/mixminion flush
Mixminion version 0.0.6alpha1
This software is for testing purposes only. Anonymity is not guaranteed.
Oct 18 19:32:25.690 [INFO] Flushing message queue
Oct 18 19:32:25.728 [INFO] Found 913 pending messages
Oct 18 19:32:25.728 [INFO] Flushing 913
Oct 18 19:32:26.997 [INFO] Sending 29 messages to 213.130.163.34:48099...
Oct 18 19:32:27.030 [INFO] Connecting...
Oct 18 19:32:27.393 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:27.394 [INFO] Error was: TLSClosed error while connecting to 213.
130.163.34:48099:
Oct 18 19:32:29.764 [INFO] Sending 9 messages to 62.109.74.123:48099...
Oct 18 19:32:29.766 [INFO] Connecting...
Oct 18 19:32:30.190 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:30.191 [INFO] Error was: TLSClosed error while connecting to 62.
109.74.123:48099:
Oct 18 19:32:30.753 [INFO] Sending 26 messages to 69.55.238.167:48099...
Oct 18 19:32:30.754 [INFO] Connecting...
Oct 18 19:32:30.836 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:30.837 [INFO] Error was: TLSClosed error while connecting to 69.55.
238.167:48099:
Oct 18 19:32:33.585 [INFO] Sending 27 messages to 62.245.184.24:48099...
Oct 18 19:32:33.586 [INFO] Connecting...
Oct 18 19:32:34.050 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:34.051 [INFO] Error was: TLSClosed error while connecting to 62.
245.184.24:48099:
Oct 18 19:32:35.761 [INFO] Sending 27 messages to 18.244.0.188:48099...
Oct 18 19:32:35.762 [INFO] Connecting...
Oct 18 19:32:35.963 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:35.963 [INFO] Error was: TLSClosed error while connecting to 18.
244.0.188:48099:
Oct 18 19:32:37.660 [INFO] Sending 119 messages to 66.92.65.81:48099...
Oct 18 19:32:37.662 [INFO] Connecting...
Oct 18 19:32:37.774 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:37.775 [INFO] Error was: Error connecting: (61, 'Connection
refused')
Oct 18 19:32:44.879 [INFO] Sending 120 messages to 208.210.149.14:48100...
Oct 18 19:32:44.881 [INFO] Connecting...
Oct 18 19:32:44.962 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:44.963 [INFO] Error was: Error connecting: (61, 'Connection
refused')
Oct 18 19:32:52.608 [INFO] Sending 27 messages to 64.142.31.83:48099...
Oct 18 19:32:52.609 [INFO] Connecting...
Oct 18 19:32:52.742 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:52.743 [INFO] Error was: TLSClosed error while connecting to 64.
142.31.83:48099:
Oct 18 19:32:54.451 [INFO] Sending 27 messages to 193.111.87.14:48099...
Oct 18 19:32:54.452 [INFO] Connecting...
Oct 18 19:32:54.539 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:54.540 [INFO] Error was: TLSClosed error while connecting to 193.
111.87.14:48099:
Oct 18 19:32:56.250 [INFO] Sending 28 messages to 24.62.130.57:48100...
Oct 18 19:32:56.252 [INFO] Connecting...
Oct 18 19:32:57.705 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:57.706 [INFO] Error was: TLSClosed error while connecting to 24.62.
130.57:48100:
Oct 18 19:32:59.415 [INFO] Sending 27 messages to 69.9.134.82:48099...
Oct 18 19:32:59.416 [INFO] Connecting...
Oct 18 19:32:59.534 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:32:59.535 [INFO] Error was: TLSClosed error while connecting to 69.9.
134.82:48099:
Oct 18 19:33:01.003 [INFO] Sending 25 messages to 140.247.60.128:48099...
Oct 18 19:33:01.005 [INFO] Connecting...
Oct 18 19:33:01.196 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:33:01.197 [INFO] Error was: TLSClosed error while connecting to 140.
247.60.128:48099:
Oct 18 19:33:02.836 [INFO] Sending 27 messages to 80.177.168.205:48099...
Oct 18 19:33:02.837 [INFO] Connecting...
Oct 18 19:33:03.240 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:33:03.241 [INFO] Error was: TLSClosed error while connecting to 80.
177.168.205:48099:
Oct 18 19:33:04.979 [INFO] Sending 30 messages to 18.244.0.188:48100...
Oct 18 19:33:04.981 [INFO] Connecting...
Oct 18 19:33:05.170 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:33:05.171 [INFO] Error was: TLSClosed error while connecting to 18.
244.0.188:48100:
Oct 18 19:33:07.045 [INFO] Sending 120 messages to 213.73.91.34:48099...
Oct 18 19:33:07.046 [INFO] Connecting...
Oct 18 19:33:27.052 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:33:27.052 [INFO] Error was:
Oct 18 19:33:34.952 [INFO] Sending 26 messages to 207.36.86.132:48099...
Oct 18 19:33:34.953 [INFO] Connecting...
Oct 18 19:33:35.175 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:33:35.176 [INFO] Error was: TLSClosed error while connecting to 207.
36.86.132:48099:
Oct 18 19:33:36.818 [INFO] Sending 27 messages to 80.0.174.191:48099...
Oct 18 19:33:36.819 [INFO] Connecting...
Oct 18 19:33:37.205 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:33:37.205 [INFO] Error was: TLSClosed error while connecting to 80.0.
174.191:48099:
Oct 18 19:33:38.728 [INFO] Sending 27 messages to 66.79.46.86:48099...
Oct 18 19:33:38.729 [INFO] Connecting...
Oct 18 19:33:38.995 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:33:38.995 [INFO] Error was: TLSClosed error while connecting to 66.79.
46.86:48099:
Oct 18 19:33:40.682 [INFO] Sending 27 messages to 65.31.179.120:48099...
Oct 18 19:33:40.683 [INFO] Connecting...
Oct 18 19:33:40.898 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:33:40.899 [INFO] Error was: TLSClosed error while connecting to 65.31.
179.120:48099:
Oct 18 19:33:42.559 [INFO] Sending 26 messages to 216.218.240.134:48099...
Oct 18 19:33:42.560 [INFO] Connecting...
Oct 18 19:33:42.624 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:33:42.625 [INFO] Error was: TLSClosed error while connecting to 216.
218.240.134:48099:
Oct 18 19:33:44.180 [INFO] Sending 29 messages to 213.146.114.96:48099...
Oct 18 19:33:44.182 [INFO] Connecting...
Oct 18 19:34:43.817 [INFO] ... messages sent
Oct 18 19:34:45.681 [INFO] Sending 29 messages to 24.62.130.57:48099...
Oct 18 19:34:45.681 [INFO] Connecting...
Oct 18 19:34:47.342 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:34:47.343 [INFO] Error was: TLSClosed error while connecting to 24.62.
130.57:48099:
Oct 18 19:34:49.101 [INFO] Sending 27 messages to 66.93.100.200:48099...
Oct 18 19:34:49.102 [INFO] Connecting...
Oct 18 19:34:49.343 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:34:49.344 [INFO] Error was: TLSClosed error while connecting to 66.93.
100.200:48099:
Oct 18 19:34:50.967 [INFO] Sending 27 messages to 208.42.19.154:39287...
Oct 18 19:34:50.968 [INFO] Connecting...
Oct 18 19:34:51.195 [INFO] Error while delivering messages; leaving in queue
Oct 18 19:34:51.196 [INFO] Error was: TLSClosed error while connecting to 208.
42.19.154:39287:
Oct 18 19:34:52.743 [INFO] Queue flushed
$ ../bin/mixminion flush
Mixminion version 0.0.6alpha1
This software is for testing purposes only. Anonymity is not guaranteed.
Oct 18 19:35:32.820 [INFO] Flushing message queue
Oct 18 19:35:32.826 [INFO] Found 0 pending messages
Oct 18 19:35:32.827 [INFO] Flushing 0
Oct 18 19:35:32.828 [INFO] Queue flushed
$

$ bin/mixminion send -t qumqats@…
Mixminion version 0.0.6alpha1
This software is for testing purposes only. Anonymity is not guaranteed.
Oct 18 19:39:08.500 [WARN] This software is newer than any version on the
recommended list.
Enter your message now. Type Ctrl-D when you are done.
sdf
sdf
sda
asd

.
Oct 18 19:39:17.144 [INFO] Generating payload(s)...
Oct 18 19:39:17.169 [INFO] Selected path is moria1,chicago,cside,Tonga:typhaon,
moria1,mercurio,aarg
Oct 18 19:39:17.636 [INFO] Message queued
Oct 18 19:39:17.637 [INFO] Connecting...
Oct 18 19:39:17.828 [INFO] Error while delivering message; leaving in queue
Oct 18 19:39:17.829 [INFO] Error was: TLSClosed error while connecting to 18.
244.0.188:48099:
$
$
$ ls -al .mixminion/queue
total 58
drwx------ 2 minion minion 22528 Oct 18 19:39 .
drwx------ 16 minion minion 512 Oct 18 19:39 ..
-rw------- 1 minion minion 32906 Oct 18 17:22 inp_y-wLWCF0
$
$ bin/mixminion flush
Mixminion version 0.0.6alpha1
This software is for testing purposes only. Anonymity is not guaranteed.
Oct 18 19:41:55.952 [INFO] Flushing message queue
Oct 18 19:41:55.958 [INFO] Found 0 pending messages
Oct 18 19:41:55.959 [INFO] Flushing 0
Oct 18 19:41:55.960 [INFO] Queue flushed
$



I'm pretty sure that this was because of a TLS bug fixed by the checkin of
2003/10/19 to tls.c. From the CVS log:

The spec says that we should support an alternative (and more common)
crypto suite for client-to-server communications. The alternative
suite is only present in SSL3; the preferred one is in TLS1.

Older versions of the code are configured to generate only TLS1
connections -- and (previously unknown to me) accept only TLS1
connections. To do the right thing, we need to accept TLS1 and SSL3,
but generate only TLS1. This patch does that.

Please verify that this bug is gone for you. :)tel.org (Joel M. Baldwin)

[Automatically added by flyspray2trac: Operating System: FreeBSD]

Child Tickets

Change History (1)

comment:1 Changed 13 years ago by weasel

flyspray2trac: bug closed.

Note: See TracTickets for help on using tickets.