2016 IEEE 29th Computer Security Foundations Symposium (CSF) 2016
DOI: 10.1109/csf.2016.10
|View full text |Cite
|
Sign up to set email alerts
|

Secure Software Licensing: Models, Constructions, and Proofs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2017
2017
2023
2023

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(6 citation statements)
references
References 15 publications
0
6
0
Order By: Relevance
“…Moraes et al [9] studied common incompatibilities among open-source licenses, compared file-level and project-level license options, and recommended that developers use a file-level multi-licensing model for their code to overcome compatibility issues and offer less restrictive access options. As part of the license management and enforcement, other research proposed using the Markov chain to flag abnormal user behavior, binary analysis tools to detect code cloning, and a Trusted Execution Environment (TEE) to ensure compliance with license agreements [22], [23], [24]. Regarding leveraging blockchain, Stepanova and Erinš [3] suggested using the technology to maintain the history of the software licenses and those who hold the legitimate license, whereas Chiu et al [25] proposed using Ethereum and IPFS for software validation and integrity.…”
Section: A Multi-license Managementmentioning
confidence: 99%
“…Moraes et al [9] studied common incompatibilities among open-source licenses, compared file-level and project-level license options, and recommended that developers use a file-level multi-licensing model for their code to overcome compatibility issues and offer less restrictive access options. As part of the license management and enforcement, other research proposed using the Markov chain to flag abnormal user behavior, binary analysis tools to detect code cloning, and a Trusted Execution Environment (TEE) to ensure compliance with license agreements [22], [23], [24]. Regarding leveraging blockchain, Stepanova and Erinš [3] suggested using the technology to maintain the history of the software licenses and those who hold the legitimate license, whereas Chiu et al [25] proposed using Ethereum and IPFS for software validation and integrity.…”
Section: A Multi-license Managementmentioning
confidence: 99%
“…In addition to attestation, SOC provides confidentiality of the computed values and unicity of the computation. Finally we provide models and an automated analysis of a recent licensing protocol [9] and a one time password protocol [10].…”
Section: Our Contributionsmentioning
confidence: 99%
“…We validate our approach experimentally by checking IEE based protocols existing in the literature, starting from the relatively straightforward attested computation protocol from [3], and following with attested key exchange and secure outsourced computation from the same paper. We also verify the licensing protocol from [9] and a one time password protocol proposed in [10].…”
Section: Implementation and Case Studiesmentioning
confidence: 99%
See 2 more Smart Citations