Open Bug 1795970 Opened 3 years ago Updated 1 day ago

engine-gecko: Integrate certificate information

Categories

(Firefox for Android :: Browser Engine, enhancement)

All
Android
enhancement

Tracking

()

ASSIGNED

People

(Reporter: csadilek, Assigned: keeler)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

From github: https://github.com/mozilla-mobile/android-components/issues/5557.

We currently only use the full (unparsed) issuer name in our SecurityInfo. GeckoView now provides more certificate information we should integrate.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Severity: -- → N/A
Type: defect → task
Type: task → enhancement
Priority: -- → P3
Flags: needinfo?(cpeterson)

Please seriously consider moving to P2 and S2. Having to switch to a chromium based Android browser everytime we want to make sure that a website is very secure (check TLS version, bit length etc.) is very frustrating.

Flags: needinfo?(jboek)

Removing severity/priority for this for re-triage.

Flags: needinfo?(jboek)
Priority: P3 → --

I have not found a way to access certificate information when using Gecko via the Android Components at all.

Since geckoSession is internal there is no way to override the progessDelegate where the certificate information is reduced and made available to the observers.

At this stage, I would suggest that the entire certificate should be made available to observers, rather than just the host and issuer.

Blocks: 2000336
Assignee: nobody → dkeeler
Status: NEW → ASSIGNED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: