NSS dislikes my server

Dear list, (I am not sure this is the correct newsgroup. If it isn't, please point me in the correct direction.) I am having troubles with my TLS-enabled lighttpd and any browser that uses NSS (Firefox, SeaMonkey, Chromium). For example, Firefox bails out with "sec_error_bad_signature" on connect

Problem with Firefox and "manual" NTLM authentication

Hi, I am having a problem with Firefox failing to do "manual" NTLM authentication. By "manual", I mean where, when you access the website, you get a popup login window and enter domain\username and password. When I do this, instead of being able to access the website, the popup login window

Re: Another Protocol Bites The Dust

(replying to a message on dev-security at mozilla, but since this affects OpenSSL more than Mozilla, I'm sending this one directly to openssl-users and bcc:ing dev-security. I hope the spam filter lets it through.) When handled properly (i.e., you don't rely on anything before the renegotiation,

Problem with Firefox and "manual" NTLM authentication

[Sorry if this gets re-posted. I tried sending to this NG using Thunderbird, but it didn't appear.] Hi, I am having a problem with Firefox failing to do "manual" NTLM authentication. By "manual", I mean where, when you access the website, you get a popup login window and enter domain\username a

Re: Browser security in the XO aka OLPC aka $100 laptop

Check with Marco Gritti . He's the guy doing all the browser work. --Chris On Apr 3, 2008, at 2:06 AM, Xavier Vergés wrote: Thanks, Boris I haven't asked them (still don't know where they hang out), but I'm under the impression that they are running plain Xulrunner, using Hulahop, a Gecko

Re: Content Security Policy feedback

You guys should add Arun + Jonas to this conversation if you can. --Chris ___ dev-security mailing list dev-security@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security

Re: Signed Jar in JSP / Firefox 2.0.0.15

Boris Zbarsky a écrit : Marine wrote: The webpage have to be able to expose some values/parameters to the extension. So I tried to add properties to button, to document or to window objects, in my webpage. The problem is that reading those from chrome would be exploitable (by the web

Scripting in a DOMParser-generated data document: Should I sandbox?

Ladies and gentlemen of the jury, In developing my markup templating system for Verbosio, it's becoming clear that I need to add JavaScript support for documents parsed through a DOMParser ("data documents"). At first, I need it for testing - data documents define the parameters of the test,