hello,
please advise re: security certificate error warning as follows:
AOL, my provider downloaded software 'fixes' due to 100's of errors,
particularly server errors. AOL.Download package contained. Bing, msm, as
well as Internet explorer update from 9.7 to 10.
Pute is humming
Matthias Apitz wrote:
El día Friday, January 18, 2013 a las 05:23:30PM +, David Woolley escribió:
David Woolley wrote:
To the extent that that is the problem, simply replacing the .pem file
with a current one, should sort the problem. I don't know if you will
The server certificates
David Woolley wrote:
There are still a lot of expired certificates.
A lot turns out to be two, the two that I sampled, both MSN related
intermediate ones:
Microsoft_Internet_Authority.pem:
Not After : Feb 19 18:24:53 2011 GMT
Microsoft_Secure_Server_Authority.pem:
El día Saturday, January 19, 2013 a las 12:43:00PM +, David Woolley
escribió:
David Woolley wrote:
There are still a lot of expired certificates.
A lot turns out to be two, the two that I sampled, both MSN related
intermediate ones:
Microsoft_Internet_Authority.pem:
Hello,
Since today morning I can't connect to MSN anymore; it says that the
certificates can't be validated;
This is with pidgin 2.10.x
Any thing I can do? Thanks
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e g...@unixarea.de - w
Matthias Apitz wrote:
Since today morning I can't connect to MSN anymore; it says that the
certificates can't be validated;
This is the second report to the list.
I tried using a Windows Pidgin (probably a little dated). This also
produces a certificate warning, but I imagine most Windows
David Woolley wrote:
I tried using a Windows Pidgin (probably a little dated). This also
2.10.3, so not that dated.
produces a certificate warning, but I imagine most Windows users would
just select the option to ignore the problem.
Looking at the certificate, I think the problem is
David Woolley spake unto us the following wisdom:
Looking at the certificate, I think the problem is that the
certificate is for contacts.msn.com, but the server is
local-bay.contacts.msn.com. An earlier certificate for a server in
the contacts.msn.com domain (omega.contacts.msn.com) seems to
As it is, I've noticed this MSN popup the last few days, but today I
haven't been prompted with it, so maybe the issue is already resolved on
MSN's side?
Ethan Blanton wrote:
David Woolley spake unto us the following wisdom:
Looking at the certificate, I think the problem is that the
Ethan Blanton wrote:
Pidgin doesn't use the OS root certificates *only* on Windows.
At least some Linux distributions don't have an OS level certificate
store; each application maintains its own set of root certificates.
On the other hand, applications like Firefox, which would use their
El día Friday, January 18, 2013 a las 08:52:16AM -0500, Ethan Blanton escribió:
David Woolley spake unto us the following wisdom:
Looking at the certificate, I think the problem is that the
certificate is for contacts.msn.com, but the server is
local-bay.contacts.msn.com. An earlier
Matthias Apitz spake unto us the following wisdom:
Pidgin doesn't use the OS root certificates *only* on Windows.
I'm not a native English and do not understand your phrase; could you
please explain what you say; thanks
On non-Windows systems, there is often a certificate store that Pidgin
the SHA1 of the popup certificate for local-bay.contacts.msn.com i am
getting is:
f6:56:e3:29:84:86:8b:6b:38:fd:e4:aa:70:1a:00:4a:33:4d:ba:04
just would like to confirm it is valid before accept.
--
[]s Fosforo
-
Se eu tiver oito
Ethan Blanton wrote:
On Windows, we don't use the system store. I don't know why not, I
assume it's painful, probably because of poor OS design and
implementation.
Probably because one would have to use all of the Windows public key
infrastructure, instead of the open source
Fosforo wrote:
the SHA1 of the popup certificate for local-bay.contacts.msn.com i am
getting is:
f6:56:e3:29:84:86:8b:6b:38:fd:e4:aa:70:1a:00:4a:33:4d:ba:04
just would like to confirm it is valid before accept.
Unfortunately I deleted it, and didn't write down the OpenSSL
fingerprint.
David Woolley wrote:
To the extent that that is the problem, simply replacing the .pem file
with a current one, should sort the problem. I don't know if you will
The server certificates don't seem to include the full certificate
chain, so I think you will need to install the pem file for
El día Friday, January 18, 2013 a las 04:34:03PM +, David Woolley escribió:
Probably because one would have to use all of the Windows public key
infrastructure, instead of the open source implementation.
The non-Windows ones are probably designed for use with OpenSSL.
In Matthias'
Matthias Apitz wrote:
El día Friday, January 18, 2013 a las 04:34:03PM +, David Woolley escribió:
Probably because one would have to use all of the Windows public key
infrastructure, instead of the open source implementation.
The non-Windows ones are probably designed for use with
18 matches
Mail list logo
