Don't assert on BoringSSL's internal refcount fields.
Those fields are private. This removes one more obstacle to making SSL_SESSION opaque. Bug: none Change-Id: I77f8ee631c6b1e0e2f26618d4b6fe8cb1aede9fe Reviewed-on: https://chromium-review.googlesource.com/1011111 Commit-Queue: Steven Valdez <svaldez@chromium.org> Reviewed-by:Steven Valdez <svaldez@chromium.org> Cr-Commit-Position: refs/heads/master@{#550671}
Showing
Please register or sign in to comment