CrySP TWiki Home

CrySP Research Group

Welcome to the home of CrySP. This is a web-based collaboration area for the Cryptography, Security, and Privacy (CrySP) research group. For general information about CrySP, such as a current list of students and publications, see the CrySP.CrySP website.

Site Tools

• Reading Group Topic Schedule

• State of PETs in 2012

Speaker Schedule

Spring 2025 term meetings will be Wednesdays at 1:00 PM, held remotely or hybrid (some people attend from the CrySP lounge).

The rotation is managed by the %ROTATOR_TITLE%, which is currently %ROTATOR%. Ask them if you need to speak on a different date, or want to schedule a practice talk (see below). The meeting is scheduled each term by the %SCHEDULER_TITLE%, which is currently %SCHEDULER%.

Do not modify the above table directly -- just email %ROTATOR%, since only they know everyone's constraints, and need to track modifications to make sure they're persistent.

See the Speaker Archives for past speakers. Speakers must now send a ~3 sentence summary to %NOTETAKER% immediately after their talk (and, at the speaker's discretion, any slides).

Rotation list: Paul Wooseok, Abdulrahman, Ruidi, Benjamin, Alireza, Diogo, Zahra, Steven, Florian, Karim, Lucas, Douglas, Ross, Michael, Vecna, Sujaya, Uzma, Hesam, Anais, David, Mehdi, Qingyang, Aswad, Alexandru, Haoyan, Onur, Sina, Daniel, Adam, Mohammad, Ruizhe, Amir, Rasoul, Haseeb-Ur-Rehman, Vasisht, Andre, Urs, Prach, Anudeep, Anas, Meng, Jaffer, Pranshu, Shanza, Gurjot, Seemal, Mohannad

Out this term: Sergey, Jesse, Ian, Parjanya, Liyi, Yousra, Asokan, Zekun, Chelsea, Hossam, Thomas, Zhiao, Vahid

If you don't see your name on the right list, let %ROTATOR% know.

Giving a CrySP Talk

The goal of these talks is to stay informed of what everyone in the lab is working on and interested in. Typically, speakers present something they're working on or recently finished, but papers you found interesting, background into a subject not all CrySP members would know, or open problems you'd like to see someone work on are all good options as well. See the Speaker Archives for some examples.

The talks are intended to be relatively informal, and there are no strict rules for what they should look like, but as a guideline you should aim for 20-25 minutes to allow time for announcements, setup, and questions.

For slides, a PDF file you can upload to BBB is preferred, since it saves bandwidth and avoids technical difficulties with getting screen sharing working (as a small bonus, it also makes the slides render with higher quality). If you want slide animations, you can use screen sharing, but you should have PDF slides ready as a backup (this is also a good idea for giving presentations in general). PDF uploads will not work for live demos, of course; if you want a backup for those, make slides with screenshots or photos of what the live demo should look like.

Rescheduling a Talk

You can also book practice talks on particular dates with the %ROTATOR_TITLE% (currently %ROTATOR%), either for one speaker slot or the whole meeting (keep in mind whether you would like time for feedback during the meeting). This will replace your normal CrySP talk for the term, if any.

Let the %ROTATOR_TITLE% know as soon as possible if you can't speak this term or on your scheduled date. If you want to cancel with less than a week before your talk is scheduled, and it's not an emergency, please ask a few CrySP members if they would be willing to fill in first. If you find someone willing, let the %ROTATOR_TITLE% know who, otherwise, let them know who you asked so nobody gets asked twice.

In general, the schedule fluctuates a lot, and the %ROTATOR_TITLE% will only let you know if your scheduled speaking date moves if it moves to a date less than two weeks away.

Requested Topics

The following topics have been requested by one or more CrySP members. If you have expertise in the topic, please consider presenting it during your next talk! If there is something you would like to learn more about, feel free to add it to the list (or ask %ROTATOR% to).

*