You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/12/06 22:49:00 UTC

[jira] [Commented] (GEODE-4007) Authentication failures/bad handshake should close the socket from the server side

    [ https://issues.apache.org/jira/browse/GEODE-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281061#comment-16281061 ] 

ASF subversion and git services commented on GEODE-4007:
--------------------------------------------------------

Commit 5063aca4b2b1a1ff43d448cd7b24f17355373a50 in geode's branch refs/heads/develop from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5063aca ]

GEODE-4007: Authentication/Handshake errors should close the socket

This will cause the connection to be closed whenever a handshake or
 authentication message fails.
The connection will also be broken if we ever receive an unexpected handshake or
 authenticantication message.

Signed-off-by: Galen O'Sullivan <go...@pivotal.io>


> Authentication failures/bad handshake should close the socket from the server side
> ----------------------------------------------------------------------------------
>
>                 Key: GEODE-4007
>                 URL: https://issues.apache.org/jira/browse/GEODE-4007
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Brian Rowe
>
> Ensure after failed auth/handshake the server (after sending error response) closes the socket and cleans up.
> While going over the code together, it looks like maybe authentication errors simply leave the socket in a state where it is expecting another authentication request. It might be better to close the socket from the server side for various error conditions like a failed handshake or authentication.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)