View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010321 | 10000-012: Discovery | Spec | public | 2025-05-09 09:28 | 2025-05-09 09:28 |
| Reporter | Matthias Damm | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Product Version | 1.05.04 | ||||
| Summary | 0010321: CheckRevocationStatus, OCSP and OCSP stapling | ||||
| Description | The CheckRevocationStatus method in Part 12 has the same problems like OCSP, it es even worse than for web server. Every client AND every server would need to call this method for every secure channel create and renew. In addition it requires that a server is also a client to the GDS. But especially small embedded servers have problems to store large CRLs files. In OCSP this problem is solved with OCSP stapling. We should discuss options to use something similar (in this case mainly from client to server) like OCSP stapling. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-09 09:28 | Matthias Damm | New Issue |
