2022
DOI: 10.1007/978-3-030-99277-4_2
|View full text |Cite
|
Sign up to set email alerts
|

Revisiting Driver Anonymity in ORide

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
4
2

Relationship

1
5

Authors

Journals

citations
Cited by 8 publications
(2 citation statements)
references
References 21 publications
0
2
0
Order By: Relevance
“…Note that LBS knows (𝑥 1 , 𝑦 1 ), i.e., as plaintexts. If (𝑋 𝑣𝑎 , 𝑌 𝑣𝑎 ) are encoded as (scaled) integers, then it will only have a "couple" of solutions on an average [8]. But to keep things simple, we can write similar equations for 𝑑 2 , 𝑑 3 , ....…”
Section: Security Implicationsmentioning
confidence: 99%
“…Note that LBS knows (𝑥 1 , 𝑦 1 ), i.e., as plaintexts. If (𝑋 𝑣𝑎 , 𝑌 𝑣𝑎 ) are encoded as (scaled) integers, then it will only have a "couple" of solutions on an average [8]. But to keep things simple, we can write similar equations for 𝑑 2 , 𝑑 3 , ....…”
Section: Security Implicationsmentioning
confidence: 99%
“…They use homomorphic encryption to compute the Euclidean distance and identify the closest driver in a zone. [5] proposes a modification to ORide to ensure location privacy of responding drivers in the region with respect to a rider.…”
Section: Algorithm 1: Rv Recovers Quadtreementioning
confidence: 99%