2011
DOI: 10.1007/978-3-642-25731-5_19
|View full text |Cite
|
Sign up to set email alerts
|

Using Middleware as a Certifying Authority in LBS Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
7
0

Year Published

2012
2012
2012
2012

Publication Types

Select...
3

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(7 citation statements)
references
References 8 publications
0
7
0
Order By: Relevance
“…It requires essential use of a trusted third party for anonymization, and anonymization; in turn serve as a barrier to user authentication (at LBS server end). Also, trusted third party becomes a single point of attack and bottleneck for the system [6]. These limitations can be conquered using zero-knowledge interactive proof systems.…”
Section: Zero Knowledge Proof In Location Privacymentioning
confidence: 99%
See 4 more Smart Citations
“…It requires essential use of a trusted third party for anonymization, and anonymization; in turn serve as a barrier to user authentication (at LBS server end). Also, trusted third party becomes a single point of attack and bottleneck for the system [6]. These limitations can be conquered using zero-knowledge interactive proof systems.…”
Section: Zero Knowledge Proof In Location Privacymentioning
confidence: 99%
“…The certificate generated by middleware (on client's request) is given to client which in turn, handovers it to LSP while asking for the service (figure 1). The encrypted certificate fulfills the authentication and authorization requirements at the LSP servers [6]. This method of authentication can be compared with zero knowledge proof (ZKP) in the manner below:…”
Section: Zero Knowledge Proof In Location Privacymentioning
confidence: 99%
See 3 more Smart Citations