Vyhľadajte odpoveď

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

is there a way to search the bugzilla database for strings?

  • 6 odpovedí
  • 1 má tento problém
  • 2 zobrazenia
  • Posledná odpoveď od cor-el

more options

I would like to search the bugzilla database for known issues.

While there is a builtin search tool, that does not work: if I search for a string and limit the search to one specific bug where I know it contains the string, then that bug is reported. Doing the same search over all bugs, it (takes long and then) reports that no bug at all contains the string - not even the one where I know it contains the string.

So this search tool is proven defective and cannot be used. What alternatives are there?

Všetky odpovede (7)

more options

What is it you are searching for?

Pomohla vám táto odpoveď?

more options

The error message from Firefox JavaScript error: chrome://browser/content/browser-siteIdentity.js, line 643: TypeError: issuerCert is undefined

Or any sensible part of it or ANYTHING that might help me fix the problem.

Pomohla vám táto odpoveď?

more options

You can surround a search string in double quotes ("issuerCert is undefined") just like on this forum, but that may not get you very far.

It is usually easier to check out the Firefox source code to see what this is about.

Pomohla vám táto odpoveď?

more options

One of the confusing issues in searching Bugzilla is figuring out which fields have the strings you want.

The source file has a bar at the left with links to the last bug that modified the code. Seldom the one you're looking for unless it's a recently introduced features, but FWIW.

Also, you can try a site-targeted Google search: https://www.google.com/search?q=site:bugzilla.mozilla.org+"issuercert"+&client=firefox-b-1-d

Pomohla vám táto odpoveď?

more options

pmc1 said

JavaScript error: chrome://browser/content/browser-siteIdentity.js, line 643: TypeError: issuerCert is undefined

When you see something like this, it means the file (name starting from chrome:) has an error at line so and so. In this case, 643.

But unless you are a programmer and have the coding, it is best to post such errors here for the brains to look over.

Pomohla vám táto odpoveď?

more options

See also refreshIdentityPopup

This could be a problem with root certificates that are automatically imported.

  • 1549605 - Add an indicator in the identity popup for when the site is verified by an imported root certificate

Pomohla vám táto odpoveď?

more options

cor-el said

You can surround a search string in double quotes ("issuerCert is undefined") just like on this forum, but that may not get you very far.

I did only search for "issuerCert" (in 'Comments'), and the seach tool did already break and produce false negatives. (Isn't anybody interested in fixing that thing? One cannot work with broken tools...)

It is usually easier to check out the Firefox source code to see what this is about.

I do that already. But I am neither a native javascript speaker nor a native cpp speaker, so usually it helps me a lot to find some related discussion of programmers in order to better understand what the code might actually do.

FredMcD said

pmc1 said

JavaScript error: chrome://browser/content/browser-siteIdentity.js, line 643: TypeError: issuerCert is undefined

When you see something like this, it means the file (name starting from chrome:) has an error at line so and so. In this case, 643.

But unless you are a programmer and have the coding, it is best to post such errors here for the brains to look over.

I did this at first, here: https://support.mozilla.org/en-US/questions/1350861

Then I started to learn the javascript.

Now I know that Firefox, all versions since at most 73 up to at least 90, does not always correctly recognize my certificates when utilizing TLS 1.3 (and with TLS 1.3 only - TLS 1.2 and below appears to work fine).

The certifcate authority people say, there should be no difference, certificates do not need to be explicitely enabled for TLS 1.3.

So what do I do next?

cor-el said

See also refreshIdentityPopup This could be a problem with root certificates that are automatically imported.
  • 1549605 - Add an indicator in the identity popup for when the site is verified by an imported root certificate

Is there a difference how this is done in TLSv1.3, versus TLSv1.2 and below?

But somehow You are right, only to the contrary: the error does NOT appear with my imported certificates. It does ONLY appear with letsencrypt certificates.

It does, however, also appear occasionally when a local certificate is NOT imported, and only an exception is added for a specific page. More precisely: the error message from above does not appear in this case, but the fact that the certificate is not known to be displayed does appear.

Upravil(a) pmc1 dňa

Pomohla vám táto odpoveď?

Položiť otázku

Ak chcete pridať odpoveď, musíte sa prihlásiť k svojmu účtu. Ak účet doteraz nemáte, položte novú otázku.