Re: Certificate could not be validated

2017-05-17 Thread Brian Morrison
On Wed, 17 May 2017 17:58:31 +
Evalee Gress wrote:

> When I asked them about this, they said they thought it might be due
> to a Microsoft update. Is that possible?

You should view the certificate and that should tell you who created it
and when. If you have an internal server then I suspect that the
certificate was created with a certain lifespan and now someone needs
to create a new certificate that expires in 5 or so years.

I don't think it can be down to MS, the certificate is for an internal
machine or domain so it's probably something from some years ago and
it's been forgotten about.

-- 

Brian Morrison

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

RE: Certificate could not be validated

2017-05-17 Thread Evalee Gress
When I asked them about this, they said they thought it might be due to a 
Microsoft update. Is that possible?

Other than that, they didn't know what could be causing the problem.

-Original Message-
From: David Woolley [mailto:for...@david-woolley.me.uk] 
Sent: Wednesday, May 17, 2017 1:55 PM
To: Evalee Gress; support@pidgin.im
Subject: Re: Certificate could not be validated

On 17/05/17 18:46, Evalee Gress wrote:
>
> I'm not sure which computer's data and time you're referring to or how 
> to check that.

That on the machine on which you are running pidgin.

>
> We use pidgin in-house within our company. I'm not sure what you mean 
> by the "service provider."

Your company's IT department.

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: Certificate could not be validated

2017-05-17 Thread David Woolley

On 17/05/17 18:46, Evalee Gress wrote:


I'm not sure which computer's data and time you're referring to or how
to check that.


That on the machine on which you are running pidgin.



We use pidgin in-house within our company. I'm not sure what you mean by
the "service provider."


Your company's IT department.

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

RE: Certificate could not be validated

2017-05-17 Thread Evalee Gress
David, thanks for your reply.



I'm not sure which computer's data and time you're referring to or how to check 
that.



We use pidgin in-house within our company. I'm not sure what you mean by the 
"service provider."



I’ve used Pidgin for years without this problem.



Here are my account settings:



[cid:image001.jpg@01D2CF14.03765D30]





-Original Message-
From: David Woolley [mailto:for...@david-woolley.me.uk]
Sent: Wednesday, May 17, 2017 1:21 PM
To: Evalee Gress; support@pidgin.im
Subject: Re: Certificate could not be validated



On 17/05/17 17:19, Evalee Gress wrote:

> What do I do to fix this SSL certificate error?



Check the computer's date and time, as it says.



If they are correct, contact the service provider by suitably secure means and 
ask them if they are really using an expired certificate.



If they say they are, point out that it is very bad practice, then make a risk 
assessment as how likely it is that a hacker may have cracked the encryption by 
now.



If they say that their certificate is valid, assume you are talking to an 
impostor, and do not use the service to send anything that you wouldn't want 
your local organised crime boss, to know, and do not receive any files unless 
you have a deep understanding of how files can be used to plant malware and you 
are certain that that is not possible in your case.



Similarly, if they say they know it is expired but your risk assessment 
determines it is too likely to have been compromised. Or preferably wait until 
they have fixed it, at their end, before continuing to use the service.



Do not ask anyone you do not know and trust to make the risk assessment for you.


___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: Certificate could not be validated

2017-05-17 Thread David Woolley

On 17/05/17 17:19, Evalee Gress wrote:

What do I do to fix this SSL certificate error?


Check the computer's date and time, as it says.

If they are correct, contact the service provider by suitably secure 
means and ask them if they are really using an expired certificate.


If they say they are, point out that it is very bad practice, then make 
a risk assessment as how likely it is that a hacker may have cracked the 
encryption by now.


If they say that their certificate is valid, assume you are talking to 
an impostor, and do not use the service to send anything that you 
wouldn't want your local organised crime boss, to know, and do not 
receive any files unless you have a deep understanding of how files can 
be used to plant malware and you are certain that that is not possible 
in your case.


Similarly, if they say they know it is expired but your risk assessment 
determines it is too likely to have been compromised. Or preferably wait 
until they have fixed it, at their end, before continuing to use the 
service.


Do not ask anyone you do not know and trust to make the risk assessment 
for you.


___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Certificate could not be validated

2017-05-17 Thread Evalee Gress
What do I do to fix this SSL certificate error?

This keeps popping up even after I click Accept.

[cid:image001.png@01D2CF07.D8891970]

Thanks.
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

403 Forbidden for Jabber

2017-05-17 Thread Serge Palladino
I'm trying to register an account on jabber (XMPP) but I'm getting an error
message 403: Forbidden. Could you offer me any insight on this please?

Thank you.
Serge
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support