| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 |
- ICSE
- 생명의 삶
- libFuzzer
- libxml2
- reading critique
- build
- citrus
- software-testing
- graphfuzz
- 대학원생
- 바이너리 분석
- fault-localization
- 프로그램 분석
- 소프트웨어 취약저 분석
- software-engineering
- Environment
- Cyber Security
- binary code analysis
- linking
- unit-testing
- protobuf
- binary code analaysis
- 느헤미야
- FSE
- 묵상
- vulnerabilties
- fuzzing
- sotware-testing
- QT
- Software Engineering
- Today
- Total
목록binary code analysis (2)
heechan.yang
The paper addresses the idea that the source code is not what is actually executed. This idea is defined as the WYSINWYX (What You See Is Not What You eXecute) phenomenon. The paper elaborates more on this phenomenon by showing concrete examples in program compilation and execution. The author explains that such phenomenon is caused due to the operations of compilers such as dead code eliminatio..
Paper Summary:Through this paper "Reflection on Trusting Trust", the author shares a moral that no code should be fully trusted even after great effort of analysis. The author builds up to his claim with thee stages that together, explains an example case of an attack within C compiler. The first stage shows a small example of a program the produces a self-reproducing program. It shows how it is..