Toots for lavados@infosec.exchange account

Written by Daniel Gruss on 2025-01-28 at 14:14

DIMVA decisions were just sent out. Congratulations to all authors who got and accept!

If your paper was not accepted, the uASC deadline is in 22 hours (same length+format) and uASC is looking for interesting insights despite flaws in the threat model -> uasc.cc

=> More informations about this toot | View the thread

Written by Daniel Gruss on 2025-01-26 at 12:54

We updated the uASC deadline: it is January 28 AoE, which is 1 day after the DIMVA notification.

Take a look at our CFP. Any insights around microarchitecture security are interesting.

https://uasc.cc/

=> More informations about this toot | View the thread

Written by Daniel Gruss on 2025-01-21 at 23:25

hyperref unfortunately can add deanonymizing information to PDFs. I posted a patch + a two-liner cp/sed here: https://github.com/latex3/hyperref/issues/376

Run that and get an anonymized PDF that does not contain all your bibkeys.

=> More informations about this toot | View the thread

Written by Daniel Gruss on 2025-01-21 at 22:52

The uASC registration is open now:

https://uasc.cc/

Also the uASC deadline is approaching: January 27 AoE.

We accept papers, posters, and talks. We have conference proceedings. We're interested in any insights broadly around microarchitecture security.

Don't miss the deadline, don't miss the conference ;)

=> More informations about this toot | View the thread

Written by Daniel Gruss on 2025-01-20 at 22:20

It's kind of like werewolves (aka Mafia aka secret Hitler) but nothing is ever revealed. No one learns anyone else's role at any point in the game. Any arguments and votes are handed in in written form.

The only thing that is revealed is how the process concluded, i.e., with one or the other outcome.

=> More informations about this toot | View the thread

Written by Daniel Gruss on 2025-01-20 at 19:53

Can I ask you all for a quick review of this idea?

Threat Model and Attack Scenario:

PC member A and B agree to not mark each other as a conflict and write each other favorable reviews and fight for each others papers.

Proposed Mitigation:

• Remove access of PC member A and B from all papers except the ones they are assigned

• Remove visibility of PC member A's and B's names from other reviewers

Conclusion:

Our approach solves the problem. PC member A and B cannot write each other favorable reviews or fight for each other's paper anymore.

Hoping for typical reviews from security folks here that identify any weaknesses or potential side effects ;)

=> More informations about this toot | View the thread

Written by Daniel Gruss on 2025-01-05 at 16:40

CFP for uASC 25 is still open. We have rolling reviews, and 1 submission is already accepted. If you have interesting results on microarchitecture security (incl. weak threat models or reproducing prior work), check out the CFP at http://uasc.cc

The CFP closes Jan 28

We look for contributions from academia and industry and accept papers, posters, and talks. Or just attend uASC 25 on February 19 in Bochum and meet fellow microarchitecture security researchers.

=> More informations about this toot | View the thread

Written by Daniel Gruss on 2024-12-26 at 21:51

I'm at #38c3 this year. Just ping me if you want to meet.

=> More informations about this toot | View the thread

Written by Daniel Gruss on 2024-12-17 at 15:09

If you are in #Graz tomorrow, join us for the last IAIK Christmas Special ever. 17:30 @ HS i13.

=> View attached media

=> More informations about this toot | View the thread

Written by Daniel Gruss on 2024-12-01 at 16:03

Got some negative or unrealistic threat model results that still bring interesting insights? A side channel that requires root to leak something from the kernel? Reproducing prior work? Somewhat related to microarchitecture? Here's your venue: uasc.cc

First edition is happening on February 19 in Bochum, the day before RuhrSec.

We accept submissions (papers, posters, talks) starting today and try to provide reviews within a 2 week time frame of submission.

Last Submission Deadline: January 27, 2025

=> More informations about this toot | View the thread

=> This profile with reblog | Go to lavados@infosec.exchange account