No we have not. That's why I wanted to see the cert being presented to see
what time ut has as it can gave any time in threory. Yes, we would need to
also see the time stamp on the client end when the messages come out.
On Mon, 6 Mar 2023, Brian P Bockelman wrote:
> If we are seeing issues with a certificate used that?s not yet valid, have we eliminated the possibility of a clock skew at either the client or the server?
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1940#issuecomment-1457543105
> You are receiving this because you commented.
>
> Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
Message ID: <xrootd/xrootd/issues/1940/1457558689@github.com>
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1940#issuecomment-1457558689",
"url": "https://github.com/xrootd/xrootd/issues/1940#issuecomment-1457558689",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
