New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GEODE-4439 Refactor HandShake.java #1374
Conversation
Created ServerSideHandshake and ServerSideHandshakeImpl for servers. Created ClientSideHandshake and ClientSideHandshakeImpl for clients. Message encryption/decryption is now in an Encryptor interface. HandShake is renamed Handshake.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The refactor looks fine to me.
import org.apache.geode.security.Authenticator; | ||
import org.apache.geode.security.GemFireSecurityException; | ||
|
||
public abstract class Handshake { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice rename.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have very little experience with the handshake stuff but it looks like a good refactoring to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, though the review was little large to go through that carefully. It may have been easier to review if you had the HandShake->Handshake rename in a separate commit.
protected HandShake getHandShake() { | ||
return handShake; | ||
protected byte[] encryptBytes(byte[] messageBytes) throws Exception { | ||
return handshake.getEncryptor().encryptBytes(messageBytes); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any risk of handshake not being set when this (or decryptBytes) is called?
} | ||
} | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there are several places in this file that have a few extra newlines.
commit c1b21c0 (HEAD -> develop, origin/develop) |
Created ServerSideHandshake and ServerSideHandshakeImpl for servers.
Created ClientSideHandshake and ClientSideHandshakeImpl for clients.
Message encryption/decryption is now in an Encryptor interface.
-- opened a new ticket to track that client/server diffie-hellman handshake has been broken since 2008
HandShake is renamed Handshake.
@PivotalSarge @WireBaron @upthewaterspout @galen-pivotal
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
Has your PR been rebased against the latest commit within the target branch (typically
develop
)?Is your initial contribution a single, squashed commit?
Does
gradlew build
run cleanly?Have you written or updated unit tests to verify your changes?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.