How do you organize information during reverse engineering, pentesting, or CTFs?
嗯,用户发来一个请求,让我帮忙总结一篇文章的内容,控制在一百个字以内,而且不需要特定的开头。首先,我需要理解文章的主要内容。文章讲的是作者在逆向工程和漏洞分析中遇到的问题,主要是信息管理混乱,然后他开发了一个工具来帮助整理思路。 接下来,用户希望总结控制在一百字以内。我得抓住关键点:问题、解决方案、工具名称以及邀请讨论。要简洁明了,同时确保所有重要信息都被涵盖。 然后,我需要避免使用“这篇文章”这样的开头,直接描述内容。可能的结构是先说明问题,再提到工具和邀请反馈。这样既符合要求,又传达了核心信息。 最后,检查字数是否符合要求,并确保语言流畅自然。这样用户就能快速了解文章的主要内容了。 </think> 作者在逆向工程和漏洞分析中发现信息管理混乱是主要问题,并开发了一个名为NotaMy的CLI工具来组织分析流程和笔记。他希望了解他人在复杂工作中的组织方法和工具使用情况。 2026-2-28 07:48:17 Author: www.reddit.com(查看原文) 阅读量:22 收藏

Over the years, while working on reverse engineering, vulnerability analysis, and CTF challenges, I realized that my real problem isn’t finding vulnerabilities — it’s not losing track of the analysis.

During a session I usually end up with:

notes about suspicious functions stack offsets and layout details assembly snippets exploit ideas failed attempts hypotheses to verify

But as the analysis grows, information often becomes scattered and harder to reconnect.

At some point I built a small CLI tool to manage notes hierarchically directly from the terminal, because I wanted something that follows the mental flow of analysis instead of interrupting it. If anyone’s curious, this is the project: https://github.com/IMprojtech/NotaMy

That said, I’m genuinely interested in how you organize your workflow when things get complex.

Do you use specific tools? Personal scripts? Just memory and the terminal?

Curious to hear different approaches.


文章来源: https://www.reddit.com/r/netsecstudents/comments/1rgwoja/how_do_you_organize_information_during_reverse/
如有侵权请联系:admin#unsafe.sh