Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Baungarten-CINVESTAV authored Nov 4, 2023
1 parent 46168ee commit 8ce2522
Showing 1 changed file with 10 additions and 2 deletions.
12 changes: 10 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,17 +4,25 @@

Author: Emilio Baungarten

<p align="center">
<img src="https://github.com/Baungarten-CINVESTAV/HW_TI_Encryption/blob/main/HTML_Docs/source/images/HardwareTrojan1.png" width=50% height=50%>
</p>

## Objective:

<p align="justify">
The project encompasses the development of a Verilog module designed to store encryption keys used in various encryption algorithms. This module is engineered to support popular encryption algorithms, including Advanced Encryption Standard (AES), Data Encryption Standard (DES), and Secure Hash Algorithm (SHA). These algorithms play a pivotal role in securing sensitive data and communications across various applications.


One noteworthy aspect of this project is the utilization of a feature called Large Language Model (LLM) to modify the behavior of the Verilog module. This modification inserts a Trojan at the Register Transfer Level (RTL) level, changing the module's capabilities by enabling the storage of the last eight keys used in the previous encryption algorithms, AES, DES, and SHA. This adaptation empowers the module to offer key management, allowing third-person access and reusing recent encryption keys. As a result, it violates the efficiency and convenience of cryptographic operations, particularly in scenarios where frequent keys are necessary.

</p>

## Background:
## Documentation


<p align="center">
Comprehensive documentation and a step-by-step explanation of the project's development can be accessed at the following URL:

[https://hw-ti-encryption.readthedocs.io/en/latest/](https://hw-ti-encryption.readthedocs.io/en/latest/)

</p>

0 comments on commit 8ce2522

Please sign in to comment.