2018
DOI: 10.1109/access.2017.2779131
|View full text |Cite
|
Sign up to set email alerts
|

What Do Software Developers Need to Know to Build Secure Energy-Efficient Android Applications?

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
2
2
1

Relationship

1
4

Authors

Journals

citations
Cited by 7 publications
(2 citation statements)
references
References 29 publications
0
2
0
Order By: Relevance
“…We re-use values published in [19] about energy cost for sending and receiving. We took experimental values from [15] for hash/signature consumption, by adding each verify and signing operation for each protocol we can then have energy consumption for both SEER4US and SOLSR. For SEER4US, messages are signed at every hop but for RSA signature only the first sender performs signature.…”
Section: Discussionmentioning
confidence: 99%
“…We re-use values published in [19] about energy cost for sending and receiving. We took experimental values from [15] for hash/signature consumption, by adding each verify and signing operation for each protocol we can then have energy consumption for both SEER4US and SOLSR. For SEER4US, messages are signed at every hop but for RSA signature only the first sender performs signature.…”
Section: Discussionmentioning
confidence: 99%
“…But, the quality of certain features usually cannot be assessed using a single feature. For example, to adequately assess the energy consumption of an encryption code, we need to specify several features, modelling the different key sizes, modes and paddings [25]. Therefore, we cannot model the energy consumption of an encryption code with an attribute, we need a way to link a complete solution, for example, composed by the features: AES algorithm, Mode CBC, NoPadding, key size = 256, to an energy measurement.…”
Section: Non-functional Requirements Modellingmentioning
confidence: 99%