|
|
|
|
|
[讨论]超好玩的壳,神秘的技术!!!
检测系统 API 的入口是否为 int 03 |
|
|
|
[转帖]ASPack.v2.25.WinALL.Cracked.READ.NFO-BRD
里面有一個 7.1mb 的 delete_me.jpg |
|
[请勿新开主题!甲壳相关主题合并帖]
雕栏玉砌应犹在 |
|
[求助]key.dat 文件,有高手能把他的算号计算出来吗
除了膜拜神奇的小z, 我還能說什麼? key.dat 的內容如下: 用戶名稱: wcnlove523 單位名稱: 九号皇亭 用戶信息: 10.10.10.10 授權硬件: 1059-4E4B-5E3C-9DA0-7F5F-154E-B65A-24F8 授權天數: 132 天 授權期限: 2011-06-28 |
|
|
|
[下载]NoobyProtect 1.7 破解 动画教程
記得 cektop 有自己的論壇 |
|
|
|
[求助]请教:The Enigma Protector加密的东西是不是很容易破解啊?不然为什么新版本一发布就有破解版了?
好好利用 SDK 的話 VMProtect 和 The Enigma Protector 都可以做到很好的保護. 如果只是破解了別人的軟件, 再拿來加密的話, 同樣杯具. |
|
|
|
[求助]求软件破解
这样子似乎不妥 |
|
[原创]几年了,还觉得自己一无是处
如果你有一技之长,而且【仅】有一技之长。 就不会迷茫了。 懂得太多,反而不知道如何抉择。 新手初学时, 难免有自己神马都懂, 技术不就是那么一回事的错觉。 唯有像您这样, 学的越多, 才越加发现不懂的更多。 高处不胜寒啊~~ |
|
|
|
有没有跟踪跳转的工具阿
Conditional Branch Logger (CBL) is a plugin which gives control and logging capabilities for conditional jumps over the full user address space of a process. From the main OllyDbg plugin menu select Conditional Branch Logger -> Configuration. This will open a dialog for managing Included (Logged) and Excluded address ranges, conditional branch type selection and project settings. Ranges can be entered manually or selected from one of the Conditional Branch Logger context menu options available in other OllyDbg windows. Main CPU window (Alt+C): Add multiline selections as Included or Excluded ranges. Executable modules (Alt+E): Add code section as an Included range. Set ranges by procedure for any module. Memory map (Alt+M): Add any memory address region, including non-standard or memory mapped sections, as an Included range. Set ranges by procedure for any module section successfully analyzed. The Set Ranges by Procedure option, available from the main menu or one of the context menus, will open a window from which individual functions can be added as Included or Excluded ranges for any module. The module will be automatically analyzed via the OllyDbg code analysis function if required. Each time the main dialog is closed the CBL jump table window will be updated with the latest conditional jump breakpoint addresses. A context menu provides several options for further controlling the selected breakpoints both before and after analysis. When you are satisfied with the settings, run or single-step the target as usual. The results will be shown in the logfile and/or the CBL jump table window. A button on the OllyDbg toolbar can be used to show the two Conditional Branch Logger custom windows if they have been hidden or closed. A logfile can be specified from the main Configuration dialog in which all executed conditional branch instructions within the selected logging range and the result of whether the jump was taken or not are recorded. If a logfile is not specified a default file named "conditional_branch_logger_default.log" in the OllyDbg main executable directory will be used. Such log files, from different runs of the same program, can then be compared using any good 'diffing' program to find changes in the code execution path as a result of changing inputs or conditions. The majority of Conditional Branch Logger settings, including active breakpoints, are saved in the OllyDbg UDD project files and restored when the target is reopened. This means that you can log conditional branch instructions in system dlls such as ntdll.dll which occur even before the Entry Point of the target is reached. The salient features are as follows: * Ability to detect all conditional branches and log their behaviour during runtime without having to single step the whole process, which results in a dramatic improvement in performance when compared to run trace logging. * Ability to choose specific conditional branch types to monitor and log. * Ability to choose and optimize included ranges and excluded ranges to fine tune the logging. * Ability to disable, delete and restore the logging status of the detected conditional branches. * Log conditional branches from multiple modules. * Ability to list all module procedures that OllyDbg has recognized, with their symbolic names if they exist, as a handy reference so that it is easier to include or exclude ranges. * A text mode log file that could serve to compare two similar runs to detect divergent paths taken with respect to input. * A runtime log window that updates the status of conditional branches live with context menus to edit, delete and disable the entries on the fly. * Context menus in Executable modules window to mass add modules after auto analyzing them or add specific modules to be included in the logging. * Context menus in Memory map window to add any module section, including non-standard or memory mapped regions, to be included in the logging. * Context menus in the main Disassmebly window to add odd ranges to be included or excluded from the logging. * Other features include saving the entire database of conditional branches to the OllyDbg UDD file and restored back when restarting the project. We hope this plugin might prove useful when monitoring execution flow path. Any comments can be directed to the OllyDbg forums at http://www.woodmann.com This plugin is available at http://www.woodmann.com/ollystuph/Conditional_Branch_Logger_v1.0.zip Regards, Blabberer, dELTA and Kayaker |
操作理由
RANk
{{ user_info.golds == '' ? 0 : user_info.golds }}
雪币
{{ experience }}
课程经验
{{ score }}
学习收益
{{study_duration_fmt}}
学习时长
基本信息
荣誉称号:
{{ honorary_title }}
能力排名:
No.{{ rank_num }}
等 级:
LV{{ rank_lv-100 }}
活跃值:
在线值:
浏览人数:{{ visits }}
最近活跃:{{ last_active_time }}
注册时间:{{ user_info.create_date_jsonfmt }}
勋章
兑换勋章
证书
证书查询 >
能力值