On Wed, Sep 13, 2006 at 08:00:20PM +0700 or thereabouts, Thomas Fernandez wrote:
Hi Thomas,
> On Tue, 12 Sep 2006 16:52:48 -0500 GMT (13/09/2006, 04:52 +0700 GMT),
> Gary wrote:
>
> G> The protocol as you call it, (SSL, TLS) does not define that the certs have
> G> to be valid, never has. It i
Hello Gary,
On Tue, 12 Sep 2006 16:52:48 -0500 GMT (13/09/2006, 04:52 +0700 GMT),
Gary wrote:
G> The protocol as you call it, (SSL, TLS) does not define that the certs have
G> to be valid, never has. It is the client, TB!, that has decided for me not
G> to accept it. It should be always up to th
Hi Raymund,
On Tue, 12 Sep 2006 23:28:20 +0200 UTC (9/12/2006, 4:28 PM -0500 UTC my
time), Raymund Tump wrote:
>> This is wrong.. it should ***ALWAYS*** be left to the user to decide
>> whether to continue to use any cert, whether expired, or incorrect name, or
>> whatever reason
R> Wel
Hi Gary!
> This is wrong.. it should ***ALWAYS*** be left to the user to decide
> whether to continue to use any cert, whether expired, or incorrect name, or
> whatever reason
Well, that depends on the protocol. It is not always up to the user to
decide if the protocol (SSL, TLS, whatever
Hi ya'll,
Well, just installed the new TB, and I logged onto a distant IMAPS server
using SSL on port 993... just like I have done for years...
Since the 2 year SSL cert has just expired on this server, I cannot log on,
(set up for SSL only) as TB says "handshake failure. invalid server
cer
5 matches
Mail list logo