|
1 | 1 | { |
2 | 2 | "magic": "E!vIA5L86J2I", |
3 | | - "timestamp": "2025-02-25T00:17:08.292851+00:00", |
| 3 | + "timestamp": "2025-02-27T00:17:08.894684+00:00", |
4 | 4 | "repo": "chris-wood/draft-bmw-tls-pake13", |
5 | 5 | "labels": [ |
6 | 6 | { |
|
570 | 570 | "updatedAt": "2025-02-07T20:34:23Z", |
571 | 571 | "closedAt": null, |
572 | 572 | "comments": [] |
| 573 | + }, |
| 574 | + { |
| 575 | + "number": 25, |
| 576 | + "id": "I_kwDOM83jm86rlUO3", |
| 577 | + "title": "Allow certificates with PAKE negotiation", |
| 578 | + "url": "https://github.com/chris-wood/draft-bmw-tls-pake13/issues/25", |
| 579 | + "state": "OPEN", |
| 580 | + "author": "chris-wood", |
| 581 | + "authorAssociation": "OWNER", |
| 582 | + "assignees": [], |
| 583 | + "labels": [], |
| 584 | + "body": "The draft currently prohibits certificate-based authentication when PAKEs are negotiated, primarily to align with RFC8446 semantics. However, multiple people have suggested this is unnecessarily restrictive, and does in fact rule out some important use cases. One such use case is where a client wishes to authenticate with a certificate as well as use the PAKE to authenticate the server.", |
| 585 | + "createdAt": "2025-02-25T15:01:07Z", |
| 586 | + "updatedAt": "2025-02-25T15:01:07Z", |
| 587 | + "closedAt": null, |
| 588 | + "comments": [] |
| 589 | + }, |
| 590 | + { |
| 591 | + "number": 26, |
| 592 | + "id": "I_kwDOM83jm86rlVbd", |
| 593 | + "title": "Make future PAKE integration constraints more clear", |
| 594 | + "url": "https://github.com/chris-wood/draft-bmw-tls-pake13/issues/26", |
| 595 | + "state": "OPEN", |
| 596 | + "author": "chris-wood", |
| 597 | + "authorAssociation": "OWNER", |
| 598 | + "assignees": [], |
| 599 | + "labels": [], |
| 600 | + "body": "Future PAKESchemes may require more round trips than what is required for the SPAKE2+ scheme. We should make this clear in the document.", |
| 601 | + "createdAt": "2025-02-25T15:02:51Z", |
| 602 | + "updatedAt": "2025-02-25T15:08:05Z", |
| 603 | + "closedAt": null, |
| 604 | + "comments": [ |
| 605 | + { |
| 606 | + "author": "chris-wood", |
| 607 | + "authorAssociation": "OWNER", |
| 608 | + "body": "We should also state the requirements for each PAKEScheme. For example, they MUST provide the same security properties as the NamedGroup-based key exchange, such as forward secrecy.", |
| 609 | + "createdAt": "2025-02-25T15:08:03Z", |
| 610 | + "updatedAt": "2025-02-25T15:08:03Z" |
| 611 | + } |
| 612 | + ] |
573 | 613 | } |
574 | 614 | ], |
575 | 615 | "pulls": [ |
|
0 commit comments