[hackathon] PQC X.509 115 Hackathon pre meeting October 31st at 10am EST

[John Gray <[e-mail]>]

I realize I failed to mention a time for our PQC x.509 pre-hackathon meeting.   This is the first hackathon I will be attending, so please forgive my newness of trying to organize this hackathon event…  😊

I am hoping it will be a fun way for us to collaborate with these new PQC key formats.   😊

For the pre-hackathon meeting we will be in gather.town on Monday the 31st in the Hackathon room table G at 10:00am EST (Easter Standard Time).
https://www.ietf.org/how/meetings/gather/

I have made up some slides, but it looks like they were blocked.   My colleague Mike Ounsworth copied the content into this google document

https://docs.google.com/document/d/1A2-D82du0qJjygvBuOlG8Xao3MzDYz1pRDzjT9eY6ls/edit?usp=sharing

Hopefully I covered everything this time.

If you can’t make this pre-meeting that is okay, we look forward to seeing you at the PQC X.509 Hackathon


Cheers,

John Gray


From: John Gray
Sent: Friday, October 21, 2022 6:33 PM
To: Mike Ounsworth <Mike.Ounsworth=[e-mail]>; 'LAMPS' <[e-mail]>; [e-mail]; [e-mail]
Cc: [e-mail]; Felipe Ventura <[e-mail]>; [e-mail]; Railean, Alexander <[e-mail]>; Kretschmer, Andreas <[e-mail]>; Tim Hollebeek <[e-mail]>; Max Pala <[e-mail]>; Michael Richardson <[e-mail]>; Sofía Celi <[e-mail]>; [e-mail]; Klaußner, Jan <[e-mail]>; Florence D <[e-mail]>; Vaira, Antonio <[e-mail]>; Serge Mister <[e-mail]>; David Hook <[e-mail]>
Subject: RE: PQC X.509 115 Hackathon

Thanks for your interesting in the PQ Keys and Signatures in X.509 / PKIX Hackathon.   I have tried to cc those people who have expressed interest in the hackathon either via email or by discussion.   Some of you may already know each other, some of you may not.   If I forgot to include you, I apologize.   You are welcome to attend.

We are planning a pre-hackathon meeting Monday October 31st in the IETF’s gather.town in the Hackathon room table G.
https://www.ietf.org/how/meetings/gather/

This will allow everyone to test their A/V and so we can sync up about what we want to hack at.     If you can’t make the meeting, that is okay, let me know and I will send you notes.

Suggested Agenda:

  1.  Introductions
  2.  Discuss Scope (What do people want to test).  I put together this slide deck today which covers much of the scope that I envision.  Hopefully it goes through email without an issue.   Obviously it is not exhaustive, but gives a good starting point for those who may just be starting to take a look at this.

Cheers,

John Gray
Entrust



From: John Gray
Sent: Wednesday, October 12, 2022 8:20 PM
To: Mike Ounsworth <Mike.Ounsworth=[e-mail]<mailto:Mike.Ounsworth=[e-mail]>>; 'LAMPS' <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: RE: PQC X.509 115 Hackathon

Thank you for all your comments and suggestions in regards to a PQC X.509 Hackathon.   We have added the details of this hackathon topic to the IETF Hackathon Wiki located here as ‘PQ keys and signatures in X.509 / PKIX’

https://wiki.ietf.org/en/meeting/115/hackathon

We hope that at least one author for each of these drafts is able to join in some capacity so we can attempt to come to a consensus on the key and signature formats of the PQ finalist algorithms.


  *   https://datatracker.ietf.org/doc/html/draft-uni-qsckeys-00.html
  *   https://datatracker.ietf.org/doc/draft-massimo-lamps-pq-sig-certificates/
We plan to distribute a set of OIDS we will use to identify the key and signature formats (we need those to interoperate with the various X.509 structures like PublicKeyInfo, PrivateKeyInfo, X509Certificate, PKCS10, X509CRL, OSCP, CMS, etc).   Ideally we suggest that these are done in an agile way in software to make it easier to plug in the real OID values once they have been officially registered.  We will use formats already suggested in existing drafts whenever possible.

I know there have already been multiple key format proposals for some of the PQ key and Signature drafts, so we can use different OIDs to designate different formats if we want to test with different key and signature formats for the same algorithms.   If there are key and signature formats that aren’t included in the list we provide, please suggest and add to the list.

I plan to add this information into the IETF GitHub repository in the next week, so stay tuned!

If there is something you think we have missed, please let us know.

Cheers,

John Gray
Entrust




From: Spasm <[e-mail]<mailto:[e-mail]>> On Behalf Of Mike Ounsworth
Sent: Tuesday, October 4, 2022 9:01 PM
To: 'LAMPS' <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Subject: [EXTERNAL] [lamps] PQC X.509 115 Hackathon

WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the content is safe.
________________________________
Hi LAMPS and people interested in PQC!

As suggested at 114, my colleague John Gray and I would like to do a 115 Hackathon on PQ keys and signatures in X.509 / PKIX.

We are suggesting to play with Dilithium, Falcon, Sphincs+, and Composite signing algorithms in Certs, CRLs, CSRs, PKCS#12s, CMS SignedData, maybe OCSP Responses, maybe Timestamping, maybe CMP. We can bring: the Entrust Toolkit (which we can hack at), Bounce Castle, OpenQuantumSafe-openssl, OpenCA (easier if Max Pala is there, but we can probably figure out how to build it).

The point of the hackathon, I think, is going to be OIDs, and public key / private key formats (ex.: the differences between Dilithium and Falcon encodings in draft-uni-qsckeys, and draft-massimo-lamps-pq-sig-certificates).



Question 1: are others interested in joining us at the hackathon? (no point is signing up for a hackathon spot if we’re the only ones there)

Question 2: whether or not you're joining, what PQ X.509 / PKIX things would you like to see working with Dilithium, Falcon, Sphincs+, Composite?


---
Mike Ounsworth
Software Security Architect, Entrust

Any email and files/attachments transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.