Changes between Initial Version and Version 1 of Ticket #906, comment 10


Ignore:
Timestamp:
06/26/17 06:32:38 (5 years ago)
Author:
Steffan Karger
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #906, comment 10

    initial v1  
    55I can think of several ways to resolve this particular bug, but find it hard what to pick.  Two good candidates:
    66
    7 1. Revert the pushed options immediately after rejecting the pushed cipher.  This fixes the issue at hand, and does not change other behaviour.
     71. Revert the pushed cipher option immediately after rejecting the pushed cipher.  This fixes the issue at hand, and does not change other behaviour.
    88
    992. Revert the entire options state on a connection reset, even when `persist-key` is used.  This fixes this issue in a more generic way, but will also change client behaviour.  The current behaviour is probably not on purpose (read: a bug), but users relying on the pushed options to persist over reconnections might be surprised that their config just stopped working.