blob: 14951aa14425ac444556d6a299aa26355a02bc10 (plain
What should be the scope of the paper?
* Introduction of sigsum logging and its architecture (informal)
* what rgdd et al. have now
* Security proof of the sigsum logging architecture (formal)
* rohonk takes the lead here
* Discussion about how to use the basic building block that we modelled
* rgdd takes the lead here
What is the required timeline for this paper?
* not rushed at all, quite busy the coming months
* can provide feedback and be involved in security proof when needed
* can do concrete paper work from March until end of June
* available from November and onwards, can then work full time on paper
Should anyone else be involved?
* rgdd and rohonk both have academic supervisors that can provide feedback
* we are still open for additional contributors
* It looks like ESORICS, with fallback on ACSAC, could work given our timeline
* ESORICS 2022
* Deadline: May 15 , 2022.
* Notification: 21 June 2021.
* Deadline usually in ~June, see http://www.wikicfp.com/cfp/program?id=45
Other conferences that rohonk mentioned
* [rgdd] much harder to get in here, and deadlines are a bit too tight
How do we work together?
* Voice meets on https://meet.sigsum.org/research
* Pads on https://pad.sigsum.org
* (Not persisted in any archive, sort of a scratch pad for now.)
* Source on https://git.sigsum.org/research
* .tex files in sigsum/research repo
* Decision: pick esorics template and start with security proof section
* rgdd will set this up in the near future
What needs to be done for a formal security analysis?
* Define security goals, assumptions, interactions
* Select a proof technique and apply it
* Some related CT papers that can be helpful to take inspiration from
* noise protocol?