From e12765bd4abf2208098bdaceddeeaf834daa50cb Mon Sep 17 00:00:00 2001 From: nb72soza Bittner Date: Thu, 29 May 2025 20:48:46 +0000 Subject: [PATCH] Update on Overleaf. --- Chapters/Implementation.tex | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/Chapters/Implementation.tex b/Chapters/Implementation.tex index 546c450..8c9c658 100644 --- a/Chapters/Implementation.tex +++ b/Chapters/Implementation.tex @@ -423,7 +423,6 @@ After multiple cards are fuzzed with the same scenario, their corresponding muta This differential testing method highlights edge-case inconsistencies across \gls{euicc} vendors and enables systematic validation of the \gls{rsp} protocol compliance. - \begin{figure} \centering \input{Graphics/record_scenario_flow.tikz} @@ -435,5 +434,13 @@ This differential testing method highlights edge-case inconsistencies across \gl \subsection{Data Fuzzing} \label{subsec:data_fuzzing} +% Problem with apdu fuzzing: often producing not valid ASN1 structured data due to bit flips etc -> need to fuzz input data +% goal leverage lpa to fuzz input data and see how the esim behaves +% oss-fuzz global project with the goal to make open source software more secure and stable by using fuzzing teqniques (ref oss-fuzz) +% oss-fuzz proposes multiple fuzzer for python implementation among them are the atheris fuzzer aswell as the python hypothesis framework +% atheris coverage guided fuzzer to fuzz python code directly -> not our use case +% python hypothesis: propery based testing library for python -> define input structure which needs to be passed into function -> hypothesis generates random input data that adheres to defined structure and tests for edge cases i.e. fuzzing +% + \section{CLI} \label{sec:cli}