Skip to content

Commit f8a51b3

Browse files
authored
Update master-thesis.md
1 parent 876b9fb commit f8a51b3

File tree

1 file changed

+2
-41
lines changed

1 file changed

+2
-41
lines changed

master-thesis.md

Lines changed: 2 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -36,45 +36,6 @@ Solidity development.</p>
3636
<li ><p><a href="https://sourcify.dev/">Sourcify</a></p>
3737
</li></ol>
3838

39-
<h3 >Zero-knowledge software bills of materials</h3>
40-
41-
Contact: Javier Ron
42-
43-
<p>Description: Software bills of materials (SBOMs) are complete lists of software components [1], these can be helpful in tracing vulnerabilities, license compliance, etc. However, revealing an SBOM publicly also means revealing said vulnerabilities to malicious actors. Furthermore, some proprietary software developers advocate for access control for SBOM distribution [2].
44-
Zero-knowledge proofs allows a party to convey that a statement is true without disclosing any additional information. [3]
45-
You will design, develop, and evaluate a zero-knowledge SBOM system, which allows developers to disclose limited, but verifiable SBOM information to authorized users.</p>
46-
<ol>
47-
<li ><p>The Minimum Elements For a Software Bill of Materials https://www.ntia.doc.gov/files/ntia/publications/sbomminimumelementsreport.pdf</p>
48-
</li>
49-
<li ><p>An Empirical Study on Software Bill of Materials: Where We Stand and the Road Ahead http://arxiv.org/abs/2301.05362</p>
50-
</li>
51-
<li ><p>Zero-knowledge proof https://en.wikipedia.org/wiki/Zero-knowledgeproof</p>
52-
</li>
53-
<li ><p><a href="https://arxiv.org/abs/2307.02088">Trust in Software Supply Chains: Blockchain-Enabled SBOM and the AIBOM Future 2024</a></p>
54-
</li></ol>
55-
56-
<h3 >Study of non-reproducible builds in the Java ecosystem</h3>
57-
<p>Description: Build Reproducibility means that a software build
58-
always results in a bit-by-bit identical output provided the source code
59-
and build environment is also the exact same [1]. This property is a
60-
good safeguard against compromised build process threat [2] and
61-
hence it is an important safeguard for software supply chain security.
62-
In Java
63-
ecosystem,&nbsp;<a href="https://github.com/jvm-repo-rebuild/reproducible-central">Reproducible
64-
Central</a>&nbsp;attempts to reproduce Maven/Gradle/sbt artifacts
65-
on&nbsp;<a href="https://mvnrepository.com/">Maven Central</a>. It does so&nbsp;by
66-
building the artifact from source and then comparing it with the
67-
artifact in Maven registry. If it is bit-by-bit identical, then the
68-
maven package is said to be reproducible, else the package is
69-
non-reproducible. In this thesis, you will create a taxonomy of reasons
70-
for non-reproducible builds of Maven packages.</p>
71-
<ol>
72-
<li ><p><a href="https://reproducible-builds.org/">https://reproducible-builds.org/</a></p>
73-
</li>
74-
<li ><p><a href="https://dl.acm.org/doi/10.1145/3643764">AROMA:
75-
Automatic Reproduction of Maven Artifacts</a></p>
76-
</li></ol>
77-
7839
<h3 >Dynamic Integrity Verification &amp; Repair for Java Applications</h3>
7940
Contact: Martin Monperrus
8041
<p>Description:
@@ -123,8 +84,8 @@ captures and standardizes the JIT compilation process, enabling developers to re
12384
assess the impact of reproducible JIT compilation on software reliability, debugging, and performance, ultimately contributing to the development of more robust and
12485
trustworthy software systems.</p>
12586
<ol>
126-
<li > [Recompilation for debugging support in a JIT-compiler](https://doi.org/10.1145/634636.586100) </li>
127-
<li > [https://github.com/rschwietzke/jmh-C2-compile](https://github.com/rschwietzke/jmh-C2-compile) </li>
87+
<li > <a href="https://doi.org/10.1145/634636.586100">Recompilation for debugging support in a JIT-compiler</a> </li>
88+
<li > <a href="https://github.com/rschwietzke/jmh-C2-compile">https://github.com/rschwietzke/jmh-C2-compile</a> </li>
12889
<ol>
12990

13091

0 commit comments

Comments
 (0)