mirror of
https://sharelatex.tu-darmstadt.de/git/681e0e7a3a9c7c9c6b8bb298
synced 2025-12-08 05:27:59 +00:00
Update on Overleaf.
This commit is contained in:
@@ -73,7 +73,7 @@ A C-APDU consists of mandatory header fields and optional data and length fields
|
||||
\caption{Structure of a \gls{capdu}}
|
||||
\begin{tabular}{|l|l|l|}
|
||||
\hline
|
||||
\textbf{Field name} & \textbf{Length} & \textbf{Description} \\
|
||||
\textbf{Field name} & \textbf{Length (bytes)} & \textbf{Description} \\
|
||||
\hline \hline
|
||||
$CLA$ & 1 & Instruction Class \\
|
||||
$INS$ & 1 & Instruction Code \ie "SELECT" \\
|
||||
@@ -91,7 +91,7 @@ A C-APDU consists of mandatory header fields and optional data and length fields
|
||||
\caption{Structure of a \gls{rapdu}}
|
||||
\begin{tabular}{|l|l|l|}
|
||||
\hline
|
||||
\textbf{Field name} & \textbf{Length} & \textbf{Description} \\
|
||||
\textbf{Field name} & \textbf{Length (bytes)} & \textbf{Description} \\
|
||||
\hline \hline
|
||||
$Data$ & at most $N_e$ & Response Data \\
|
||||
$SW1$ & 1 & Status Word 1 \\
|
||||
@@ -112,7 +112,7 @@ The status word (SW) in an \gls{rapdu} signifies whether a command was successfu
|
||||
% - it uses a TLV for the encoding of all its information -> tag indicates what kind of data follows, then length to tell the parser how much that to read for this tag, and then the actual data (provide example for BER-TLV ASN1 encoding of some short RSP message)
|
||||
% - the GSMA provides ASN.1 definitions for all of its standardized functions
|
||||
|
||||
When interacting with a \gls{uicc}, either to request or to store data, the command payload is typically structured using \gls{asn1} encoded in the \gls{ber}-\gls{tlv} format. \gls{asn1} is a formal language used to define data structures in a way that is independent of machine-specific encoding. It is a mature and widely adopted technology, particularly within the field of telecommunications, and is standardized by the ITU-T~\cite{oss_nokalva_asn1_nodate}.
|
||||
When interacting with a \gls{uicc}, either to request or to store data, the command payload is typically structured using \gls{asn1} encoded in the \gls{ber}-\gls{tlv} format. \gls{asn1} is a formal language used to define data structures in a way that is independent of machine-specific encoding. It is a mature and widely adopted technology, particularly within the field of telecommunications, and is standardized by the ITU-T~\cite{oss_nokalva_asn1_nodate}. Eventhough its an established encoding standard, it is still prone to be the source of bugs and security vulnerabilities.\cite{nist_nvd_2024, nist_nvd_2025, mitre_cve_2003}
|
||||
|
||||
\gls{asn1} supports a variety of encoding rules. One of the most commonly used in the context of smart cards and mobile communications is the \gls{ber}. In \gls{ber}, all data is encoded as a sequence of \gls{tlv} elements. The \emph{Tag} identifies the type of data, the \emph{Length} specifies the number of bytes used for the value, and the \emph{Value} contains the actual data payload.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user