HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
FPSG-UIUC
lotr
C2021–2021
FPSG-UIUC / lotr

lotr

Source code of the paper "Lord of the Ring(s): Side Channel Attacks on the CPU On-Chip Ring Interconnect Are Practical"

2Distinct people
2Mentions
0Explicit recommenders
145GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Source code of the paper "Lord of the Ring(s): Side Channel Attacks on the CPU On-Chip Ring Interconnect Are Practical"

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2021-03-08 05:51:18 UTC to 2021-03-08 13:29:54 UTC.

012021-03-08 05:00:00 UTC to 2021-03-08 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 8, 05:002021-03-08 06:00:00 UTC to 2021-03-08 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-08 07:00:00 UTC to 2021-03-08 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-08 08:00:00 UTC to 2021-03-08 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-08 09:00:00 UTC to 2021-03-08 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 8, 09:002021-03-08 10:00:00 UTC to 2021-03-08 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-08 11:00:00 UTC to 2021-03-08 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-08 12:00:00 UTC to 2021-03-08 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-08 13:00:00 UTC to 2021-03-08 14:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 8, 13:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 8, 05:002021-03-08 05:00:00 UTC2021-03-08 06:00:00 UTC101
Mar 8, 06:002021-03-08 06:00:00 UTC2021-03-08 07:00:00 UTC000
Mar 8, 07:002021-03-08 07:00:00 UTC2021-03-08 08:00:00 UTC000
Mar 8, 08:002021-03-08 08:00:00 UTC2021-03-08 09:00:00 UTC000
Mar 8, 09:002021-03-08 09:00:00 UTC2021-03-08 10:00:00 UTC000
Mar 8, 10:002021-03-08 10:00:00 UTC2021-03-08 11:00:00 UTC000
Mar 8, 11:002021-03-08 11:00:00 UTC2021-03-08 12:00:00 UTC000
Mar 8, 12:002021-03-08 12:00:00 UTC2021-03-08 13:00:00 UTC000
Mar 8, 13:002021-03-08 13:00:00 UTC2021-03-08 14:00:00 UTC110

What Hacker News says

2 sources
This is a great paper, really well explained. The source code: https://github.com/FPSG-UIUC/lotr The TL;DR is that the L3 cache (LLC: Last Level Cache) is shared between all cores on the chip, but the L3 is composed of a number of slices colocated with each core: the L3 is actually CC-NUMA! There is contention when reading/writing to the L3 via the ring interconnect, which can be used to identify the memory addresses access patterns of the cache. There's a bit more covering how the L1/L2 caches, private to each core, are revealed via the set inclusivity properly of Intel's cache design. In monitoring LLC it is similar to https://eprint.iacr.org/2015/898.pdf though it doesn't reference them. It isn't a game over attack but it reinforces how sharing resources (cache, memory, cores) is a bad idea when that crosses a security boundary. VM exc
Read the rest
lusive cache regions (Intel CAT cache partitioning) and cache locking should help, but cache slice partitioning is reqd too.
In Lord of the Ring(s): Side Channel Attacks on the CPU On-Chip Ring Interconnect

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.