Lucas, do you have any more context about this? Looks like PageInfo uses |security_bits| so I'm not sure how we can get rid of it / with what we should replace those checks.

I assume the idea here is that we only needed this when we would frown on weak crypto (e.g. 56 bit suites) instead of blocking it completely. These days, we only have two states ("We don't know how many bits the crypto is" and "We are satisfied with the number of bits the crypto is") and the former completely overlaps the latter.

The current calculations don't rely on security bits, only cipher suite values.

It should be easy to remove security_bits from Page Info after https://chromium-review.googlesource.com/c/chromium/src/+/575835 lands. That CL still needs a UI test for Android.

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!