On 4/2/09 10:49, Kyle Hamilton wrote:
Realistically, the only way to describe this kind of thing to an
end-user is to bring up something -- in a language the user can
understand -- that explains what's going on with the connection. My
current thinking is that this needs to be brought up for all
On 02/04/2009 11:28 AM, Gervase Markham:
Jean-Marc Desperrier wrote:
Gerv, what about changing the Firefox SSL page/implementation so that in
that situation, for those 99% of the market, it gives the most
informative information, non scary, non blocking possible ? Even when
there was an error in
Realistically, the only way to describe this kind of thing to an
end-user is to bring up something -- in a language the user can
understand -- that explains what's going on with the connection. My
current thinking is that this needs to be brought up for all
connections, not just connections that h
Jean-Marc Desperrier wrote:
> Gerv, what about changing the Firefox SSL page/implementation so that in
> that situation, for those 99% of the market, it gives the most
> informative information, non scary, non blocking possible ? Even when
> there was an error in the configuration ?
I'm not sure w
On 30/1/09 13:25, Jean-Marc Desperrier wrote:
Ian G wrote:
Ian G wrote, On 2009-01-29 10:01:
[...] when firefox trips
over a cert, it could show something like that.
| There is a problem with this cert!
|
| ==> *The cert was not issued by a known CA*<==
| The cert has expired or is not yet v
Ian G wrote:
On 29/1/09 19:24, Nelson B Bolyard wrote:
Ian G wrote, On 2009-01-29 10:01:
[...] when firefox trips
over a cert, it could show something like that.
| There is a problem with this cert!
|
| ==> *The cert was not issued by a known CA*<==
| The cert has expired or is not yet vali
On 29/1/09 19:24, Nelson B Bolyard wrote:
Ian G wrote, On 2009-01-29 10:01:
Hmm, nope, apologies, I wasn't clear. What I wanted was something like
the behaviour shown on that page, when it comes in contact with a cert,
to be incorporated as behaviour in firefox. So that when firefox trips
over
Ian G wrote, On 2009-01-29 10:01:
> Hmm, nope, apologies, I wasn't clear. What I wanted was something like
> the behaviour shown on that page, when it comes in contact with a cert,
> to be incorporated as behaviour in firefox. So that when firefox trips
> over a cert, it could show something l
On 29/1/09 17:36, Johnathan Nightingale wrote:
On 29-Jan-09, at 8:29 AM, Ian G wrote:
On 29/1/09 13:31, Jean-Marc Desperrier wrote:
Gerv, what about changing the Firefox SSL page/implementation so that in
that situation, for those 99% of the market, it gives the most
informative information, n
On 01/29/2009 06:36 PM, Johnathan Nightingale:
I think I'm hearing an RFE to change the cert error page to link to
elaborated information elsewhere (probably on support.mozilla.com, but
maybe on mozilla.com itself) which explains this problem to users,
possibly with a section for site administrat
On 29-Jan-09, at 8:29 AM, Ian G wrote:
On 29/1/09 13:31, Jean-Marc Desperrier wrote:
Gerv, what about changing the Firefox SSL page/implementation so
that in
that situation, for those 99% of the market, it gives the most
informative information, non scary, non blocking possible ? Even when
t
On 29/1/09 13:31, Jean-Marc Desperrier wrote:
Gervase Markham wrote:
Robertss wrote:
http://www.sslshopper.com/ssl-certificate-not-trusted-error.html
...
Gerv, what about changing the Firefox SSL page/implementation so that in
that situation, for those 99% of the market, it gives the most
in
On 01/29/2009 02:31 PM, Jean-Marc Desperrier:
Gerv, what about changing the Firefox SSL page/implementation so that in
that situation, for those 99% of the market, it gives the most
informative information, non scary, non blocking possible ? Even when
there was an error in the configuration ?
T
Gervase Markham wrote:
Robertss wrote:
Thanks, Gerv! I went through each of the providers websites and found
their main support pages. I have added links to them on this page:
http://www.sslshopper.com/ssl-certificate-not-trusted-error.html
I can tell you that you have covered 96% of the CA ma
Robertss wrote:
> Thanks, Gerv! I went through each of the providers websites and found
> their main support pages. I have added links to them on this page:
> http://www.sslshopper.com/ssl-certificate-not-trusted-error.html
I can tell you that you have covered 96% of the CA market with the list
yo
On Jan 20, 9:35 pm, Gervase Markham wrote:
> If you can give us a URL to a page which will always show the entire
> list you currently have, perhaps people in this group can add to it.
>
> Gerv
Thanks, Gerv! I went through each of the providers websites and found
their main support pages. I have
Robertss wrote:
> Thanks for pointing this tool out. I actually helped create it. I
> included a link to a page that explains why an error is given when an
> Intermediate certificate cert is missing but I didn't include specific
> instructions on how to fix it because each certificate provider is
>
On Jan 19, 3:22 pm, Gervase Markham wrote:
> I just came across this:http://www.sslshopper.com/ssl-checker.html
>
> Rather nice, particularly for people with intermediate cert chain
> errors. It would be even better if there was an independent version of
> such a tool, which could link you through
Gervase Markham wrote:
I just came across this:
http://www.sslshopper.com/ssl-checker.html
Rather nice, particularly for people with intermediate cert chain
errors. It would be even better if there was an independent version of
such a tool, which could link you through to the "fix it" pages for
I just came across this:
http://www.sslshopper.com/ssl-checker.html
Rather nice, particularly for people with intermediate cert chain
errors. It would be even better if there was an independent version of
such a tool, which could link you through to the "fix it" pages for
certificate providers who
20 matches
Mail list logo
