aboutsummaryrefslogtreecommitdiff
path: root/src/cadet
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2017-02-19 00:28:17 +0100
committerChristian Grothoff <christian@grothoff.org>2017-02-19 00:28:17 +0100
commit5afc3372aec888e2db988ad30a889c4bc842e5ac (patch)
treeae273b229bac1c0d31107fd174ad1b0098728382 /src/cadet
parent6f8fabef01d53234928a2c766fe19b0bbb00a2a2 (diff)
downloadgnunet-5afc3372aec888e2db988ad30a889c4bc842e5ac.tar.gz
gnunet-5afc3372aec888e2db988ad30a889c4bc842e5ac.zip
trying to fix #4899
Diffstat (limited to 'src/cadet')
-rw-r--r--src/cadet/gnunet-service-cadet-new_tunnels.c17
1 files changed, 15 insertions, 2 deletions
diff --git a/src/cadet/gnunet-service-cadet-new_tunnels.c b/src/cadet/gnunet-service-cadet-new_tunnels.c
index f0ab86431..26983d465 100644
--- a/src/cadet/gnunet-service-cadet-new_tunnels.c
+++ b/src/cadet/gnunet-service-cadet-new_tunnels.c
@@ -3008,8 +3008,21 @@ GCT_handle_encrypted (struct CadetTConnection *ct,
3008 case CADET_TUNNEL_KEY_UNINITIALIZED: 3008 case CADET_TUNNEL_KEY_UNINITIALIZED:
3009 case CADET_TUNNEL_KEY_AX_RECV: 3009 case CADET_TUNNEL_KEY_AX_RECV:
3010 /* We did not even SEND our KX, how can the other peer 3010 /* We did not even SEND our KX, how can the other peer
3011 send us encrypted data? */ 3011 send us encrypted data? Must have been that we went
3012 GNUNET_break_op (0); 3012 down and the other peer still things we are up.
3013 Let's send it KX back. */
3014 GNUNET_STATISTICS_update (stats,
3015 "# received encrypted without any KX",
3016 1,
3017 GNUNET_NO);
3018 if (NULL != t->kx_task)
3019 {
3020 GNUNET_SCHEDULER_cancel (t->kx_task);
3021 t->kx_task = NULL;
3022 }
3023 send_kx (t,
3024 ct,
3025 &t->ax);
3013 return; 3026 return;
3014 case CADET_TUNNEL_KEY_AX_SENT_AND_RECV: 3027 case CADET_TUNNEL_KEY_AX_SENT_AND_RECV:
3015 /* We send KX, and other peer send KX to us at the same time. 3028 /* We send KX, and other peer send KX to us at the same time.