You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Blake Bender (Jira)" <ji...@apache.org> on 2020/10/23 15:17:00 UTC
[jira] [Resolved] (GEODE-8569) Missing message security footer
check in gnmsg
[ https://issues.apache.org/jira/browse/GEODE-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Blake Bender resolved GEODE-8569.
---------------------------------
Resolution: Fixed
> Missing message security footer check in gnmsg
> ----------------------------------------------
>
> Key: GEODE-8569
> URL: https://issues.apache.org/jira/browse/GEODE-8569
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Blake Bender
> Assignee: Blake Bender
> Priority: Major
> Labels: pull-request-available
>
> In an older version of the `gnmsg.py` script, there was a function called request_requires_security_footer that returned a boolean based on the message name, indictating whether or not the message needed the security footer in a server conversation with authentication. In the refactor that moved the client message decoding into a class, this method was left out, so attempting to decode messages from a client log that used AuthInitialize will throw an exception attempting to call this missing function. We need to add this call to the ClientMessageDecoder class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)