-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Minimal fix for b/74357976. #890
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
Minimal fix for b/74357976. #890
Conversation
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.
Content LGTM, but I'm not sure this is the right branch. Do not merge.
Oh also, changelog |
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.
LGTM thank you for helping this.
Good call, added changelog entry. |
I made a release-4.10.1 branch. Please target it there. |
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.
Change merge target to release-4.10.1
I've changed the target branch, but we're looking into an additional (perhaps related issue) so may want to hold off on merging this. |
Okay, I've incorporated the second fix that @wilhuff tracked down. PTAL |
Actually @wilhuff is doing a further audit of WrapNSStringNoCopy() usages for additional potential bugs... |
…NSStringNoCopy() issue which @wilhuff is going to create a fix for.
37073b6
to
3b4fa32
Compare
@wilhuff is going to create a separate PR for all of the util:WrapNSStringNoCopy() fixes. This PR will just be for the original token issue and should be good-to-go 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.
Approving on @paulb777's behalf, since this PR is now targeting the correct branch.
Paul briefly unavailable--see review comment
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.
Please fix duplicate in title
* Version bumps for Firebase 4.10.1 (#891) * Minimal fix for b/74357976 (#890) Fixes b/74357976 which caused unauthenticated users to be unable to reach the Firestore backend and updates the changelog. * Copy all C++ strings to NSString where they're not obviously safe (#893) This fixes a known instances of memory corruption where in FSTLevelDBMutationQueue, the NSString view was retained for later, and the incorrect user was used, causing b/74381054. gRPC does not necessarily copy its string argumnets and if our hostname were configured to a non-default one it's possible that we could corrupt the host cache too. All remaining usages of util::WrapNSStringNoCopy are obviously safe: passed into logging or other known transient usages. * fix lint
Fixes b/74357976 which caused unauthenticated users to be unable to reach the Firestore backend and updates the changelog.
* Version bumps for Firebase 4.10.1 (firebase#891) * Minimal fix for b/74357976 (firebase#890) Fixes b/74357976 which caused unauthenticated users to be unable to reach the Firestore backend and updates the changelog. * Copy all C++ strings to NSString where they're not obviously safe (firebase#893) This fixes a known instances of memory corruption where in FSTLevelDBMutationQueue, the NSString view was retained for later, and the incorrect user was used, causing b/74381054. gRPC does not necessarily copy its string argumnets and if our hostname were configured to a non-default one it's possible that we could corrupt the host cache too. All remaining usages of util::WrapNSStringNoCopy are obviously safe: passed into logging or other known transient usages. * fix lint
This is a more minimal alternative to #887.