[pre-sve] commissioning fail #19459
Assignees
Comments
|
Pretty sure #19470 should fix this. |
|
Yes it is |
msandstedt
added a commit
to msandstedt/connectedhomeip
that referenced
this issue
Jun 10, 2022
… of wall clock time Most of our in-tree example server platforms do not have wall clock time. But to complicate matters, most are also reporting that they _do_ have wall clock time through the GetClock_RealTime interface. With project-chip#19119, this is now breaking CASE on these platforms. This commit does two things: first, where in-tree example platforms are seen by inspection to be giving obviously incorrect time, GetClock_RealTime now returns an error. Second, a default policy is injected from the server code that ignores NotBefore / NotAfter validation. This prevents NotBefore / NotAfter certificate validation breakages in other server implementations, whether in tree or out of tree, and is pragmatic in that it recognizes that many server-oriented nodes may not have access to a reliable time source. Fixes project-chip#19459
mkardous-silabs
pushed a commit
to mkardous-silabs/connectedhomeip
that referenced
this issue
Jun 10, 2022
… of wall clock time Most of our in-tree example server platforms do not have wall clock time. But to complicate matters, most are also reporting that they _do_ have wall clock time through the GetClock_RealTime interface. With project-chip#19119, this is now breaking CASE on these platforms. This commit does two things: first, where in-tree example platforms are seen by inspection to be giving obviously incorrect time, GetClock_RealTime now returns an error. Second, a default policy is injected from the server code that ignores NotBefore / NotAfter validation. This prevents NotBefore / NotAfter certificate validation breakages in other server implementations, whether in tree or out of tree, and is pragmatic in that it recognizes that many server-oriented nodes may not have access to a reliable time source. Fixes project-chip#19459
jmartinez-silabs
pushed a commit
that referenced
this issue
Jun 10, 2022
… of wall clock time (#19470) * Inject a certificate validity policy that accounts for unavailability of wall clock time Most of our in-tree example server platforms do not have wall clock time. But to complicate matters, most are also reporting that they _do_ have wall clock time through the GetClock_RealTime interface. With #19119, this is now breaking CASE on these platforms. This commit does two things: first, where in-tree example platforms are seen by inspection to be giving obviously incorrect time, GetClock_RealTime now returns an error. Second, a default policy is injected from the server code that ignores NotBefore / NotAfter validation. This prevents NotBefore / NotAfter certificate validation breakages in other server implementations, whether in tree or out of tree, and is pragmatic in that it recognizes that many server-oriented nodes may not have access to a reliable time source. Fixes #19459 * per tcarmelveilleux, #if 0 #19081 workaround
step0035
pushed a commit
to hank820/connectedhomeip
that referenced
this issue
Jun 13, 2022
… of wall clock time (project-chip#19470) * Inject a certificate validity policy that accounts for unavailability of wall clock time Most of our in-tree example server platforms do not have wall clock time. But to complicate matters, most are also reporting that they _do_ have wall clock time through the GetClock_RealTime interface. With project-chip#19119, this is now breaking CASE on these platforms. This commit does two things: first, where in-tree example platforms are seen by inspection to be giving obviously incorrect time, GetClock_RealTime now returns an error. Second, a default policy is injected from the server code that ignores NotBefore / NotAfter validation. This prevents NotBefore / NotAfter certificate validation breakages in other server implementations, whether in tree or out of tree, and is pragmatic in that it recognizes that many server-oriented nodes may not have access to a reliable time source. Fixes project-chip#19459 * per tcarmelveilleux, #if 0 project-chip#19081 workaround
pankore
pushed a commit
to pankore/connectedhomeip
that referenced
this issue
Jun 13, 2022
… of wall clock time (project-chip#19470) * Inject a certificate validity policy that accounts for unavailability of wall clock time Most of our in-tree example server platforms do not have wall clock time. But to complicate matters, most are also reporting that they _do_ have wall clock time through the GetClock_RealTime interface. With project-chip#19119, this is now breaking CASE on these platforms. This commit does two things: first, where in-tree example platforms are seen by inspection to be giving obviously incorrect time, GetClock_RealTime now returns an error. Second, a default policy is injected from the server code that ignores NotBefore / NotAfter validation. This prevents NotBefore / NotAfter certificate validation breakages in other server implementations, whether in tree or out of tree, and is pragmatic in that it recognizes that many server-oriented nodes may not have access to a reliable time source. Fixes project-chip#19459 * per tcarmelveilleux, #if 0 project-chip#19081 workaround
chrisbeach59
pushed a commit
to chrisbeach59/connectedhomeip
that referenced
this issue
Jun 19, 2022
… of wall clock time (project-chip#19470) * Inject a certificate validity policy that accounts for unavailability of wall clock time Most of our in-tree example server platforms do not have wall clock time. But to complicate matters, most are also reporting that they _do_ have wall clock time through the GetClock_RealTime interface. With project-chip#19119, this is now breaking CASE on these platforms. This commit does two things: first, where in-tree example platforms are seen by inspection to be giving obviously incorrect time, GetClock_RealTime now returns an error. Second, a default policy is injected from the server code that ignores NotBefore / NotAfter validation. This prevents NotBefore / NotAfter certificate validation breakages in other server implementations, whether in tree or out of tree, and is pragmatic in that it recognizes that many server-oriented nodes may not have access to a reliable time source. Fixes project-chip#19459 * per tcarmelveilleux, #if 0 project-chip#19081 workaround
chrisbeach59
pushed a commit
to chrisbeach59/connectedhomeip
that referenced
this issue
Jun 29, 2022
… of wall clock time (project-chip#19470) * Inject a certificate validity policy that accounts for unavailability of wall clock time Most of our in-tree example server platforms do not have wall clock time. But to complicate matters, most are also reporting that they _do_ have wall clock time through the GetClock_RealTime interface. With project-chip#19119, this is now breaking CASE on these platforms. This commit does two things: first, where in-tree example platforms are seen by inspection to be giving obviously incorrect time, GetClock_RealTime now returns an error. Second, a default policy is injected from the server code that ignores NotBefore / NotAfter validation. This prevents NotBefore / NotAfter certificate validation breakages in other server implementations, whether in tree or out of tree, and is pragmatic in that it recognizes that many server-oriented nodes may not have access to a reliable time source. Fixes project-chip#19459 * per tcarmelveilleux, #if 0 project-chip#19081 workaround
thcu-gp
pushed a commit
to thcu-gp/connectedhomeip
that referenced
this issue
Oct 5, 2022
… of wall clock time (project-chip#19470) * Inject a certificate validity policy that accounts for unavailability of wall clock time Most of our in-tree example server platforms do not have wall clock time. But to complicate matters, most are also reporting that they _do_ have wall clock time through the GetClock_RealTime interface. With project-chip#19119, this is now breaking CASE on these platforms. This commit does two things: first, where in-tree example platforms are seen by inspection to be giving obviously incorrect time, GetClock_RealTime now returns an error. Second, a default policy is injected from the server code that ignores NotBefore / NotAfter validation. This prevents NotBefore / NotAfter certificate validation breakages in other server implementations, whether in tree or out of tree, and is pragmatic in that it recognizes that many server-oriented nodes may not have access to a reliable time source. Fixes project-chip#19459 * per tcarmelveilleux, #if 0 project-chip#19081 workaround
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Commissioning failed over Thread and WiFi
System Configuration
DUT: EFR32
App: lighting/window/lock/light-swithc
SDK SHA: 5d8599d
Logs
pre-sve wk 2 commissioning fail - thread.txt
The text was updated successfully, but these errors were encountered: