- Apr 29, 2018
-
-
akwizgran authored
Update transport keys in-place to retain key set IDs Closes #1213 See merge request akwizgran/briar!779
-
Torsten Grote authored
Don't make or accept Bluetooth contact connections during key agreement See merge request akwizgran/briar!770
-
Torsten Grote authored
IntroduceeProtocolEngine uses wrong role when adding keys See merge request akwizgran/briar!780
- Apr 28, 2018
-
-
Torsten Grote authored
Don't automatically respond to declined introductions See merge request akwizgran/briar!777
- Apr 27, 2018
-
-
akwizgran authored
Fix introduction response messages in UI and some minor fixes Closes #923 See merge request akwizgran/briar!776
-
Torsten Grote authored
-
Torsten Grote authored
Send automatic decline when other introducee declines See merge request akwizgran/briar!775
-
Torsten Grote authored
New Introduction Protocol Closes #308, #377, #474, and #613 See merge request akwizgran/briar!758
-
Torsten Grote authored
This will be changed once we have a way to reset state for peers that were contacts already at some point in the past. One contact might have deleted the other, but not vice versa. So they have mismatching state that needs to be reset. See #2 for more information.
-
Torsten Grote authored
- Apr 26, 2018
-
-
Torsten Grote authored
-
Torsten Grote authored
It is possible that a remote DECLINE message arrives short before the user responds to the introduction. This will cause a ProtocolStateException which (for now) is just caught and a generic (existing) error message will be shown.
-
Torsten Grote authored
Previously, DECLINE messages let directly to the START state for introducer and introducees. So incoming ACCEPT and DECLINE messages needed to be ignored in START state introducing undefined behavior into the protocol. This is fixed with this commit by adding two additional states to the introducer state machine as well as making use of the existing LOCAL_DECLINED state for the introducees.
-
Torsten Grote authored
A fake ACTIVATE message would cause us to activate the transport keys before the contact has received our auth message, which would compromise forward secrecy.
-
Torsten Grote authored
Previously, the introducer would process and forward invalid messages by the introducees. This commit adds the necessary checks and tests.
-
- Apr 25, 2018
-
-
Torsten Grote authored
-
Torsten Grote authored
-
Torsten Grote authored
When the user attempts an introduction, instead of the introduction message input field, an explanatory text will be shown and the introduction can not be made until the last one has been finished.
-
Torsten Grote authored
-
Torsten Grote authored
-
Torsten Grote authored
Closes #308
-