2019
DOI: 10.1007/978-3-030-36033-7_10
|View full text |Cite
|
Sign up to set email alerts
|

Stronger Lower Bounds for Online ORAM

Abstract: Oblivious RAM (ORAM), introduced in the context of software protection by Goldreich and Ostrovsky [JACM'96], aims at obfuscating the memory access pattern induced by a RAM computation. Ideally, the memory access pattern of an ORAM should be independent of the data being processed. Since the work of Goldreich and Ostrovsky, it was believed that there is an inherent Ω(log n) bandwidth overhead in any ORAM working with memory of size n. Larsen and Nielsen [CRYPTO'18] were the first to give a general Ω(log n) low… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
8
0

Year Published

2020
2020
2022
2022

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 12 publications
(8 citation statements)
references
References 23 publications
0
8
0
Order By: Relevance
“…Removing Read operations from traces is also preferable because an analogue of Lem. 2 will show that including will lead to a trace-oriented PD definition that is equivalent to ORAMs (instead of write-only ORAMs), thus suffering ORAMs' efficiency lower-bounds [5,20,22,27,47].…”
Section: Independence Of Storage Layersmentioning
confidence: 99%
See 1 more Smart Citation
“…Removing Read operations from traces is also preferable because an analogue of Lem. 2 will show that including will lead to a trace-oriented PD definition that is equivalent to ORAMs (instead of write-only ORAMs), thus suffering ORAMs' efficiency lower-bounds [5,20,22,27,47].…”
Section: Independence Of Storage Layersmentioning
confidence: 99%
“…2. Thus, it will suffer from ORAMs' efficiency lower bound [5,20,22,27,47]. For example, HIVE [4] can be proven secure even if Read leaves traces; indeed, it employs this actively by explaining a hidden access as a public Read.…”
Section: Unified Definitionmentioning
confidence: 99%
“…Removing Read operations from traces is also preferable because an analogue of Lem. 2 will show that including will lead to a traceoriented PD definition that is equivalent to ORAMs (instead of write-only ORAMs), thus suffering ORAMs' efficiency lower-bounds [20,5,27,47,22].…”
Section: Independence Of Storage Layersmentioning
confidence: 99%
“…suffer from ORAMs' efficiency lower bound [20,5,27,47,22]. For example, HIVE [4] can be proven secure even if Read leaves traces; indeed, it employs this actively by explaining a hidden access as a public Read.…”
Section: Unified Definitionmentioning
confidence: 99%
See 1 more Smart Citation