]>
Commit | Line | Data |
---|---|---|
5634a5af | 1 | It looks like the 1.3 branch already has a more correct fix for this problem |
2 | (which has potential to crop up elsewhere in the source tree), but this fixes | |
3 | the most obvious one. | |
4 | ||
5 | --- mutt-1.2.5/imap/auth_gss.c Wed Jun 21 15:21:56 2000 | |
6 | +++ mutt-1.2.5/imap/auth_gss.c Mon Nov 6 13:24:27 2000 | |
7 | @@ -226,13 +226,15 @@ | |
8 | mutt_socket_write (idata->conn, buf1); | |
9 | ||
10 | /* Joy of victory or agony of defeat? */ | |
11 | - if (mutt_socket_read_line_d (buf1, GSS_BUFSIZE, idata->conn) < 0) | |
12 | - { | |
13 | - dprint (1, (debugfile, "Error receiving server response.\n")); | |
14 | - | |
15 | - mutt_socket_write(idata->conn, "*\r\n"); | |
16 | - return -1; | |
17 | - } | |
18 | + do { | |
19 | + if (mutt_socket_read_line_d (buf1, GSS_BUFSIZE, idata->conn) < 0) | |
20 | + { | |
21 | + dprint (1, (debugfile, "Error receiving server response.\n")); | |
22 | + mutt_socket_write(idata->conn, "*\r\n"); | |
23 | + return -1; | |
24 | + } | |
25 | + } while ((mutt_strncmp (buf1, seq, SEQLEN) != 0)); | |
26 | + | |
27 | if (imap_code (buf1)) | |
28 | { | |
29 | /* flush the security context */ |