[PRE REVIEW]: X.509 Compliant Hybrid Certificates for the Post-Quantum Transition

[whedon]

Submitting author: @j-braun (Johannes Braun) Repository: https://github.com/CROSSINGTUD/bc-hybrid-certificates Version: v1.0.0 Editor: @danielskatz Reviewers: @jbasney, @jteheran

Author instructions

Thanks for submitting your paper to JOSS @j-braun. Currently, there isn't an JOSS editor assigned to your paper.

@j-braun if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.

Editor instructions

The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:

@whedon commands

[whedon]

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@whedon commands

What happens now?

This submission is currently in a pre-review state which means we are waiting for an editor to be assigned and for them to find some reviewers for your submission. This may take anything between a few hours to a couple of weeks. Thanks for your patience :smile_cat:

You can help the editor by looking at this list of potential reviewers to identify individuals who might be able to review your submission (please start at the bottom of the list). Also, feel free to suggest individuals who are not on this list by mentioning their GitHub handles here.

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

:point_right: Check article proof :page_facing_up: :point_left:

[arfon]

@j-braun :wave: thanks for your submission to JOSS. From a quick inspection of this submission it's not entirely obvious that it meets our submission criteria. In particular, this item:

• Your software should have an obvious research application

Could you confirm here that there is a research application for this software (and explain what that application is)? The section 'what should my paper contain' has some guidance for the sort of content we're looking to be present in the paper.md.

Many thanks!

[danielskatz]

👋 @j-braun - note that we are waiting for your reply here...

[j-braun]

@arfon @danielskatz - I am sorry for the delayed answer. I was busy the past days and did not have the possibility to track the issue all the time. So here is the answer to your question in regard to research applictions: Our software was designed to be used by (post-quantum) cryptography researchers and IT security practitioners. It’s goal is to enable researchers to extensively test their newly designed schemes in real world environments and to demonstrate their practicality. This is a very important aspect on that field of research as it allows insights and gives valuable hints in regard to optimization and parameter setting. A prior mock-up implementation was for example used for the following publication, which we also reference in the paper: “N. Bindel, U. Herath, M. McKague, and D. Stebila. Transitioning to a quantum resistant public key infrastructure. In T. Lange and T. Takagi, editors, Post-Quantum Cryptography, pages 384{405, Cham, 2017. Springer International Publishing.” The mock up implementation was used to do a first evaluation of the hybrid certificate approach in conjunction with the Q-TESLA scheme designed by Bindel at al. Our software now allows a more thorough evaluation of such schemes.

Should we explicitly add this to the paper?

[j-braun]

@whedon - potential reviewers could be:

• gcdeshpande
• trp07

[j-braun]

@whedon commands

[whedon]

Here are some things you can ask me to do:

# List Whedon's capabilities
@whedon commands

# List of editor GitHub usernames
@whedon list editors

# List of reviewers together with programming language preferences and domain expertise
@whedon list reviewers

EDITORIAL TASKS

# Compile the paper
@whedon generate pdf

# Compile the paper from alternative branch
@whedon generate pdf from branch custom-branch-name

# Ask Whedon to check the references for missing DOIs
@whedon check references

[j-braun]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

:point_right: Check article proof :page_facing_up: :point_left:

[danielskatz]

@j-braun - we have rotating associate editors-in-chief, which is why two of us have asked about this, and this week, we'll let a third (@kyleniemeyer) reply and follow-up...

[kyleniemeyer]

Hi @j-braun, thanks for your explanation. Yes, please do add some description of the research applications of the software to your paper; this may be most helpful near the beginning.

[kyleniemeyer]

@danielskatz can you serve as editor for this submission?

[danielskatz]

@whedon assign @danielskatz as editor

[whedon]

OK, the editor is @danielskatz

[danielskatz]

👋 @gcdeshpande & @trp07 - would you be willing to review this JOSS submission?

[danielskatz]

👋 @jbasney - would you be willing to review this JOSS submission? Or perhaps suggest others who would be well-suited. See the paper above and info on JOSS reviewing

[jbasney]

Yes I can do the review this weekend. -Jim

[danielskatz]

Thanks Jim - I'll assign you as a reviewer, but we won't start the review until I also get another reviewer assigned.

[danielskatz]

@whedon assign @jbasney as reviewer

[whedon]

OK, the reviewer is @jbasney

[j-braun]

Hi @danielskatz , just added some text regarding research applications to the paper as @kyleniemeyer requested.

[danielskatz]

@jbasney - do you have any thoughts on another reviewer?

[jbasney]

@jbasney - do you have any thoughts on another reviewer?

Yes, I think @msalle @DrDaveD @jteheran @zsshah & @djw8605 would all be good reviewers if they are available.

[danielskatz]

👋 @msalle @DrDaveD @jteheran @zsshah & @djw8605 - would one of you be willing to review this submission for JOSS? See the paper above and info on JOSS reviewing

[jteheran]

I can review it. Is there a deadline?

[danielskatz]

Thanks @jteheran - it's an open interactive process, so there's not exactly a deadline, but we like to have reviewers provide initial feedback in a couple of weeks, if possible

[danielskatz]

@whedon add @jteheran as reviewer

[whedon]

OK, @jteheran is now a reviewer

[danielskatz]

@whedon start review

[whedon]

OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/1606. Feel free to close this issue now!