-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fix url encoding for ocsp requests #7184
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
Merged
+42
−5
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
package certidp | ||
|
||
import ( | ||
"encoding/base64" | ||
"net/url" | ||
"strings" | ||
"testing" | ||
) | ||
|
||
func TestEncodeOCSPRequest(t *testing.T) { | ||
data := []byte("test data for OCSP request") | ||
encoded := encodeOCSPRequest(data) | ||
|
||
if strings.ContainsAny(encoded, "+/=") { | ||
t.Errorf("URL contains unescaped characters: %s", encoded) | ||
} | ||
|
||
decodedURL, err := url.QueryUnescape(encoded) | ||
if err != nil { | ||
t.Errorf("failed to url-decode request: %v", err) | ||
} | ||
decodedData, err := base64.StdEncoding.DecodeString(decodedURL) | ||
if err != nil { | ||
t.Errorf("failed to base64-decode request: %v", err) | ||
} | ||
if string(decodedData) != string(data) { | ||
t.Errorf("Decoded data does not match original: got %s, want %s", decodedData, data) | ||
} | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Should this be
base64.RawURLEncoding.EncodeToString(...)
and then you can get rid ofurl.QueryEscape
?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 was hesitant to remove the padding characters because I don't know how the decoder is implemented. It should be able to determine the correct size by measuring and rounding up, though.
However, using the URLEncoding functions definitely makes sense.
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.
Good point about the padding, in which case
URLEncoding
should be fine indeed.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 will test this against our PKI first and report back.
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.
How did it go?
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.
Not well. The PKI we use can't handle some of the options, but I'm still waiting for a response.
I also checked back with the RFC 4648 and the URLEncode is not the same like normal base64.
See https://datatracker.ietf.org/doc/html/rfc4648#section-5 for reference.
Right now I think that my first approach of using the StdEncoding (without removing padding characters) and then url.Encoding is safer. Will update this PR as soon as I get feedback from my colleagues.
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.
OK, I've tested all the combinations against our PKI system.
Only the 'normal' Base64 encoding, including the padding characters, worked.
Therefore, I would stick with my initial proposal to fix the bug and achieve the greatest possible compatibility with external PKI systems.