You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2019/05/12 05:50:00 UTC

[jira] [Updated] (DIRAPI-314) StartTLS operation is not correctly handled

     [ https://issues.apache.org/jira/browse/DIRAPI-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRAPI-314:
-------------------------------------
    Fix Version/s:     (was: 2.0.0)
                   2.0.0.AM3

> StartTLS operation is not correctly handled
> -------------------------------------------
>
>                 Key: DIRAPI-314
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-314
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Emmanuel Lecharny
>            Priority: Critical
>             Fix For: 2.0.0.AM3
>
>
> Currently, the {{startTLS}} operation waits for the {{ExtendedRespose}} to be received to add the {{SslFilter}} into the network chain. So far, so good, as it's not accepting any other operation while doing that (well, it does accept some new request, but they will be queued).
> The problem arise when the response has been received, and once the {{SslFilter}} has been added : the {{SSL}} handshake starts, but as it's not blocking, it does not forbid other operations to be executed, and as the secured session may not yet established, those extra messages are going to be mixed with the handshake messages, leading to a closure of the connection.
> We must find a way to wait for the handshake to be completed before allowing other operations to be accepted.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)