diff --git a/Degate-2024/Degate 2024.pdf b/Degate-2024/Degate 2024.pdf new file mode 100644 index 0000000..3ca49f6 Binary files /dev/null and b/Degate-2024/Degate 2024.pdf differ diff --git a/Degate-2024/LICENSE b/Degate-2024/LICENSE new file mode 100644 index 0000000..0e259d4 --- /dev/null +++ b/Degate-2024/LICENSE @@ -0,0 +1,121 @@ +Creative Commons Legal Code + +CC0 1.0 Universal + + CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE + LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN + ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS + INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES + REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS + PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM + THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED + HEREUNDER. + +Statement of Purpose + +The laws of most jurisdictions throughout the world automatically confer +exclusive Copyright and Related Rights (defined below) upon the creator +and subsequent owner(s) (each and all, an "owner") of an original work of +authorship and/or a database (each, a "Work"). + +Certain owners wish to permanently relinquish those rights to a Work for +the purpose of contributing to a commons of creative, cultural and +scientific works ("Commons") that the public can reliably and without fear +of later claims of infringement build upon, modify, incorporate in other +works, reuse and redistribute as freely as possible in any form whatsoever +and for any purposes, including without limitation commercial purposes. +These owners may contribute to the Commons to promote the ideal of a free +culture and the further production of creative, cultural and scientific +works, or to gain reputation or greater distribution for their Work in +part through the use and efforts of others. + +For these and/or other purposes and motivations, and without any +expectation of additional consideration or compensation, the person +associating CC0 with a Work (the "Affirmer"), to the extent that he or she +is an owner of Copyright and Related Rights in the Work, voluntarily +elects to apply CC0 to the Work and publicly distribute the Work under its +terms, with knowledge of his or her Copyright and Related Rights in the +Work and the meaning and intended legal effect of CC0 on those rights. + +1. Copyright and Related Rights. A Work made available under CC0 may be +protected by copyright and related or neighboring rights ("Copyright and +Related Rights"). Copyright and Related Rights include, but are not +limited to, the following: + + i. the right to reproduce, adapt, distribute, perform, display, + communicate, and translate a Work; + ii. moral rights retained by the original author(s) and/or performer(s); +iii. publicity and privacy rights pertaining to a person's image or + likeness depicted in a Work; + iv. rights protecting against unfair competition in regards to a Work, + subject to the limitations in paragraph 4(a), below; + v. rights protecting the extraction, dissemination, use and reuse of data + in a Work; + vi. database rights (such as those arising under Directive 96/9/EC of the + European Parliament and of the Council of 11 March 1996 on the legal + protection of databases, and under any national implementation + thereof, including any amended or successor version of such + directive); and +vii. other similar, equivalent or corresponding rights throughout the + world based on applicable law or treaty, and any national + implementations thereof. + +2. Waiver. To the greatest extent permitted by, but not in contravention +of, applicable law, Affirmer hereby overtly, fully, permanently, +irrevocably and unconditionally waives, abandons, and surrenders all of +Affirmer's Copyright and Related Rights and associated claims and causes +of action, whether now known or unknown (including existing as well as +future claims and causes of action), in the Work (i) in all territories +worldwide, (ii) for the maximum duration provided by applicable law or +treaty (including future time extensions), (iii) in any current or future +medium and for any number of copies, and (iv) for any purpose whatsoever, +including without limitation commercial, advertising or promotional +purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each +member of the public at large and to the detriment of Affirmer's heirs and +successors, fully intending that such Waiver shall not be subject to +revocation, rescission, cancellation, termination, or any other legal or +equitable action to disrupt the quiet enjoyment of the Work by the public +as contemplated by Affirmer's express Statement of Purpose. + +3. Public License Fallback. Should any part of the Waiver for any reason +be judged legally invalid or ineffective under applicable law, then the +Waiver shall be preserved to the maximum extent permitted taking into +account Affirmer's express Statement of Purpose. In addition, to the +extent the Waiver is so judged Affirmer hereby grants to each affected +person a royalty-free, non transferable, non sublicensable, non exclusive, +irrevocable and unconditional license to exercise Affirmer's Copyright and +Related Rights in the Work (i) in all territories worldwide, (ii) for the +maximum duration provided by applicable law or treaty (including future +time extensions), (iii) in any current or future medium and for any number +of copies, and (iv) for any purpose whatsoever, including without +limitation commercial, advertising or promotional purposes (the +"License"). The License shall be deemed effective as of the date CC0 was +applied by Affirmer to the Work. Should any part of the License for any +reason be judged legally invalid or ineffective under applicable law, such +partial invalidity or ineffectiveness shall not invalidate the remainder +of the License, and in such case Affirmer hereby affirms that he or she +will not (i) exercise any of his or her remaining Copyright and Related +Rights in the Work or (ii) assert any associated claims and causes of +action with respect to the Work, in either case contrary to Affirmer's +express Statement of Purpose. + +4. Limitations and Disclaimers. + + a. No trademark or patent rights held by Affirmer are waived, abandoned, + surrendered, licensed or otherwise affected by this document. + b. Affirmer offers the Work as-is and makes no representations or + warranties of any kind concerning the Work, express, implied, + statutory or otherwise, including without limitation warranties of + title, merchantability, fitness for a particular purpose, non + infringement, or the absence of latent or other defects, accuracy, or + the present or absence of errors, whether or not discoverable, all to + the greatest extent permissible under applicable law. + c. Affirmer disclaims responsibility for clearing rights of other persons + that may apply to the Work or any use thereof, including without + limitation any person's Copyright and Related Rights in the Work. + Further, Affirmer disclaims responsibility for obtaining any necessary + consents, permissions or other rights required for any use of the + Work. + d. Affirmer understands and acknowledges that Creative Commons is not a + party to this document and has no duty or obligation with respect to + this CC0 or use of the Work. diff --git a/Degate-2024/sources/.gitignore b/Degate-2024/sources/.gitignore new file mode 100644 index 0000000..d1ec76a --- /dev/null +++ b/Degate-2024/sources/.gitignore @@ -0,0 +1,10 @@ +*.aux +*.gz +*.log +*.nav +*.out +*.snm +*.toc +*.snm +*.bbl +*.blg diff --git a/Degate-2024/sources/Degate 2024.tex b/Degate-2024/sources/Degate 2024.tex new file mode 100644 index 0000000..4058a37 --- /dev/null +++ b/Degate-2024/sources/Degate 2024.tex @@ -0,0 +1,1105 @@ +\documentclass[aspectratio=169]{beamer} +\usetheme{AnnArbor} + +\definecolor{degatered}{rgb}{0.902,0.22,0.161} +\setbeamercolor{titlelike}{parent=structure,fg=white,bg=degatered} +\setbeamercolor*{palette primary}{bg=degatered!50!black,fg=white} +\setbeamercolor*{palette secondary}{bg=degatered!40!black,fg=white} +\setbeamercolor*{palette tertiary}{bg=degatered!30!black,fg=white} +\setbeamercolor*{palette quaternary}{bg=degatered!20!black,fg=white} +\setbeamercolor{frametitle}{bg=degatered} +\setbeamercolor{frametitle right}{bg=degatered!60!black} +\setbeamertemplate{bibliography item}{\insertbiblabel} + +\usepackage{tikz} + +\title{\textbf{\underline{Degate}}} +\subtitle{The stakes and challenges of silicon reverse engineering \\ \url{https://www.degate.org}} +\titlegraphic{\includegraphics[width=2cm]{res/degate.png}} +\author{\textbf{D.~Bachelot}} +\date{\textbf{\underline{Degate Community}},\\ 2024} +\logo{\includegraphics[scale=0.08]{res/degate.png}} + +\AtBeginSection[ ] +{ + \begin{frame}{} + \tableofcontents[currentsection] + \end{frame} +} + +\begin{document} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\begin{frame}[plain] + \maketitle +\end{frame} +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\begin{frame}{} + \tableofcontents +\end{frame} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\section{Silicon Chips Reverse Engineering} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + \subsection{Introduction} + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + \begin{frame}{} + \tableofcontents[currentsection, currentsubsection] + \end{frame} + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{What is Silicon Chips RE?} + \begin{tabular}{cl} + + \begin{tabular}{c} + \includegraphics[width=5.2cm]{res/chip_example.png} + \end{tabular} + + & \begin{tabular}{l} + \parbox{0.5\linewidth}{\scriptsize + Same idea than with software RE (from binary, to assembly and to code), silicon chip RE go \textbf{from silicon}, \textbf{to images}, \textbf{to transistors}, \textbf{to gates}, \textbf{to netlist} and \textbf{to algorithm}. \\ + + With proper preparation and knowledge, we can go into silicon, \textbf{analyze transistors}, \textbf{retrieve gates/wires/vias} and \textbf{reconstruct implemented algorithms}. This can be used to \textbf{analyze old hardware}, build \textbf{software emulators}, search for \textbf{vulnerabilities} and \textbf{backdoors}, \textbf{break/test a protection}, \textbf{secret extraction} or \textbf{check intellectual property}. \\ + + \textbf{Used in IC industry} for \textbf{fault/failure detection} \& analysis, but \textbf{not at the same scale}. + } + \end{tabular} + + \end{tabular} + + \begin{figure}[!ht] + \centering + \resizebox{0.7\textwidth}{!}{% + \begin{tikzpicture} + \tikzstyle{every node}=[font=\normalsize] + \draw (10.5,17.75) circle (2.5cm) node [text width=4cm] + { \Large + \centering \textbf{Image chip} \\ + \vspace{3mm} + \textit{(or SEM scan or 3D tomography)} + } ; + \draw (16.5,17.75) circle (2.5cm) node {\Large \textbf{Analyze Gates}} ; + \draw (22.5,17.75) circle (2.5cm) node {\Large \textbf{Trace Wires/Vias}} ; + \draw (28.5,17.75) circle (2.5cm) node {\Large \textbf{Generate Netlist}} ; + \draw [, dashed] (34.5,17.75) circle (2.5cm) node {\Large \textbf{Retrieve Algorithm}} ; + \draw [->] (13,17.75) -- (14,17.75); + \draw [->] (19,17.75) -- (20,17.75); + \draw [->] (25,17.75) -- (26,17.75); + \draw [->] (31,17.75) -- (32,17.75); + \end{tikzpicture} + }% + \end{figure} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{How to Access Silicon?} + Can be very costly (plasma \& laser) and destructive... But also accessible with simpler methods (like chemical/mechanical). More on \cite{SiliconPron}. + + \begin{enumerate} + \item \textbf{Decapsulation} (heat, acid, mechanical, plasma, laser...) + \item \textbf{Delayering} (chemical, abrasive, laser, plasma...) + \item \textbf{Cleaning} (ultrasound, acid...) + \end{enumerate} + + \begin{center} + \includegraphics[width=4cm]{res/decap.jpg} + \cite{Holler2017} + \includegraphics[width=3cm]{res/delayer.png} + \cite{KarstenNohl2009} + \includegraphics[width=4.5cm]{res/delayered.png} + \tiny MIT + \end{center} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{How to Retrieve Images?} + Using each layer (invasive) or directly using the chip (non-invasive): + \begin{itemize} + \item Take very-high resolution images from \textbf{optical microscope} (basic, confocal) ; + \item Scan from an \textbf{electron microscope} (SEM, TEM...) ; + \item Generate a 3D model using \textbf{electron tomography} ; + \end{itemize} + + \begin{center} + \includegraphics[width=5cm]{res/3d_1.png} + \includegraphics[width=5.4cm]{res/3d_2.png} + \cite{Holler2017} + \end{center} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{How to Perform the Analysis?} + + \begin{tabular}{cl} + + \begin{tabular}{c} + \parbox{0.5\linewidth}{ + \vspace{-3mm} + Overview: + \begin{enumerate} + \item Choose a \textbf{zone of interest}, + \item Identify each \textbf{gate type}, annotate, and place in a \textbf{"gate library"}, + \item Find other \textbf{gates instance} from gate library, + \item Link gates by tracing \textbf{wires and vias}, + \item Export to \textbf{netlist} (e.g. by translating each gate to VHDL/Verilog code). + \end{enumerate} + } + \end{tabular} + + & \begin{tabular}{l} + \includegraphics[width=6.25cm]{res/transistor.png} + \end{tabular} + + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{How to identify a transistor?} + + \begin{tabular}{cl} + + \begin{tabular}{c} + \parbox{0.5\linewidth}{\small + \begin{enumerate} + \item Search, at transistor layer, for \textbf{doped zones}. + \item Spot the \textbf{zebras}. + \item Use logic to identify the \textbf{type of each transistor} (e.g. PMOS are bigger to compensate with lower hole mobility). + \item Search for \textbf{wires} (to identify inputs and outputs). + \end{enumerate} + } + \end{tabular} + + & \begin{tabular}{l} + \includegraphics[width=4cm]{res/npn.png} + \vspace{10mm} + \tiny (NMOS, \textit{Wikipedia}) + \end{tabular} + + \end{tabular} + + \centering + \hspace{-40mm} + \includegraphics[width=2.5cm]{res/cmos.png} + \tiny (Inverter, \textit{Wikipedia}) + \hspace{6mm} + \includegraphics[width=3cm]{res/dopant_pmos.png} + \tiny (PMOS \cite{YenerBulent2014}) + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{How to Identify a Gate?} + + \begin{tabular}{ccc} + \begin{tabular}{c} + + \begin{tabular}{ccc} + \includegraphics[width=1.75cm]{res/ana_1.png} & + \includegraphics[width=1.75cm]{res/ana_2.png} & + \includegraphics[width=1.75cm]{res/ana_3.png} \\ + \tiny Transistor layer & + \tiny Logic layer & + \tiny Metal layer \\ + \end{tabular} \\ + + $\Downarrow$ \\ + + \begin{tabular}{cc} + \tiny + \includegraphics[width=1.75cm]{res/post_ana_1.png} & + \includegraphics[width=1.75cm]{res/post_ana_2.png} \\ + \tiny P \& N zones and 2 inputs & + \tiny V+ \& V-, and output \\ + \end{tabular} + + \end{tabular} & + + $\Rightarrow$ + + & + + \ensuremath{\vcenter{\hbox{\includegraphics[width=3cm]{res/ana_layout.png}}}} + {\tiny\cite{SiliconZoo}} + $\Rightarrow$ + \begin{tabular}{c} + \textbf{NAND gate!} \\ + \includegraphics[width=2.5cm]{res/nand.png} \\ + \begin{tabular}{ | c | c || c | } + \hline + A & B & Y \\ + \hline + 0 & 0 & 1 \\ + 1 & 0 & 1 \\ + 0 & 1 & 1 \\ + 1 & 1 & 0 \\ + \hline + \end{tabular} + \end{tabular} \\ + + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{How to Retrieve the Netlist from Analyzed Gates?} + \begin{tabular}{cl} + + \begin{tabular}{c} + \includegraphics[width=6cm]{res/verilog.png} + \end{tabular} + + & \begin{tabular}{l} + \parbox{0.5\linewidth}{\scriptsize + \begin{itemize} + \item Each gate can be described with \textbf{hardware description language (HDL)}, like \textbf{Verilog} or \textbf{VHDL}. + \item \textbf{Wires \& vias} can also be described. + \item That's all we need to \textbf{obtain the netlist}! + \end{itemize} + + We can, from HDL, \textbf{simulate the extracted netlist} and \textbf{find incoherence} (\textit{example with gtkwave below}): + + \vspace{2mm} + + \includegraphics[width=7cm]{res/gtkwave.png} + } + \end{tabular} + + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{How to Get the Algorithm/Specification from Netlist? \cite{LeonidAzriel2021}} + \small + + After retrieving the \textbf{netlist}, we are left with a \textbf{huge and "unorganized" number of gates}. The \textbf{specification discovery} phase aims to \textbf{retrieve IC's algorithm/functionality} from the extracted netlist. + + \vspace{3mm} + + Using specific algorithms you can \textbf{automate some phase}: + \begin{itemize} + \item \textbf{Partitioning} of the netlist (\textit{to retrieve a semblance of "code" structure}). + \item \textbf{Recovery} of the registers (\textit{if applicable}). + \item \textbf{Identification} of the extracted "groups" (\textit{partitions}) of the netlist. + \item \textbf{Construction} of a library of netlist components from the identified "groups". + \end{itemize} + + \vspace{3mm} + + These algorithms \textbf{need to allow some degrees of error} from the netlist extraction. This phase is $\sim$analogous with \textbf{duplicated, standard \& library functions identification} for \textbf{software engineering}. A nice open source tool for this is \textbf{HAL}\footnote{https://github.com/emsec/hal} (compatible with Degate's outputs!). + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{To Summarize} + + \begin{figure}[!ht] + \centering + \resizebox{0.8\textwidth}{!}{% + \begin{tikzpicture} + \tikzstyle{every node}=[font=\normalsize] + \draw (10.5,17.75) circle (2.5cm) node [text width=4cm] + { \Large + \centering \textbf{Image chip} \\ + \vspace{3mm} + \textit{(or SEM or 3D tomography)} + } ; + \draw (16.5,17.75) circle (2.5cm) node {\Large \textbf{Analyze Gates}} ; + \draw (22.5,17.75) circle (2.5cm) node {\Large \textbf{Trace Wires/Vias}} ; + \draw (28.5,17.75) circle (2.5cm) node {\Large \textbf{Generate Netlist}} ; + \draw [, dashed] (34.5,17.75) circle (2.5cm) node {\Large \textbf{Retrieve Algorithm}} ; + \draw [->] (13,17.75) -- (14,17.75); + \draw [->] (19,17.75) -- (20,17.75); + \draw [->] (25,17.75) -- (26,17.75); + \draw [->] (31,17.75) -- (32,17.75); + + \draw [, dashed] (8.25,15) rectangle node [text width=4cm] + { + - \textbf{Decapsulate}, \\ + - Select \textbf{area of interest}, \\ + - \textbf{Delayer}, \\ + - Clean, \\ + - Stitch. + } (12.75,10.25); + + \draw [, dashed] (14.25,15) rectangle node [text width=4cm] + { + - Analyze transistors, \\ + - \textbf{Identify each type of gates}, \\ + - Retrieve all instances of each gate (\textbf{pattern matching}). + } (18.75,10.25); + + \draw [, dashed] (20.25,15) rectangle node [text width=4cm] + { + - Identify \textbf{wires}, \\ + - Identify \textbf{vias}, \\ + - \textbf{Connect gates}. + } (24.75,10.25); + + \draw [, dashed] (26.25,15) rectangle node [text width=4cm] + { + - \textbf{Export netlist}, \\ + - Gate simulation, \\ + - Try to identify errors. + } (30.75,10.25); + + \draw [, dashed] (32.25,15) rectangle node [text width=4cm] + { + - Extract algorithm, \\ + - \textbf{Discover specification}, \\ + - Perform functional analysis\cite{LeonidAzriel2021}, \\ + - Build a \textbf{software emulator}, \\ + - Try to \textbf{identify errors}. + } (36.75,10.25); + + \draw [] (10.5,15.25) -- (10.5,15); + \draw [] (16.5,15.25) -- (16.5,15); + \draw [] (22.5,15.25) -- (22.5,15); + \draw [] (28.5,15.25) -- (28.5,15); + \draw [] (34.5,15.25) -- (34.5,15); + + + \node (tikzmaker) [shift={(2.75, -0)}] at (7.5,7.25) {\includegraphics[width=5cm]{res/how_1.png}\cite{KarstenNohl2009}}; + \node (tikzmaker) [shift={(2.75, -0)}] at (13.5,7.25) {\includegraphics[width=5cm]{res/how_2.png}\cite{KarstenNohl2009}}; + \node (tikzmaker) [shift={(2.75, -0)}] at (19.5,6.5) {\includegraphics[width=5cm]{res/how_3.png}\cite{KarstenNohl2009}}; + \node (tikzmaker) [shift={(2.75, -0)}] at (25.5,7.25) {\includegraphics[width=5cm]{res/how_4.png}\cite{KarstenNohl2009}}; + \node (tikzmaker) [shift={(2.75, -0)}] at (31.75,7.25) {\includegraphics[width=5cm]{res/how_5.png}\cite{KarstenNohl2009}}; + + \draw [, dashed] (10.25,10.25) -- (10.25,9.75); + \draw [, dashed] (16.25,10.25) -- (16.25,9.75); + \draw [, dashed] (22.25,10.25) -- (22.25,9.75); + \draw [, dashed] (28.5,10.25) -- (28.5,9.75); + \draw [, dashed] (34.5,10.25) -- (34.5,9.75); + \end{tikzpicture} + }% + \end{figure} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + \subsection{Challenges} + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + \begin{frame}{} + \tableofcontents[currentsubsection] + \end{frame} + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Cost Perspective (1/2)} + \textbf{Costly solutions will give best results}, and sometime reduce the difficulty for analysis software: + \begin{itemize} + \item \textbf{Decapsulation/delayering:} plasma, laser, FIB ; + \item \textbf{Imaging:} Scanning Electron Microscope (SEM), other electron microscope (TEM, STEM, LEEM, PEEM...) ; + \item \textbf{3D modelization:} electron tomography (3D) ; + \end{itemize} + + \vspace{3mm} + + Simpler methods rely on \textbf{mechanical \& chemical} decapsulation/delayering and \textbf{optical microscopes} to obtain \textbf{very-high resolution but imperfect images}. Using images is more challenging: \textbf{color channels}, \textbf{impurity/damage/dust}, \textbf{single dimension}, \textbf{stitching}, \textbf{resolution}, \textbf{laborious work}... + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Cost Perspective (2/2)} + \textbf{Chip samples cost} are also to consider (when doing invasive analysis, you'll maybe need multiple samples of the chip). + + \vspace{3mm} + + Compared to software reverse engineering, there is a \textbf{lot more costs associated}, and a \textbf{higher entry barrier}. + + \vspace{3mm} + + \begin{tabular}{cl} + + \begin{tabular}{c} + \includegraphics[width=7.5cm]{res/sem.png} + \end{tabular} + + & \begin{tabular}{l} + \parbox{0.4\linewidth}{\small + A \textbf{new SEM microscope} can cost from \textbf{70k\$ to over 1M\$}. \textbf{Used instruments} can cost from \textbf{2,5k\$ to 550k\$}. Resolution may vary a lot. \\ + + And that's \textbf{just for imaging}! + + \vspace{12mm} + + \textit{(Umeå University)} + } + \end{tabular} + + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Analysis Perspective} + \begin{itemize} + \item Newest chips \textbf{have $\sim$3nm transistors} and \textbf{billions of them}! + \item Need automatic \textbf{gate recognition, wire tracing and netlist reconstruction}, which a human can't handle alone. + \item Resulting images can be \textbf{millions of pixels large} ($width$ $>$ million pixels)! + \item How to perform \textbf{template matching/image recognition} on such \textbf{gigantic images}? + \item How to handle \textbf{all possible formats} (images, multi-layered images, SEM images, 3D tomography...)? + \item There are so \textbf{many steps where that can go wrong}, or a \textbf{small error slips} into the analysis... + \item Non-planerized IC exists (non repeated standard cells)! + \item And what about \textbf{obfuscation}? + \end{itemize} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Human Perspective} + \begin{itemize} + \item Need a \textbf{highly technical level} in several disciplines, this will help for \textbf{error spotting}, choosing a \textbf{zone of interest} and more. + \item Need to \textbf{understand "silicon"} (how IC are made) and have \textbf{low-level electronic knowledge}. + \item Have the necessary \\ \textbf{equipment available}. + \item Be \textbf{persistent} and \textbf{patient}. + \item \textbf{Practice}. + \item And \textbf{Have time!} + \end{itemize} + + \vspace{-30mm} + \hfill\parbox{.65\textwidth}{ + \includegraphics[width=9cm]{res/dect.png} + } + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Importance for Cybersecurity} + + How can we \textbf{trust software} if we \textbf{can't trust hardware} (e.g. "specialized" ASIC)? + + \vspace{3mm} + + \begin{itemize} + \item Is there any \textbf{vulnerability in the hardware implementation} of an algorithm (e.g. crypto standard with predictable initialization, bad randomness...)? + \item Is there any \textbf{hardware Trojan} (e.g. placed by the foundry)? + \item If there is a vulnerability/backdoor, \textbf{patching is impossible}, far \textbf{more impactful} than software vulnerabilities. + \end{itemize} + + \vspace{3mm} + + Some examples of vulnerabilities found thanks to silicon RE: + \begin{itemize} + \item \textit{Legic Prime}, \textit{NXP Hitag2}, \textit{DECT DSC}, \textit{CryptoRF}, \textit{Atmel CryptoMemory} \& \textit{NXP Mifare Crypto-1} ($\sim$2008, Nohl et al): \textbf{weak (or potentially weak) cryptographic ciphers}. + \item Undisclosed ones? + \end{itemize} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Available Tools \& Products} + + \begin{tabular}{cl} + + \begin{tabular}{c} + \parbox{0.4\linewidth}{\small + Commercial products: + \begin{itemize} + \item \href{https://www.texplained.com/about-us/chipjuice-software/}{\textbf{CHIPJUICE}}: + Extracting Data from Highly Encrypted ICs. + \item \textit{Internal tools}: for sure, there is a lot of them. + \end{itemize} + + \vspace{3mm} + + Open Source tools: + \begin{itemize} + \item \href{https://www.degate.org/}{\textbf{Degate}} + \item \href{https://github.com/emu-russia/psxrev}{\textbf{psxrev}}: SONY PlayStation PCB/chips reverse engineering. + \item \href{https://github.com/emu-russia/Deroute}{\textbf{Deroute}}: Tool for untangling wires. + \item \href{https://github.com/galibert/dietools}{\textbf{dietools}}: Series of tools for die shot reverse-engineering. % from vectorization to netlist + \end{itemize} + } + \end{tabular} + + & \begin{tabular}{c} + \includegraphics[width=7cm]{res/chipjuice.jpg} \\ + \textit{\small(Texplained)} + \end{tabular} + + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\section{Degate} + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Introduction} + \textbf{Degate} is a multi-platform software for semi-automatic \textbf{Very-Large-Scale Integration (VLSI) chips reverse engineering} of digital logic in chips. + + \vspace{3mm} + + \begin{tabular}{cl} + + \begin{tabular}{c} + \parbox{0.4\linewidth}{\small + \begin{itemize} + \item $\sim$70k LoC + \item Supports Mac, Linux \& Windows, + \item Qt based, + \item Multi-language support, + \item Gate definition, + \item Gate template, via \& wire matching, + \item Rule checks, + \item ... + \end{itemize} + } + \end{tabular} + + & \begin{tabular}{l} + \includegraphics[width=7cm]{res/degate1.png} + \end{tabular} + + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{History} + A long story, with \textbf{technical debt} and \textbf{major IC evolution} (in transistor count), along with a \textbf{small community}. + + \vspace{-10mm} + + \begin{center} + \begin{tikzpicture}[very thick, black, rotLabel/.style={above=3pt, anchor= south west, rotate=45}] + \small + + % draw a horizontal line + \draw (1,0) -- (14,0); + + % draw vertical lines + \foreach \x in {1,2,4,9,10,11,12,14} + \draw (\x cm,3pt) -- (\x cm,-3pt); + + % draw nodes to add events + \draw (1,0) node[below=3pt] {2007} node[rotLabel] {Martin Schobert \textbf{start developing Degate}}; + \draw (2,0) node[below=3pt] {2008} node[rotLabel] {Famous \textbf{hardware ciphers analysis} w/ Degate}; + \draw (4,0) node[below=3pt] {2010} node[rotLabel] {End of Martin Schobert thesis}; + + \draw (6.5,0) node[above=0pt] {\footnotesize \textit{(Minimum maintenance)}}; + + \draw (9,0) node[below=3pt] {2018} node[rotLabel] {\textbf{Forked}, major rewrite}; + \draw (10,0) node[below=3pt] {2019} node[rotLabel] {Vulgarization \textbf{papers}, start working with a lab...}; + \draw (11,0) node[below=3pt] {2020} node[rotLabel] {Pandemic}; + \draw (12,0) node[below=3pt] {2021} node[rotLabel] {Degate \textbf{2.0}}; + \draw (14,0) node[below=3pt] {2023} node[rotLabel] {Degate \textbf{2.1 beta}}; + \end{tikzpicture} + \end{center} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Usage} + + Degate help to reverse \textbf{VLSI chips} by creating an analyzed \textbf{gate library}, doing \textbf{template matching} to find gates instances from this library, \textbf{matching wires \& vias}, \textbf{exporting netlist} and \textbf{navigating really huge images}. \\ + + \vspace{3mm} + + Focus on \textbf{modern ICs} with \textbf{standard cells}, and supports \textbf{any 2D capture/imaging method} (SEM, optical...). + + \begin{figure}[!ht] + \centering + \resizebox{0.7\textwidth}{!}{% + \begin{tikzpicture} + \tikzstyle{every node}=[font=\normalsize] + + \draw [, line width=2pt, rounded corners = 93.8] (16.75,21) rectangle (31.5,14.75); % 16.75 -> 14.5 + \node [font=\LARGE] at (24.25,21.5) {\textbf{\underline{Degate 2.0}}}; % 24.25 -> 22.5 + + \draw [dashed, line width=2pt, rounded corners = 140] (13.5,23) rectangle (34.325,12.75); % 16.75 -> 14.5 + \node [font=\LARGE] at (24.25,13.5) {\textit{\underline{Degate 3.0}}}; % 24.25 -> 22.5 + + \draw (10.5,17.75) circle (2.5cm) node [text width=4cm] + { \Large + \centering \textbf{Image chip} \\ + \vspace{3mm} + \textit{(or SEM scan or 3D tomography)} + } ; + \draw (16.5,17.75) circle (2.5cm) node {\Large \textbf{Analyze Gates}} ; + \draw (22.5,17.75) circle (2.5cm) node {\Large \textbf{Trace Wires/Vias}} ; + \draw (28.5,17.75) circle (2.5cm) node {\Large \textbf{Generate Netlist}} ; + \draw [, dashed] (34.5,17.75) circle (2.5cm) node {\Large \textbf{Retrieve Algorithm}} ; + \draw [->] (13,17.75) -- (14,17.75); + \draw [->] (19,17.75) -- (20,17.75); + \draw [->] (25,17.75) -- (26,17.75); + \draw [->] (31,17.75) -- (32,17.75); + \end{tikzpicture} + }% + \end{figure} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Small Demonstration} + + \begin{tabular}{cl} + + \begin{tabular}{l} + \hspace{-8mm} + \includegraphics[width=0.8\textwidth]{res/degate_overview.png} + \end{tabular} + + & + + \begin{tabular}{l} + \hspace{-8mm} + \parbox{0.225\textwidth}{\footnotesize + Overview of the chip, for zone of interest selection. \\ + + A sub-project can then be created on the zone of interest, and specific layers can be added (independent from the rest). + } + \end{tabular} + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Small Demonstration} + + \begin{tabular}{cl} + + \begin{tabular}{l} + \hspace{-8mm} + \includegraphics[width=0.8\textwidth]{res/degate_layers.png} + \end{tabular} + + & + + \begin{tabular}{l} + \hspace{-8mm} + \parbox{0.225\textwidth}{\footnotesize + Each sub-project can contains multiple layers (pre-aligned images). \\ + + Two project mode: 1. For smaller images, will convert each images in Degate's format (for fast access) and 2. New (WIP, beta) mode for huge images (load only partial tiles in RAM, and doesn't change/import initial file). + } + \end{tabular} + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Small Demonstration} + + \begin{tabular}{cl} + + \begin{tabular}{l} + \hspace{-8mm} + \includegraphics[width=0.8\textwidth]{res/degate_gate.png} + \end{tabular} + + & + + \begin{tabular}{l} + \hspace{-8mm} + \parbox{0.225\textwidth}{\footnotesize + Each gate can be described with VHDL/Verilog, have a list of port (placed on image), a type associated etc. + } + \end{tabular} + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Small Demonstration} + + \begin{tabular}{cl} + + \begin{tabular}{l} + \hspace{-8mm} + \includegraphics[width=0.8\textwidth]{res/degate_instance.png} + \end{tabular} + + & + + \begin{tabular}{l} + \hspace{-8mm} + \parbox{0.225\textwidth}{\footnotesize + Each identified gate (from the gate library) can be matched manually or using template matching algorithms. + } + \end{tabular} + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Small Demonstration} + + \begin{tabular}{cl} + + \begin{tabular}{l} + \hspace{-8mm} + \includegraphics[width=0.8\textwidth]{res/degate_matching.png} + \end{tabular} + + & + + \begin{tabular}{l} + \hspace{-8mm} + \parbox{0.225\textwidth}{\footnotesize + Template matching (will soon be ported to OpenCV) will use gate library to automate gate identification. \\ + + Currently it uses normalized cross-correlation (with some more steps). + } + \end{tabular} + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Small Demonstration} + + \begin{tabular}{cl} + + \begin{tabular}{l} + \hspace{-8mm} + \includegraphics[width=0.8\textwidth]{res/degate_wires.png} + \end{tabular} + + & + + \begin{tabular}{l} + \hspace{-8mm} + \parbox{0.225\textwidth}{\footnotesize + Wire matching, and specifically port interconnection, is the real challenge (and very error prone). \\ + + Currently it uses zero crossing edge detection. + } + \end{tabular} + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Small Demonstration} + + \begin{tabular}{cl} + + \begin{tabular}{l} + \hspace{-8mm} + \includegraphics[width=0.8\textwidth]{res/degate_rule.png} + \end{tabular} + + & + + \begin{tabular}{l} + \hspace{-8mm} + \parbox{0.225\textwidth}{\footnotesize + Helpers are available, like rudimentary (but to be improved) rule checking (e.g. for coherency). + } + \end{tabular} + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Small Demonstration} + + \begin{tabular}{cl} + + \begin{tabular}{l} + \hspace{-8mm} + \includegraphics[width=0.8\textwidth]{res/degate_modules.png} + \end{tabular} + + & + + \begin{tabular}{l} + \hspace{-8mm} + \parbox{0.225\textwidth}{\footnotesize + Everything can be organized in "module", exported individually (in Verilog/VHDL), etc... "Divide et impera". + } + \end{tabular} + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Engineering Challenges} + \begin{tabular}{cl} + + \begin{tabular}{l} + \parbox{0.6\textwidth}{ + \begin{itemize} + \item Gate template, wires \& vias \textbf{matching}. + \item Very \textbf{huge images} handling. + \item \textbf{Error} recovery/acceptance/identification. + \item Multiple possible \textbf{image format} (e.g. .tiff, .png...) \& \textbf{image source} (e.g. SEM, confocal...). + \item 10+ years \textbf{old software} (mix of old \& new C++). + \item \textbf{Collaborative} analysis. + \item Integrated \textbf{gate analyzer}. + \item Explicit full \textbf{netlist exporter}. + \end{itemize} + } + + \end{tabular} + + & + + \vspace{8mm} + \begin{tabular}{cc} + \includegraphics[width=1.55cm]{res/nand_mifare_transistor.png} & + \includegraphics[width=1.45cm]{res/nand_legic_transistor.png} \\ + \includegraphics[width=1.48cm]{res/nand_mifare_logic.png} & + \includegraphics[width=1.45cm]{res/nand_legic_logic.png} \\ + \tiny MIFARE NAND\cite{KarstenNohl2009} & + \tiny LEGIC NAND\cite{KarstenNohl2009} \\ + \end{tabular} + \end{tabular} + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + + + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + \begin{frame}{Research Challenges} + + \begin{itemize} + \item \textbf{3D capture}, imply rethinking Degate (New 3D mode? New software? Really accessible?), and \textbf{new algorithms} (e.g. for matching, tracing and gate identification). + \item \textbf{Machine learning}/better algorithms for: + \begin{itemize} + \item Auto-\textbf{vectorization} ; + \item Gate auto \textbf{identification} (from vectorized analysis) ; + \item Gate auto \textbf{wiring} ; + \item Auto vias \& wires \textbf{identification}. + \end{itemize} + \item Take advantage of certain capture methods such as \textbf{SEM} which makes \textbf{automation easier}. + \item Making the \textbf{field more accessible} (more automation, new abstractions for analysis, communication...). + \item Use Degate for \textbf{advanced analysis} and \textbf{published results}. + \end{itemize} + + \end{frame} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\section{MIFARE Classic Chip Reverse Engineering Case} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\begin{frame}{MIFARE Classic Chip \cite{KarstenNohl2009}} + + \begin{tabular}{cc} + + \begin{tabular}{c} + \parbox{0.5\textwidth}{\small + \vspace{-6mm} + + \begin{itemize} + \item \textbf{RFID card} from NXP launched in 1994. + \item Used the \textbf{Crypto1 cypher} (until MIFARE Classic EV1, that are using \textbf{Hitag2} cipher). + \item \textbf{Proprietary encryption} algorithm (stream cipher), security by obscurity. + \item Cryto1 cipher is only \textbf{implemented in hardware}. + \item Used (back in 2008) in more than \textbf{3.5 billions cards} (including many building access control systems). + \end{itemize} + + \vspace{3mm} + + A \textbf{huge target} with a \textbf{suspicious cypher} and \textbf{security standards}? + } + \end{tabular} + + & + + \begin{tabular}{c} + \includegraphics[width=0.4\textwidth]{res/mifare.png} + \end{tabular} + \end{tabular} +\end{frame} +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\begin{frame}{Degate's origins \cite{NohlEvans2008}} + + \begin{tabular}{cc} + + \begin{tabular}{c} + \hspace{-7mm} + \includegraphics[width=0.4\textwidth]{res/mifare_reverse2.png} + \end{tabular} + + & + + \begin{tabular}{c} + + \hspace{-10mm} + \parbox{0.6\textwidth}{\footnotesize + \begin{itemize} + \item K. Nohl \& Starbug \textbf{reverse-engineered the Crypto1 cypher} from MIFARE Classic chip in 2007. + \item Used \textbf{acetone} to dissolve the RFID cards. + \item Used \textbf{manual polishing} for delayering. + \item Image a total of \textbf{6 layers}. + \item Identify zone of interest, \textbf{searching for 48-bit register} \& group of XOR gates. + \item Used \textbf{standard optical microscope} (500x) \& hugin tool for stitching. + \item Identified \textbf{around 70 types of gates}. + \item Used \textbf{home-made scripts} (which became the base of Degate) for \textbf{template matching} to identify all gates. + \item \textbf{Manually} reconstructed \textbf{connections} between gates. + \item Made a \textbf{script} to help detecting \textbf{wires} \& \textbf{vias}. + \end{itemize} + } + \end{tabular} + \end{tabular} +\end{frame} +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\begin{frame}{Consequences \cite{NohlEvans2008}} + \begin{tabular}{cc} + \hspace{-10mm} + \parbox{0.6\textwidth}{\footnotesize + \begin{itemize} + \item Using the reverse-engineering results and protocol analysis, authors found \textbf{multiple weakness} in the cipher: + \begin{itemize} + \item The cipher is vulnerable to \textbf{brute force} attack, key is too small. + \item RNG is predictable, it uses a 16-bit LFSR (linear feedback shift register) \textbf{initialized with constant value} and reset at each power-up. + \item There is \textbf{only one secret key} for each ID that can result to a specific session key, and all shifts are linear. + \end{itemize} + \item Meaning that just by \textbf{sniffing interactions} with the card and the reader, we can compute the key and \textbf{retrieve all the data} of the card. + \item NXP release a retro-compatible \& "hardened" version of the Cipher (Hitag2), which was also weak, MIFARE Classic were \textbf{"discontinued" in 2015}. + \end{itemize} + } + + & + + \begin{tabular}{c} + \begin{tabular}{c} + \hspace{-7mm} + \includegraphics[width=0.4\textwidth]{res/crypto1.png} + \end{tabular} \\ + \hspace{-10mm} + \parbox{0.35\textwidth}{\footnotesize + \begin{itemize} + \item Authors \textbf{analyzed other RFID devices} after. + \item \textbf{Degate was created} from this analysis, used for other RFID devices reverse-engineering and open-sourced in 2008. + \end{itemize} + } + \end{tabular} + \end{tabular} +\end{frame} +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\section{Future of Silicon Chip Reverse Engineering} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\begin{frame}{Future of Silicon Chip RE} + \begin{itemize} + \item \textbf{Simpler} and \textbf{cheaper} IC capture (decap \& delayer). + \item Making the \textbf{field more accessible} (communication, more real-life and useful example/reference analysis...). + \item \textbf{Shared and open} library of \textbf{chips captures} ($\sim$zeptobar \& siliconpr0n + SiliconZoo). + \item \textbf{Machine learning} to automate even more analysis steps (\textit{gate identification, wire extract, algorithm retrieving \& analysis})? + \end{itemize} + + \vspace{3mm} + + There is \textbf{2 EU projects} running around \textbf{ICs reverse-engineering}, but no information on tools, process and analysis \underline{\textbf{sharing}}. + + \begin{center} + \begin{tabular}{cccc} + + \hspace{-13mm} + + \begin{tabular}{c} + \includegraphics[width=0.27\textwidth]{res/google_scholar.png} + \end{tabular} + + & + + \begin{tabular}{c} + \includegraphics[width=0.25\textwidth]{res/old_google_scholar.png} + \end{tabular} + + & + + \hspace{10mm} + + \begin{tabular}{c} + \includegraphics[width=0.1\textwidth]{res/ForRES.png} + \end{tabular} + + & + + \begin{tabular}{c} + \includegraphics[width=0.1\textwidth]{res/ORSHIN.png} + \end{tabular} + + \end{tabular} + \end{center} +\end{frame} +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\section{Bonus} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\begin{frame}{Which gate is this?} + % This is a nand, inversed on y axis + + \begin{center} + \begin{tabular}{ccc} + \includegraphics[width=2.6cm]{res/nand2_transistor_a.png} & + \includegraphics[width=2.6cm]{res/nand2_logic_a.png} & + \includegraphics[width=2.6cm]{res/nand2_metal_a.png} \\ + \tiny Transistor layer & + \tiny Logic layer & + \tiny Metal layer \\ + \end{tabular} + \end{center} +\end{frame} +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\section{References} + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\begin{frame}[allowframebreaks]{References} + \bibliographystyle{plain} + \bibliography{bibli} + \nocite{*} +\end{frame} +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\end{document} diff --git a/Degate-2024/sources/bibli.bib b/Degate-2024/sources/bibli.bib new file mode 100644 index 0000000..9783ed8 --- /dev/null +++ b/Degate-2024/sources/bibli.bib @@ -0,0 +1,75 @@ +@Article{Holler2017, + author = {Holler, Mirko and Guizar-Sicairos, Manuel and Tsai, Esther H. R. and Dinapoli, Roberto and Müller, Elisabeth and Bunk, Oliver and Raabe, Jörg and Aeppli, Gabriel}, + journal = {Nature}, + title = {High-resolution non-destructive three-dimensional imaging of integrated circuits}, + year = {2017}, + issn = {1476-4687}, + month = mar, + number = {7645}, + pages = {402--406}, + volume = {543}, + doi = {10.1038/nature21698}, + publisher = {Springer Science and Business Media LLC}, +} + +@Misc{SiliconZoo, + author = {Security Research Labs, Berlin}, + title = {SiliconZoo, \url{http://siliconzoo.org}}, + url = {http://siliconzoo.org}, +} + +@Misc{SiliconPron, + author = {John McMaster}, + title = {SiliconPr0n, \url{https://siliconpr0n.org/}}, + url = {https://siliconpr0n.org/}, +} + +@Misc{KenShirriff, + author = {Ken Shirriff}, + title = {Ken Shirriff's blog, \url{https://www.righto.com/}}, + url = {https://www.righto.com/}, +} + +@Conference{KarstenNohl2009, + author = {Karsten Nohl, Starbug}, + title = {Pacsec Silicon Conference}, + year = {2009}, +} + +@Misc{YenerBulent2014, + author = {Yener Bulent, Zonenberg Andrew}, + title = {CSCI 4974/6974 Hardware Reverse Engineering}, + year = {2014}, +} + +@Misc{LeonidAzriel2021, + author = {Leonid Azriel, Julian Speith, Nils Albartus, Ran Ginosara, Avi Mendelson, and Christof Paar}, + howpublished = {Cryptology ePrint Archive, Paper 2021/1278}, + title = {Azriel and Julian Speith and Nils Albartus and Ran Ginosara and Avi Mendelson and Christof Paar}, + year = {2021}, +} + +@article{NohlEvans2008, + title = {Reverse-{Engineering} a {Cryptographic} {RFID} {Tag}}, + abstract = {The security of embedded devices often relies on the secrecy of proprietary cryptographic algorithms. These algorithms and their weaknesses are frequently disclosed through reverse-engineering software, but it is commonly thought to be too expensive to reconstruct designs from a hardware implementation alone. This paper challenges that belief by presenting an approach to reverse-engineering a cipher from a silicon implementation. Using this mostly automated approach, we reveal a cipher from an RFID tag that is not known to have a software or micro-code implementation. We reconstruct the cipher from the widely used Mifare Classic RFID tag by using a combination of image analysis of circuits and protocol analysis. Our analysis reveals that the security of the tag is even below the level that its 48-bit key length suggests due to a number of design flaws. Weak random numbers and a weakness in the authentication protocol allow for pre-computed rainbow tables to be used to find any key in a matter of seconds. Our approach of deducing functionality from circuit images is mostly automated, hence it is also feasible for large chips. The assumption that algorithms can be kept secret should therefore to be avoided for any type of silicon chip.}, + language = {en}, + author = {Nohl, Karsten and Evans, David and Plotz, Henryk}, + keywords = {ANALYSE, MIFARE, CRYPTANALYSE, RFID}, + pages = {9}, + file = {Nohl et al. - Reverse-Engineering a Cryptographic RFID Tag.pdf:/home/db/Zotero/storage/JDG9FW4I/Nohl et al. - Reverse-Engineering a Cryptographic RFID Tag.pdf:application/pdf}, +} + +@article{schobertgnu, + title={GNU software degate}, + author={Schobert, Martin}, + journal={Webpage: \url{http://www.degate.org}} +} + +@Misc{Zeptobars, + author = {Mikhail Svarichevsky}, + title = {Zeptobars, \url{https://zeptobars.com/en/}}, + url = {https://zeptobars.com/en/}, +} + + +@Comment{jabref-meta: databaseType:bibtex;} diff --git a/Degate-2024/sources/res/3d_1.png b/Degate-2024/sources/res/3d_1.png new file mode 100644 index 0000000..dbb5a7f Binary files /dev/null and b/Degate-2024/sources/res/3d_1.png differ diff --git a/Degate-2024/sources/res/3d_2.png b/Degate-2024/sources/res/3d_2.png new file mode 100644 index 0000000..cf526a8 Binary files /dev/null and b/Degate-2024/sources/res/3d_2.png differ diff --git a/Degate-2024/sources/res/ForRES.png b/Degate-2024/sources/res/ForRES.png new file mode 100644 index 0000000..6437575 Binary files /dev/null and b/Degate-2024/sources/res/ForRES.png differ diff --git a/Degate-2024/sources/res/NAND.xcf b/Degate-2024/sources/res/NAND.xcf new file mode 100644 index 0000000..70d3814 Binary files /dev/null and b/Degate-2024/sources/res/NAND.xcf differ diff --git a/Degate-2024/sources/res/ORSHIN.png b/Degate-2024/sources/res/ORSHIN.png new file mode 100644 index 0000000..efaf1ac Binary files /dev/null and b/Degate-2024/sources/res/ORSHIN.png differ diff --git a/Degate-2024/sources/res/ana_1.png b/Degate-2024/sources/res/ana_1.png new file mode 100644 index 0000000..a5d9af1 Binary files /dev/null and b/Degate-2024/sources/res/ana_1.png differ diff --git a/Degate-2024/sources/res/ana_2.png b/Degate-2024/sources/res/ana_2.png new file mode 100644 index 0000000..3d0e344 Binary files /dev/null and b/Degate-2024/sources/res/ana_2.png differ diff --git a/Degate-2024/sources/res/ana_3.png b/Degate-2024/sources/res/ana_3.png new file mode 100644 index 0000000..4d913b2 Binary files /dev/null and b/Degate-2024/sources/res/ana_3.png differ diff --git a/Degate-2024/sources/res/ana_layout.png b/Degate-2024/sources/res/ana_layout.png new file mode 100644 index 0000000..55d21f8 Binary files /dev/null and b/Degate-2024/sources/res/ana_layout.png differ diff --git a/Degate-2024/sources/res/chipJuice.jpg b/Degate-2024/sources/res/chipJuice.jpg new file mode 100644 index 0000000..d8ce0d8 Binary files /dev/null and b/Degate-2024/sources/res/chipJuice.jpg differ diff --git a/Degate-2024/sources/res/chip_example.png b/Degate-2024/sources/res/chip_example.png new file mode 100644 index 0000000..a6f2944 Binary files /dev/null and b/Degate-2024/sources/res/chip_example.png differ diff --git a/Degate-2024/sources/res/cmos.png b/Degate-2024/sources/res/cmos.png new file mode 100644 index 0000000..4cfb6b7 Binary files /dev/null and b/Degate-2024/sources/res/cmos.png differ diff --git a/Degate-2024/sources/res/crypto1.png b/Degate-2024/sources/res/crypto1.png new file mode 100644 index 0000000..317b7c0 Binary files /dev/null and b/Degate-2024/sources/res/crypto1.png differ diff --git a/Degate-2024/sources/res/decap.jpg b/Degate-2024/sources/res/decap.jpg new file mode 100644 index 0000000..32087f7 Binary files /dev/null and b/Degate-2024/sources/res/decap.jpg differ diff --git a/Degate-2024/sources/res/dect.png b/Degate-2024/sources/res/dect.png new file mode 100644 index 0000000..49ec045 Binary files /dev/null and b/Degate-2024/sources/res/dect.png differ diff --git a/Degate-2024/sources/res/dect_1.png b/Degate-2024/sources/res/dect_1.png new file mode 100644 index 0000000..5075ec1 Binary files /dev/null and b/Degate-2024/sources/res/dect_1.png differ diff --git a/Degate-2024/sources/res/dect_2.png b/Degate-2024/sources/res/dect_2.png new file mode 100644 index 0000000..5391c0a Binary files /dev/null and b/Degate-2024/sources/res/dect_2.png differ diff --git a/Degate-2024/sources/res/degate.png b/Degate-2024/sources/res/degate.png new file mode 100644 index 0000000..526d90d Binary files /dev/null and b/Degate-2024/sources/res/degate.png differ diff --git a/Degate-2024/sources/res/degate1.png b/Degate-2024/sources/res/degate1.png new file mode 100644 index 0000000..a9b9838 Binary files /dev/null and b/Degate-2024/sources/res/degate1.png differ diff --git a/Degate-2024/sources/res/degate_after_matching.png b/Degate-2024/sources/res/degate_after_matching.png new file mode 100644 index 0000000..05457d4 Binary files /dev/null and b/Degate-2024/sources/res/degate_after_matching.png differ diff --git a/Degate-2024/sources/res/degate_connect.png b/Degate-2024/sources/res/degate_connect.png new file mode 100644 index 0000000..a74c818 Binary files /dev/null and b/Degate-2024/sources/res/degate_connect.png differ diff --git a/Degate-2024/sources/res/degate_gate.png b/Degate-2024/sources/res/degate_gate.png new file mode 100644 index 0000000..420e1a5 Binary files /dev/null and b/Degate-2024/sources/res/degate_gate.png differ diff --git a/Degate-2024/sources/res/degate_instance.png b/Degate-2024/sources/res/degate_instance.png new file mode 100644 index 0000000..15e934b Binary files /dev/null and b/Degate-2024/sources/res/degate_instance.png differ diff --git a/Degate-2024/sources/res/degate_layers.png b/Degate-2024/sources/res/degate_layers.png new file mode 100644 index 0000000..3750f20 Binary files /dev/null and b/Degate-2024/sources/res/degate_layers.png differ diff --git a/Degate-2024/sources/res/degate_matching.png b/Degate-2024/sources/res/degate_matching.png new file mode 100644 index 0000000..9329491 Binary files /dev/null and b/Degate-2024/sources/res/degate_matching.png differ diff --git a/Degate-2024/sources/res/degate_modules.png b/Degate-2024/sources/res/degate_modules.png new file mode 100644 index 0000000..5a9b038 Binary files /dev/null and b/Degate-2024/sources/res/degate_modules.png differ diff --git a/Degate-2024/sources/res/degate_overview.png b/Degate-2024/sources/res/degate_overview.png new file mode 100644 index 0000000..3cbaa60 Binary files /dev/null and b/Degate-2024/sources/res/degate_overview.png differ diff --git a/Degate-2024/sources/res/degate_rule.png b/Degate-2024/sources/res/degate_rule.png new file mode 100644 index 0000000..b709ed8 Binary files /dev/null and b/Degate-2024/sources/res/degate_rule.png differ diff --git a/Degate-2024/sources/res/degate_wires.png b/Degate-2024/sources/res/degate_wires.png new file mode 100644 index 0000000..5fe2370 Binary files /dev/null and b/Degate-2024/sources/res/degate_wires.png differ diff --git a/Degate-2024/sources/res/delayer.png b/Degate-2024/sources/res/delayer.png new file mode 100644 index 0000000..9187244 Binary files /dev/null and b/Degate-2024/sources/res/delayer.png differ diff --git a/Degate-2024/sources/res/delayered.png b/Degate-2024/sources/res/delayered.png new file mode 100644 index 0000000..810da13 Binary files /dev/null and b/Degate-2024/sources/res/delayered.png differ diff --git a/Degate-2024/sources/res/dopant_pmos.png b/Degate-2024/sources/res/dopant_pmos.png new file mode 100644 index 0000000..78e9bb0 Binary files /dev/null and b/Degate-2024/sources/res/dopant_pmos.png differ diff --git a/Degate-2024/sources/res/google_scholar.png b/Degate-2024/sources/res/google_scholar.png new file mode 100644 index 0000000..3229f3b Binary files /dev/null and b/Degate-2024/sources/res/google_scholar.png differ diff --git a/Degate-2024/sources/res/gtkwave.png b/Degate-2024/sources/res/gtkwave.png new file mode 100644 index 0000000..a0205e8 Binary files /dev/null and b/Degate-2024/sources/res/gtkwave.png differ diff --git a/Degate-2024/sources/res/how_1.png b/Degate-2024/sources/res/how_1.png new file mode 100644 index 0000000..d8128e9 Binary files /dev/null and b/Degate-2024/sources/res/how_1.png differ diff --git a/Degate-2024/sources/res/how_2.png b/Degate-2024/sources/res/how_2.png new file mode 100644 index 0000000..88f7d1c Binary files /dev/null and b/Degate-2024/sources/res/how_2.png differ diff --git a/Degate-2024/sources/res/how_3.png b/Degate-2024/sources/res/how_3.png new file mode 100644 index 0000000..d6544fe Binary files /dev/null and b/Degate-2024/sources/res/how_3.png differ diff --git a/Degate-2024/sources/res/how_4.png b/Degate-2024/sources/res/how_4.png new file mode 100644 index 0000000..3eee02d Binary files /dev/null and b/Degate-2024/sources/res/how_4.png differ diff --git a/Degate-2024/sources/res/how_5.png b/Degate-2024/sources/res/how_5.png new file mode 100644 index 0000000..2e80e96 Binary files /dev/null and b/Degate-2024/sources/res/how_5.png differ diff --git a/Degate-2024/sources/res/logo.png b/Degate-2024/sources/res/logo.png new file mode 100755 index 0000000..b9ec2f2 Binary files /dev/null and b/Degate-2024/sources/res/logo.png differ diff --git a/Degate-2024/sources/res/mifare.png b/Degate-2024/sources/res/mifare.png new file mode 100644 index 0000000..a7f47e8 Binary files /dev/null and b/Degate-2024/sources/res/mifare.png differ diff --git a/Degate-2024/sources/res/mifare_reverse.png b/Degate-2024/sources/res/mifare_reverse.png new file mode 100644 index 0000000..1176d92 Binary files /dev/null and b/Degate-2024/sources/res/mifare_reverse.png differ diff --git a/Degate-2024/sources/res/mifare_reverse2.png b/Degate-2024/sources/res/mifare_reverse2.png new file mode 100644 index 0000000..8044abf Binary files /dev/null and b/Degate-2024/sources/res/mifare_reverse2.png differ diff --git a/Degate-2024/sources/res/nand.png b/Degate-2024/sources/res/nand.png new file mode 100644 index 0000000..0ab3d5e Binary files /dev/null and b/Degate-2024/sources/res/nand.png differ diff --git a/Degate-2024/sources/res/nand2_logic.png b/Degate-2024/sources/res/nand2_logic.png new file mode 100644 index 0000000..c1aebaf Binary files /dev/null and b/Degate-2024/sources/res/nand2_logic.png differ diff --git a/Degate-2024/sources/res/nand2_logic_a.png b/Degate-2024/sources/res/nand2_logic_a.png new file mode 100644 index 0000000..75ccb32 Binary files /dev/null and b/Degate-2024/sources/res/nand2_logic_a.png differ diff --git a/Degate-2024/sources/res/nand2_metal.png b/Degate-2024/sources/res/nand2_metal.png new file mode 100644 index 0000000..01f7af3 Binary files /dev/null and b/Degate-2024/sources/res/nand2_metal.png differ diff --git a/Degate-2024/sources/res/nand2_metal_a.png b/Degate-2024/sources/res/nand2_metal_a.png new file mode 100644 index 0000000..f35fbc6 Binary files /dev/null and b/Degate-2024/sources/res/nand2_metal_a.png differ diff --git a/Degate-2024/sources/res/nand2_transistor.png b/Degate-2024/sources/res/nand2_transistor.png new file mode 100644 index 0000000..98f8682 Binary files /dev/null and b/Degate-2024/sources/res/nand2_transistor.png differ diff --git a/Degate-2024/sources/res/nand2_transistor_a.png b/Degate-2024/sources/res/nand2_transistor_a.png new file mode 100644 index 0000000..3ae223e Binary files /dev/null and b/Degate-2024/sources/res/nand2_transistor_a.png differ diff --git a/Degate-2024/sources/res/nand_legic_logic.png b/Degate-2024/sources/res/nand_legic_logic.png new file mode 100644 index 0000000..e47bb2e Binary files /dev/null and b/Degate-2024/sources/res/nand_legic_logic.png differ diff --git a/Degate-2024/sources/res/nand_legic_transistor.png b/Degate-2024/sources/res/nand_legic_transistor.png new file mode 100644 index 0000000..a51ac03 Binary files /dev/null and b/Degate-2024/sources/res/nand_legic_transistor.png differ diff --git a/Degate-2024/sources/res/nand_mifare_logic.png b/Degate-2024/sources/res/nand_mifare_logic.png new file mode 100644 index 0000000..6336b61 Binary files /dev/null and b/Degate-2024/sources/res/nand_mifare_logic.png differ diff --git a/Degate-2024/sources/res/nand_mifare_transistor.png b/Degate-2024/sources/res/nand_mifare_transistor.png new file mode 100644 index 0000000..850d3fd Binary files /dev/null and b/Degate-2024/sources/res/nand_mifare_transistor.png differ diff --git a/Degate-2024/sources/res/npn.png b/Degate-2024/sources/res/npn.png new file mode 100644 index 0000000..dd5dd58 Binary files /dev/null and b/Degate-2024/sources/res/npn.png differ diff --git a/Degate-2024/sources/res/npn.xcf b/Degate-2024/sources/res/npn.xcf new file mode 100644 index 0000000..f91e84b Binary files /dev/null and b/Degate-2024/sources/res/npn.xcf differ diff --git a/Degate-2024/sources/res/old_google_scholar.png b/Degate-2024/sources/res/old_google_scholar.png new file mode 100644 index 0000000..1151da9 Binary files /dev/null and b/Degate-2024/sources/res/old_google_scholar.png differ diff --git a/Degate-2024/sources/res/post_ana_1.png b/Degate-2024/sources/res/post_ana_1.png new file mode 100644 index 0000000..c53929a Binary files /dev/null and b/Degate-2024/sources/res/post_ana_1.png differ diff --git a/Degate-2024/sources/res/post_ana_2.png b/Degate-2024/sources/res/post_ana_2.png new file mode 100644 index 0000000..e7df88a Binary files /dev/null and b/Degate-2024/sources/res/post_ana_2.png differ diff --git a/Degate-2024/sources/res/sem.png b/Degate-2024/sources/res/sem.png new file mode 100644 index 0000000..f4eb097 Binary files /dev/null and b/Degate-2024/sources/res/sem.png differ diff --git a/Degate-2024/sources/res/transistor.png b/Degate-2024/sources/res/transistor.png new file mode 100644 index 0000000..bf5c55c Binary files /dev/null and b/Degate-2024/sources/res/transistor.png differ diff --git a/Degate-2024/sources/res/verilog.png b/Degate-2024/sources/res/verilog.png new file mode 100644 index 0000000..71753cc Binary files /dev/null and b/Degate-2024/sources/res/verilog.png differ diff --git a/LICENSE b/LICENSE deleted file mode 100644 index a612ad9..0000000 --- a/LICENSE +++ /dev/null @@ -1,373 +0,0 @@ -Mozilla Public License Version 2.0 -================================== - -1. Definitions --------------- - -1.1. "Contributor" - means each individual or legal entity that creates, contributes to - the creation of, or owns Covered Software. - -1.2. "Contributor Version" - means the combination of the Contributions of others (if any) used - by a Contributor and that particular Contributor's Contribution. - -1.3. "Contribution" - means Covered Software of a particular Contributor. - -1.4. "Covered Software" - means Source Code Form to which the initial Contributor has attached - the notice in Exhibit A, the Executable Form of such Source Code - Form, and Modifications of such Source Code Form, in each case - including portions thereof. - -1.5. "Incompatible With Secondary Licenses" - means - - (a) that the initial Contributor has attached the notice described - in Exhibit B to the Covered Software; or - - (b) that the Covered Software was made available under the terms of - version 1.1 or earlier of the License, but not also under the - terms of a Secondary License. - -1.6. "Executable Form" - means any form of the work other than Source Code Form. - -1.7. "Larger Work" - means a work that combines Covered Software with other material, in - a separate file or files, that is not Covered Software. - -1.8. "License" - means this document. - -1.9. "Licensable" - means having the right to grant, to the maximum extent possible, - whether at the time of the initial grant or subsequently, any and - all of the rights conveyed by this License. - -1.10. "Modifications" - means any of the following: - - (a) any file in Source Code Form that results from an addition to, - deletion from, or modification of the contents of Covered - Software; or - - (b) any new file in Source Code Form that contains any Covered - Software. - -1.11. "Patent Claims" of a Contributor - means any patent claim(s), including without limitation, method, - process, and apparatus claims, in any patent Licensable by such - Contributor that would be infringed, but for the grant of the - License, by the making, using, selling, offering for sale, having - made, import, or transfer of either its Contributions or its - Contributor Version. - -1.12. "Secondary License" - means either the GNU General Public License, Version 2.0, the GNU - Lesser General Public License, Version 2.1, the GNU Affero General - Public License, Version 3.0, or any later versions of those - licenses. - -1.13. "Source Code Form" - means the form of the work preferred for making modifications. - -1.14. "You" (or "Your") - means an individual or a legal entity exercising rights under this - License. For legal entities, "You" includes any entity that - controls, is controlled by, or is under common control with You. For - purposes of this definition, "control" means (a) the power, direct - or indirect, to cause the direction or management of such entity, - whether by contract or otherwise, or (b) ownership of more than - fifty percent (50%) of the outstanding shares or beneficial - ownership of such entity. - -2. License Grants and Conditions --------------------------------- - -2.1. Grants - -Each Contributor hereby grants You a world-wide, royalty-free, -non-exclusive license: - -(a) under intellectual property rights (other than patent or trademark) - Licensable by such Contributor to use, reproduce, make available, - modify, display, perform, distribute, and otherwise exploit its - Contributions, either on an unmodified basis, with Modifications, or - as part of a Larger Work; and - -(b) under Patent Claims of such Contributor to make, use, sell, offer - for sale, have made, import, and otherwise transfer either its - Contributions or its Contributor Version. - -2.2. Effective Date - -The licenses granted in Section 2.1 with respect to any Contribution -become effective for each Contribution on the date the Contributor first -distributes such Contribution. - -2.3. Limitations on Grant Scope - -The licenses granted in this Section 2 are the only rights granted under -this License. No additional rights or licenses will be implied from the -distribution or licensing of Covered Software under this License. -Notwithstanding Section 2.1(b) above, no patent license is granted by a -Contributor: - -(a) for any code that a Contributor has removed from Covered Software; - or - -(b) for infringements caused by: (i) Your and any other third party's - modifications of Covered Software, or (ii) the combination of its - Contributions with other software (except as part of its Contributor - Version); or - -(c) under Patent Claims infringed by Covered Software in the absence of - its Contributions. - -This License does not grant any rights in the trademarks, service marks, -or logos of any Contributor (except as may be necessary to comply with -the notice requirements in Section 3.4). - -2.4. Subsequent Licenses - -No Contributor makes additional grants as a result of Your choice to -distribute the Covered Software under a subsequent version of this -License (see Section 10.2) or under the terms of a Secondary License (if -permitted under the terms of Section 3.3). - -2.5. Representation - -Each Contributor represents that the Contributor believes its -Contributions are its original creation(s) or it has sufficient rights -to grant the rights to its Contributions conveyed by this License. - -2.6. Fair Use - -This License is not intended to limit any rights You have under -applicable copyright doctrines of fair use, fair dealing, or other -equivalents. - -2.7. Conditions - -Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted -in Section 2.1. - -3. Responsibilities -------------------- - -3.1. Distribution of Source Form - -All distribution of Covered Software in Source Code Form, including any -Modifications that You create or to which You contribute, must be under -the terms of this License. You must inform recipients that the Source -Code Form of the Covered Software is governed by the terms of this -License, and how they can obtain a copy of this License. You may not -attempt to alter or restrict the recipients' rights in the Source Code -Form. - -3.2. Distribution of Executable Form - -If You distribute Covered Software in Executable Form then: - -(a) such Covered Software must also be made available in Source Code - Form, as described in Section 3.1, and You must inform recipients of - the Executable Form how they can obtain a copy of such Source Code - Form by reasonable means in a timely manner, at a charge no more - than the cost of distribution to the recipient; and - -(b) You may distribute such Executable Form under the terms of this - License, or sublicense it under different terms, provided that the - license for the Executable Form does not attempt to limit or alter - the recipients' rights in the Source Code Form under this License. - -3.3. Distribution of a Larger Work - -You may create and distribute a Larger Work under terms of Your choice, -provided that You also comply with the requirements of this License for -the Covered Software. If the Larger Work is a combination of Covered -Software with a work governed by one or more Secondary Licenses, and the -Covered Software is not Incompatible With Secondary Licenses, this -License permits You to additionally distribute such Covered Software -under the terms of such Secondary License(s), so that the recipient of -the Larger Work may, at their option, further distribute the Covered -Software under the terms of either this License or such Secondary -License(s). - -3.4. Notices - -You may not remove or alter the substance of any license notices -(including copyright notices, patent notices, disclaimers of warranty, -or limitations of liability) contained within the Source Code Form of -the Covered Software, except that You may alter any license notices to -the extent required to remedy known factual inaccuracies. - -3.5. Application of Additional Terms - -You may choose to offer, and to charge a fee for, warranty, support, -indemnity or liability obligations to one or more recipients of Covered -Software. However, You may do so only on Your own behalf, and not on -behalf of any Contributor. You must make it absolutely clear that any -such warranty, support, indemnity, or liability obligation is offered by -You alone, and You hereby agree to indemnify every Contributor for any -liability incurred by such Contributor as a result of warranty, support, -indemnity or liability terms You offer. You may include additional -disclaimers of warranty and limitations of liability specific to any -jurisdiction. - -4. Inability to Comply Due to Statute or Regulation ---------------------------------------------------- - -If it is impossible for You to comply with any of the terms of this -License with respect to some or all of the Covered Software due to -statute, judicial order, or regulation then You must: (a) comply with -the terms of this License to the maximum extent possible; and (b) -describe the limitations and the code they affect. Such description must -be placed in a text file included with all distributions of the Covered -Software under this License. Except to the extent prohibited by statute -or regulation, such description must be sufficiently detailed for a -recipient of ordinary skill to be able to understand it. - -5. Termination --------------- - -5.1. The rights granted under this License will terminate automatically -if You fail to comply with any of its terms. However, if You become -compliant, then the rights granted under this License from a particular -Contributor are reinstated (a) provisionally, unless and until such -Contributor explicitly and finally terminates Your grants, and (b) on an -ongoing basis, if such Contributor fails to notify You of the -non-compliance by some reasonable means prior to 60 days after You have -come back into compliance. Moreover, Your grants from a particular -Contributor are reinstated on an ongoing basis if such Contributor -notifies You of the non-compliance by some reasonable means, this is the -first time You have received notice of non-compliance with this License -from such Contributor, and You become compliant prior to 30 days after -Your receipt of the notice. - -5.2. If You initiate litigation against any entity by asserting a patent -infringement claim (excluding declaratory judgment actions, -counter-claims, and cross-claims) alleging that a Contributor Version -directly or indirectly infringes any patent, then the rights granted to -You by any and all Contributors for the Covered Software under Section -2.1 of this License shall terminate. - -5.3. In the event of termination under Sections 5.1 or 5.2 above, all -end user license agreements (excluding distributors and resellers) which -have been validly granted by You or Your distributors under this License -prior to termination shall survive termination. - -************************************************************************ -* * -* 6. Disclaimer of Warranty * -* ------------------------- * -* * -* Covered Software is provided under this License on an "as is" * -* basis, without warranty of any kind, either expressed, implied, or * -* statutory, including, without limitation, warranties that the * -* Covered Software is free of defects, merchantable, fit for a * -* particular purpose or non-infringing. The entire risk as to the * -* quality and performance of the Covered Software is with You. * -* Should any Covered Software prove defective in any respect, You * -* (not any Contributor) assume the cost of any necessary servicing, * -* repair, or correction. This disclaimer of warranty constitutes an * -* essential part of this License. No use of any Covered Software is * -* authorized under this License except under this disclaimer. * -* * -************************************************************************ - -************************************************************************ -* * -* 7. Limitation of Liability * -* -------------------------- * -* * -* Under no circumstances and under no legal theory, whether tort * -* (including negligence), contract, or otherwise, shall any * -* Contributor, or anyone who distributes Covered Software as * -* permitted above, be liable to You for any direct, indirect, * -* special, incidental, or consequential damages of any character * -* including, without limitation, damages for lost profits, loss of * -* goodwill, work stoppage, computer failure or malfunction, or any * -* and all other commercial damages or losses, even if such party * -* shall have been informed of the possibility of such damages. This * -* limitation of liability shall not apply to liability for death or * -* personal injury resulting from such party's negligence to the * -* extent applicable law prohibits such limitation. Some * -* jurisdictions do not allow the exclusion or limitation of * -* incidental or consequential damages, so this exclusion and * -* limitation may not apply to You. * -* * -************************************************************************ - -8. Litigation -------------- - -Any litigation relating to this License may be brought only in the -courts of a jurisdiction where the defendant maintains its principal -place of business and such litigation shall be governed by laws of that -jurisdiction, without reference to its conflict-of-law provisions. -Nothing in this Section shall prevent a party's ability to bring -cross-claims or counter-claims. - -9. Miscellaneous ----------------- - -This License represents the complete agreement concerning the subject -matter hereof. If any provision of this License is held to be -unenforceable, such provision shall be reformed only to the extent -necessary to make it enforceable. Any law or regulation which provides -that the language of a contract shall be construed against the drafter -shall not be used to construe this License against a Contributor. - -10. Versions of the License ---------------------------- - -10.1. New Versions - -Mozilla Foundation is the license steward. Except as provided in Section -10.3, no one other than the license steward has the right to modify or -publish new versions of this License. Each version will be given a -distinguishing version number. - -10.2. Effect of New Versions - -You may distribute the Covered Software under the terms of the version -of the License under which You originally received the Covered Software, -or under the terms of any subsequent version published by the license -steward. - -10.3. Modified Versions - -If you create software not governed by this License, and you want to -create a new license for such software, you may create and use a -modified version of this License if you rename the license and remove -any references to the name of the license steward (except to note that -such modified license differs from this License). - -10.4. Distributing Source Code Form that is Incompatible With Secondary -Licenses - -If You choose to distribute Source Code Form that is Incompatible With -Secondary Licenses under the terms of this version of the License, the -notice described in Exhibit B of this License must be attached. - -Exhibit A - Source Code Form License Notice -------------------------------------------- - - This Source Code Form is subject to the terms of the Mozilla Public - License, v. 2.0. If a copy of the MPL was not distributed with this - file, You can obtain one at http://mozilla.org/MPL/2.0/. - -If it is not possible or desirable to put the notice in a particular -file, then You may include the notice in a location (such as a LICENSE -file in a relevant directory) where a recipient would be likely to look -for such a notice. - -You may add additional accurate notices of copyright ownership. - -Exhibit B - "Incompatible With Secondary Licenses" Notice ---------------------------------------------------------- - - This Source Code Form is "Incompatible With Secondary Licenses", as - defined by the Mozilla Public License, v. 2.0. diff --git a/README.md b/README.md new file mode 100644 index 0000000..e2472f4 --- /dev/null +++ b/README.md @@ -0,0 +1,3 @@ +This repository store some past talks' resources, like PDFs and sources. + +Each talk has its own license, generally CC0 (public domain).