New answers tagged


This is an interesting question why I was looking into the source code of Chromium too see how they do it. The Answer It is nearly impossible to implement a 100% reliable feature to prevent a screenshot that will be used in the most visited view. You have to hide the sensitive content right the moment the service is storing the data. Which might happen all ...


When using client certificates the server sends a list of acceptable CA which issued the client certificate. Based on this list the browser will select the matching client certificate. If there is no client certificate issued by the CA expected by the server you get the error message. Thus the problem might not be the certificate itself, but simply that the ...


You can disable it: To disable OCSP in Firefox: Go to "Tools (or Menu button) -> Options -> Advanced -> Certificates" and uncheck Query OCSP responder servers to confirm the current validity of certificates. (source:


Have you tried editing the field name using Saved Password Editor's "Edit" feature? Save the logon. Open it in Saved Password Editor. Select the logon, and click edit. You will see a box near the bottom labeled "Password field name". Paste in the name of the real password field. Firefox should be able to match it up after that. Of course, this won't ...


For most major browsers that are used in the tech community, the only thing stopping them from being evil is the fact that they rely on open source code, and are widely poked and prodded. Unfortunately, these browsers also include add-ons and extensions, which are less likely to be well-vetted and so even more likely to be causing insecurity. It is indeed ...


Is there anything stopping from web browsers snooping into our activities? Nope, not really. That's a bit like asking Is there anything stopping my keyboard from recording my keystrokes? In theory, we are interacting directly with the keyboard / web browser, which in turn talks to other components for us, and we are trusting that it is acting in our ...


You better ignore that commenter entirely. Joey Spinosa is either royally confused or is trolling. There are many totally inaccurate statements in his comments; mainly from conflating Server Certificate with Certificate Authority Certificate. Claim 1: downloading files ... install these certificates of authority. Browsers never silently install a ...


It's probably to simplify the implementation. Rather than having two cases where the key store could be encrypted or not depending on whether Master Password is set, the code always encrypts. This reduces the likelihood that a code path that forgets to encrypt when Master Password is enabled goes unnoticed.


I'd say that the reason is to obfuscate the stored passwords, and that the "remember websites passwords" feature in Firefox is supposed to be always used with a master key.

Top 50 recent answers are included