-
-
Notifications
You must be signed in to change notification settings - Fork 608
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
ratelimit: Remove legacy registrations per IP implementation #7760
ratelimit: Remove legacy registrations per IP implementation #7760
Conversation
52963aa
to
884dc1f
Compare
884dc1f
to
b51c916
Compare
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 this deployable in a single release as-is? It seems like if a WFE gets updated before an RA, the RA might reject new registrations due to incomplete gRPC fields.
@@ -1543,7 +1543,6 @@ func TestNewECDSAAccount(t *testing.T) { | |||
test.Assert(t, len(*acct.Contact) >= 1, "No contact field in account") | |||
test.AssertEquals(t, (*acct.Contact)[0], "mailto:[email protected]") | |||
test.AssertEquals(t, acct.Agreement, "") | |||
test.AssertEquals(t, acct.InitialIP.String(), "1.1.1.1") |
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.
Might be worth preserving a single test that confirms that the WFE is hardcoding this to 0.0.0.0 now.
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.
We can't preserve this test unless we also preserve the code that marshals the corepb.Registration back into the core.Registration object we can show the subscriber.
Co-authored-by: Aaron Gable <[email protected]>
Part of #7671