All users were logged out of Bugzilla on October 13th, 2018

Need to decide the PSM interface we expose for embeddors

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
18 years ago
9 years ago

People

(Reporter: chak, Assigned: thayes0993)

Tracking

Trunk
All
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Currently there's not a way for the embeddors to impl a security info dlg (i.e.
the one which gets shown when one clicks on the Mozilla lock icon) since they do
not have access to any PSM interfaces via nsIwebBrowser or some other embedding
interface(using which they can impl the dlg)

We have access to an nsISecureBrowserUI interface in
embedding/browser/webBrowser/nsWebBrowser.cpp where it's created. However, we
decided a while ago that this may not be the correct interface the embeddors
should have access to.

If we decide that exposing this interface is the way to go, then we can easily
impl the dlg. by doing something like:

+    // Get the nsISecureBrowserUI via nsIWebBrowser
+    nsresult rv = NS_OK;
+    nsCOMPtr<nsISecureBrowserUI> securityUI = do_GetInterface(mWebBrowser, &rv);
+    if (NS_FAILED(rv)) return;
+
+
nsCOMPtr<nsISSLStatusProvider> sslStatusProvider = do_QueryInterface(securityUI,
&rv);
+
if(NS_FAILED(rv)) return;
+
+    nsCOMPtr<nsISSLStatus> sslStatus;
+    rv = sslStatusProvider->GetSSLStatus(getter_AddRefs(sslStatus));
+    if (NS_FAILED(rv)) return;

Once we have nsISSLStatus we can get all kinds of info about the X.509 cert etc.
which can be used to impl. dlg.

So, let's decide the interface we want to expose....
QA Contact: dunn5557 → apis

Updated

9 years ago
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.