Dear Pidgin Support
I have a problem, when i connect pidgin with Mxit pidgin always error.
And dtail
Problem signature:
Problem Event Name:APPCRASH
Application Name: pidgin.exe
Application Version:
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
Just confirming that others received also the same certificate for
contacts.msn.com domain:
Name: contacts.msn.com
Impressão digital (SHA1):
f6:56:e3:29:84:86:8b:6b:38:fd:e4:aa:70:1a:00:4a:33:4d:ba:04
Data de ativação: Fri Jan 11 14:47:08 2013
Data de expiração: Sun Jan 11 14:47:08 2015
--
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.
Jeronimo de A. Barros wrote:
Hi...
Today my pidgin is refusing to connect to MSN and returns this error:
Unable to validate certificate
The certificate for local-blu-people.directory.live.com could not be
validated. The certificate chain presented is invalid.
It would appear that
For anyone having trouble with the Pidgin icon disappearing in Cinnamon in
the system tray, I was able to fix it using the following hack:
As root (or sudo) from a terminal window:
cd /usr/share/pixmaps/pidgin/tray/hicolor
mv 16x16 16x16old
ln -s 22x22 16x16
Then restart pidgin.
This
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
Thanks for this, Dustin.
Since Cinnamon plays nicer with the 22x22 version, perhaps the Cinnamon
desktop team has a way of making this default?
Pidgin + Cinnamon are a fairly popular combination, I'm sure others will
benefit from your investigation.
-Tres
On Fri, Jan 18, 2013 at 12:10 PM,
Yes, I actually brought this up on the system icon bugs thread for cinnamon
(don't have the url handy) that was a catchall ticket for bugs related to
system tray behavior, so hopefully someone on the cinnamon development team
can help us out. Either way, in glad to finally have this fixed!
On Jan
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
Hallo,
It doent work The Tutorial is NOT exact enough!
Es funktioniert einfach nicht, das Tutorial ist an den entscheidenden
Punkten zu ungenau.
Hier meine Jabber Daten (Mail):
Du hast eben über http://einfachjabber.de http://einfachjabber.de einen
neuen
Jabber-Account
21 matches
Mail list logo
