[
https://issues.apache.org/jira/browse/GEODE-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205868#comment-17205868
]
ASF GitHub Bot commented on GEODE-8569:
---------------------------------------
pdxcodemonkey opened a new pull request #663:
URL: https://github.com/apache/geode-native/pull/663
- This would be called, and thus throw an exception, for client logs using
AuthInitialize
- Also added NC v10.0.3 to version lookup for regex function dispatcher.
Apparently we'd
never tried to decode a v10.0.3 log before, go figure
@mreddington @davebarnes97 @dihardman @karensmolermiller @alb3rtobr
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
>
> 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)
