Ability to force connection protocol from client
Issue #18
resolved
fc2b82f fixes a protocol negotiation problem which prevents version prior to 1.6.7 from being able to negotiate down to protocol 2. To allow 1.7.x to deal with older connections, a mechanism should be provided to force the protocol used for connection. This is a stop-gap mechanism to allow interoperability while people upgrade to 1.7.
Comments (3)
-
reporter
-
reporter
Ability to force proto 2 and auth failure fixes.
Added an option to
IntrepidSetupto force the usage of protocol version 2 for outbound (i.e., client) connections due to a protocol negotiation bug in versions prior to 1.6.4 which prevents 1.6 from properly negotiating with 1.7.x. When the option is set, ONLY protocol version 2 will be used. Inbound connections are not effected by the configuration and may use protocol version 3. (See#18)User authentication or other session initialization problems generated an NPE during message encoding resulting in a "Session unexpectedly closed" error.
Fixes:
#18→ <<cset de77561fcbe5>>
-
reporter
- changed status to resolved
Ability to force proto 2 and auth failure fixes.
Added an option to
IntrepidSetupto force the usage of protocol version 2 for outbound (i.e., client) connections due to a protocol negotiation bug in versions prior to 1.6.4 which prevents 1.6 from properly negotiating with 1.7.x. When the option is set, ONLY protocol version 2 will be used. Inbound connections are not effected by the configuration and may use protocol version 3. (See#18)User authentication or other session initialization problems generated an NPE during message encoding resulting in a "Session unexpectedly closed" error.
Fixes:
#18→ <<cset de77561fcbe5>>
- Log in to comment
