Brian Smith
Brian Smith
PR #2361 brings in BoringSSL's checks for SSE2 on the C side, and changes build.rs to automatically pass "-msse2" to the C compiler for x86 targets. PR #2363 tries to...
In PR #2359, I added a requirement that SSSE3 be detected in order to use AES-NI. (Technically SSE2 is all that is required but I don't think there are any...
I've rebased PR #2346 on top of all the changes I merged yesterday, mentioned above.
In PR #2368 I add a test that you should ensure passes (except on ancient CPUs) in your patched versions of *ring*.
> Now that we have [Feature Policy](https://github.com/WICG/feature-policy), I think that's the way to go about that. Similarly, there is a proposal to [expose `bounds`](https://github.com/WICG/feature-policy/issues/132) cross-origin. Content Security Policy (CSP) already...
> How big of a problem is it that navigation of the `` ends up resizing it? It does not seem like a security issue as we already expose navigation...
Good idea. I think that this can be automated by putting it in the mk/package.sh script, which I always run prior to doing `cargo publish --allow-dirty`. Note that the mk/package.sh...
I manually created a tag for the 0.7.0 release. I haven't tried to automate the tagging yet.
In general I've been doing this. It would be better if I automated it, but I'm going to close this since the manual step seems to be working well enough....
Here are the exact steps I did for the 0.17.6 release, copied from https://github.com/briansmith/ring/issues/1460#issuecomment-1830416384: ``` # Start Windows machine, open a "Git Bash" prompt, and change to my *ring* checkout...