Bug 1723586
Summary: | Firefox cannot browse some pages with fips mode on | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Joe Wright <jwright> |
Component: | nss | Assignee: | nss-nspr-maint <nss-nspr-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.0 | CC: | brclark, dueno, hbarcomb, hkario, jkoten, jprajzne, pasik, rrelyea, stransky, tmraz, tpelka, vanhoof |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-03 16:08:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1724250 | ||
Bug Blocks: | 1739559 |
Description
Joe Wright
2019-06-24 21:19:07 UTC
Is this still a problem with latest firefox 60.8.0? Thanks. it fails on RHEL-8.1.0-20190730.n.0 with nspr-4.21.0-3.el8_0.x86_64.rpm nss-sysinit-3.44.0-7.el8_0.x86_64.rpm nss-softokn-3.44.0-7.el8_0.x86_64.rpm nss-tools-3.44.0-7.el8_0.x86_64.rpm nss-3.44.0-7.el8_0.x86_64.rpm nss-softokn-freebl-3.44.0-7.el8_0.x86_64.rpm nss-util-3.44.0-7.el8_0.x86_64.rpm firefox-68.0.1-3.el8_0.x86_64.rpm firefox-debuginfo-68.0.1-3.el8_0.x86_64.rpm firefox-debugsource-68.0.1-3.el8_0.x86_64.rpm Do I understand correctly that this bug was present in FF 60.8.0 and it's also there in FF68.0? Thanks. (In reply to Martin Stransky from comment #3) > Do I understand correctly that this bug was present in FF 60.8.0 and it's > also there in FF68.0? Thanks. yes Moving to NSS as it looks like NSS issue to me. Martin, we already have bug 1724250 for tracking TLS 1.3 support in FIPS mode. Unless we get some additional information to show that this issue is not TLS 1.3 related, I will close this bug as a duplicate. *** This bug has been marked as a duplicate of bug 1724250 *** |