2010
DOI: 10.1007/978-3-642-13869-0_6
|View full text |Cite
|
Sign up to set email alerts
|

Towards a Trusted Mobile Desktop

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
11
0

Year Published

2011
2011
2013
2013

Publication Types

Select...
5
4
1

Relationship

0
10

Authors

Journals

citations
Cited by 19 publications
(11 citation statements)
references
References 13 publications
0
11
0
Order By: Relevance
“…This approach has been ported to the mobile area [33,3,39]. Although virtualization provides strong isolation, it duplicates the entire Android software stack, which renders those approaches quite heavy-weight in consideration of the scarce battery life of smartphones.…”
Section: Virtualizationmentioning
confidence: 99%
“…This approach has been ported to the mobile area [33,3,39]. Although virtualization provides strong isolation, it duplicates the entire Android software stack, which renders those approaches quite heavy-weight in consideration of the scarce battery life of smartphones.…”
Section: Virtualizationmentioning
confidence: 99%
“…We assume that the software on the handheld is trustworthy and that no malicious software components are installed. Related study that investigates the design of a trustworthy handheld device is presented by, e.g., Selhorst et al [38]. Furthermore, we assume that the handheld is preloaded with the public key certificate of the TrustCenter.…”
Section: Assumptionsmentioning
confidence: 99%
“…In principle, the hardware and software resources needed for user interaction in a TZ-enabled device (e.g., access to the display buffer or the touchscreen input events) can be temporarily reserved for the secure world. A security indicator, such as a colored bar on the top of the screen [23] or a dedicated LED [1] can be used to inform the user about the type of the application he is communicating with (the correct trusted application or a normal world application). However, current smartphones typically do not implement such division of user-interface resources.…”
Section: Password Enrollmentmentioning
confidence: 99%