Train

PDA

توجه ! این یک نسخه آرشیو شده میباشد و در این حالت شما عکسی را مشاهده نمیکنید برای مشاهده کامل متن و عکسها بر روی لینک مقابل کلیک کنید : OllyDbg Modifications


Reloaded
04-20-2010, 06:01 PM
درود

در این تاپیک نسخه های تغییر داده شده ی OllyDbg رو قرار خواهیم داد. نسخه های تغییر داده شده معمولا دارای ظاهری بهتر و Plugin ها و Script ها مختلف هستند، در بعضی موارد هم با تغییر دادن جزئی در برنامه کاری کرده اند که این دیباگر از دید بعضی پروتکتور های قوی مخفی بمونه. در این پست ورژن اصلی و بدون تغییر OllyDbg رو آپلود کردم.

Reloaded
04-20-2010, 06:02 PM
A version of OllyDbg specifically modified to allow debugging of Themida protected applications.

نسخه تغییر داده شده مخصوص کار با پروتکتور Themida

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:06 PM
Another OllyDbg modification, mainly changed for aesthetic reasons in an XP styles format.

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:07 PM
Not exactly sure what modifications have been made to this modified Olly version other than the obvious edition of new icons, modified layout, colours and About logo. It also contains a collection of the most commonly, and usefully, used pluings plus a wealth of Olly scripts found here on Tuts 4 You.

As to the Olly engine, I'm not sure what has been changed but I'll welcome anyone letting me know so that I can update this description.

The following is from a text file located in the original archive distribution and by the author of this modified engine:

If you wanna work with this modified version of OllyDBG, please don't Add it to menu in Windows Explorer. To do : run "CiM's.exe" then F3 to chose the target file. Else you wont be satisfied by the result of the analyse (it may also crash)...

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:07 PM
This is Diablo's modified version of OllyDbg. Its mainly got a few aesthetic changes to the layout plus it includes all the basic plugins and scripts to get a first time user up and running.

بهترین نسخه تغییر داده شده از نظر من

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:09 PM
This is my version of OllyDBG. I removed all useless plugins and put my preferred ones, and also I set-up a good configuration. With it you should be able to load any protected file (Themida for example).

Sometimes you have to change some options inside plugins (with Obsidium for example), but the current setting is good in 90% of cases.

It has also a more advanced loaddll.exe that allows you to load dll's in different memory locations, so you can rebuild relocations in an easy way.

قوی در براپر انواع پروتکتورها و ترفندهای Anti-Debug

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:10 PM
This engine isn't intentionally called ExeCryptor Edition its actually called ODbyDYK (after the author) but since its been commonly used for ExeCryptor and more generally known as such thats how I've named it here.

I think there has been quite a few modifications to it but not being Chinese I'm unable to read and understand the information within the archive correctly to discover exactly what. Maybe a native or Chinese literate person could pass on to me further details about this engine or translate the included .txt file for me, please :)

بعضی نسخه ها نیازی به توضیح ندارن ;)

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:11 PM
OllyDbg - FOFF Team Edition 1.0

It has been modified to be undetectable by general protectors. A set of the most used and popular plugins is included.

[Only registered and activated users can see links]

OllyDbg - FOFF Team Edition 2.0

This version of OllyDbg is moded to be undetectable by protectors or protecting formulas, it is fast and with most needed plugins for everyday cracking! A few fixes where done, some where reported by the users thanks to them some changes in code for hidding and of course speed is as always even or better......DLL loader was added since first version hadn't one, added plugins and updated osme old version with newer ones..... Most important to note i add a new plugin manager to this package that works on DeFixed only now instead of deleting your plugins you can easly choose which to disable and which to use and return them back too without any problem !!

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:12 PM
This modified OllyDbg version has some bug fixes from the original OllyDbg such as the buffer overflow bug.

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:13 PM
HanOlly.exe + HanOlly.dll - [Themida 1.9.5.0]

- This is a custom Olly and Plugin that defeats Themida 1.9.5.0 Anti-Debugger checks (tested with Shooo's unpackme).
- Olly is modified the least amount possible, only bypasses debugger checks, and nothing more, very close to orgional "clean" olly.
- The plugin also works with OllyIce but I dont know exactly what has been modified in OllyIce so I cannot guarentee it is stable.

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:14 PM
This tool can let you debug a client process as a normal process,you can use normal debugger(exp:ollydbg) to debug the parent process at the same time.

Usage help:
1.This tool must inject into the parent process and listen client process create event.
2.If the parent process not started with the client process at the same time and parent process first.we need inject the debugger by myself.Just selete a process in list and click "inject" ,a debugger will be started. if not please check the lifeODBG's privilege or selected "step up privilege" have another try.when the debugger started,it's just like a simple debugger,if you not selected "Auto listen" be front of Inject you must start listen manually.Just use debugger open a program(exp:notepad.exe).After listen started,the debugger just like fool until the client process created.
3.If the parent and client process start at the same time,we only click "O" to select the program we need,type in the command line in left edit control and click "Debug",the process and debugger will be created automatically.But if not select "auto listen" beforehand,we need start listen manually.(exp:Armadillo)
Options:
"Inject":Just inject the debugger into selected process.
"Inject DLL":Just inject a DLL into selected process.
"Refresh":Refresh the processes list.
"Single debug mode":Let the injected debugger just like a simple debugger,It is can debug but not client process.
"Disable handle close":Disable the client process close the handles in debug event.(exp:Debug EncryptPE).
"Set up privilege":Set up the LifeODBG.exe's privilege.
"Auto listen":turn into debug stats automatically when the debugger be injected.
"Passive mode":Just use for the process we started is a client process when the parent process append start debugger automatically.
"Call back debug event":Set up who will be call back to the debugger.

از بهترین ها!

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:15 PM
Plug-in to load, additional support for the mouse wheel window, Execryptor been detected. Rear number library functions.

Paste to copy BUG. Closed OD shortcuts ALT + Q, the environment variable settings can be automatically downloaded and loaded

PDB, and so on. Part of the revised approach from the Internet. There have been some changes do not remember where it is

taken from the ... Amended the title of the window. Unmodified category, can make its own decisions. STRONGOD or with the use

of.

Annex contains some of his extracted LIB file. Can be identified only some of the serial number and not the function of CALL

or JMP

To load signs need to set the environment variable.
Set the environment variable name: _NT_SYMBOL_PATH
Content
SRV * F: \ Ollydbg \ Symbols * [Only registered and activated users can see links] F: \ Ollydbg \ Symbols make its own decisions as

needed.

Of course, we can not set the environment variable load PDB. But the need to batch or CMD window to run the following

command.
set _NT_SYMBOL_PATH = SRV * F: \ Tools \ Ollydbg \ Symbols * [Only registered and activated users can see links] F: \ Ollydbg \

Symbols make its own decisions as needed.
NoLoVeR.exe (based on the need to amend its own name OD)

The annex is symchk.exe download symbols (PDB) with the use of methods can be used symchk c: \ windows \ system32 \ *. dll

download this way, and not set the environment variable to use / s parameter setting when Symbol path Will automatically use

the default path SRV *% SYSTEMROOT% \ SYMBOLS * [Only registered and activated users can see links] that under the system directory

SYMBOLS directory.

SYMCHK.EXE use

symchk [/r] [/q] [Input options] <Filename> [/s <SymbolPath>] [options]

<Filename> Name of the file or directory that contains the executables
to perform symbol checking on.

/s <SymbolPath> Semi-colon separated list of symbol paths. Symbol server
paths are allowed. To retrieve symbols to a downstream
store, use "SRV*<downstream store>*<symbol server>" for
the symbol path. See the debugger documentation for more
details.

/r Perform recursive operations on the <Filename> specified. The
wildcard * can be used in filenames.

/q Turn off all output options by default. Only output turned on
with a output flag (see below) will be printed

--------------------------------------------------------------------------------
* Input options (choose only one):
/if <Filename> Input is a file name. Wildcards can be used to specify
the file name. Default if nothing is specified.
/id <DumpFile> Input is a dump file.
/ih <HotFix> Input is a self-extracting Hotfix cab.
/ie <ExeName> Input is an application name that is currently running.
If the provided ExeName is '*', all currently running
processes will be checked.
/im <ManifestList> Input is a manifest previously created using the /om <file>
option.
/ip <ProcessId> Input is a process id. If the provided ProcessID is '*',
all currently running processes will be checked.
/it <TextFileList> Input is a list of files, one per line, inside of a text
file.

--------------------------------------------------------------------------------
* Action options (choose only one):
/av For each binary, Verify symbols exist and match. Default.

--------------------------------------------------------------------------------
* Symbol checking options:
/cc when symbol checking a hotfix cab, don't look for symbols inside the cab.
By default, symchk will look for symbols in the cab as well as in the
provided symbol path.
/cn When symbol checking a running process, don't suspend that process. User
must ensure the process doesn't exit before symbol checking finishes.
/cs Skip verifying that there is CodeView data. Symchk will verify that there
IS codeview data by default.

- Symbol checking options for DBG information (choose one):
/ds If image was built so that there is information that belongs in a DBG
file, then this option verifies that the DBG information is stripped
from the image and that the image points to a DBG file. Default.
/de If image was built so that there is information that belongs in a DBG
file, then this option verifies that the DBG information is STILL in the
image and that the image does not point to a DBG file.
/dn Verify that the image does not point to a DBG file and that DBG
information is not in the image.

- Symbol checking options for PDB files:
/pa Allow both public and private PDBs. Default.
/pf Verify that PDB files contain full source information.
/ps Verify that PDB files are stripped and do not contain full source
(private) information.
/pt Verify that PDB files are stripped, but do have type information. Some
PDB files may be stripped but have type information added back in.

--------------------------------------------------------------------------------
* Symbol checking exclude options:
/ea <Filename> Don't perform symbol checking for the binaries listed in the
file specified. <Filename> is a text file that contains the
name of each binary, one per line.
/ee <Filename> Perform symbol checking and report files that pass or are
ignored, but don't report errors for binaries listed in the
file specified. <Filename> is a text file that contains the
name of each binary, one per line.

--------------------------------------------------------------------------------
* Symbol path options:
/s[epsu] <SymbolPath> Use <SymbolPath> as the search path.

NOTE: If the '/s' option is not used, SymChk defaults to using the value
in %_NT_SYMBOL_PATH%. If %_NT_SYMBOL_PATH% is not defined, then SymChk
will default to:
SRV*%SYSTEMROOT%\SYMBOLS*[Only registered and activated users can see links]

* Modifiers (choose all that apply):
e - check each path individually instead of checking all paths at once.
p - force checking for private symbols. Public symbols will be treated as
not matching. (Implies the 'e' and 'u' modifiers.)
s - force checking for public (split) symbols. Private symbols will be
treated as not matching. (Implies the 'e' and 'u' modifiers.)
u - force updating of downstream stores. If the symbol path includes a
downstream store, always re-check the server for the symbol. Only
stores that are checked against will be updated.
NOTE: The 's' and 'p' options are mutually exclusive. Only the last one
present will be used.

--------------------------------------------------------------------------------
* Output options (choose all that apply):
/ob Give the full path for binaries in the output messages for symbol
checking.
/oc[x[a]] <Directory> Create a flat symbols tree in <Directory> which
contains all matching symbols. If 'x' is also used, copy the matching
binaries into <Directory> as well. If 'a' is also present, the binary
will always be copied to the flat symbol tree even if symbol checking
failed.
/od List all details. Same as /oe /op /oi
/oe List individual errors. Errors will be sent to the output by default.
This option is only needed when using /q
/oi List each file that is ignored.
/op List each file that passes.
/os Give the full path for symbols in the output messages for symbol
checking.
/ot Send totals to the output. Totals are sent to the output by default.
This option is only needed when using /q
/ov Print version information for checked binaries as well.

- Extended output options:
/ol <File> In addition to the messages sent to standard out, write a
file that contains a comma separated list of all the
binaries and their symbols that pass symbol checking.
/om <Manifest> Print out a manifest file for later use with the '/im' option.
/v Turn on verbose output mode.
--------------------------------------------------------------------------------
* Module filtering options when checking processes or dump files (choose one):
/fm <Module> ****** results to only include the named module.

--------------------------------------------------------------------------------
* Misc options
/port Old usage to new usage quick porting table
--------------------------------------------------------------------------------

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:16 PM
+ New look
+ Modified code for almost perfect hiding
+ Modified code for expanded windows
+ Modified code for %s overflow RCE exploit
+ Modified code to make symbols load properly
+ OllyDRX Plugin Patcher

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:17 PM
This is the final OllyDbg release from Hacnho, his further enhanced OllyDbg Hacnho modification. It includes all the bug fixes from his original Hacnho. It is also compressed using the Themida 1.xx Ring-0 engine to help hide the debugger from detection. Be warned it runs quite slowly because of this and it is not very compatible with certain operating systems (WinXP SP2) and applications like anti-virus tools. Blue Screens of Death (BOD) are quite common with this Olly.

معروف!

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:18 PM
This is an updated release based upon the final OllyDbg release from Hacnho, his further enhanced OllyDbg Hacnho modification. It includes all the bug fixes from his original Hacnho. It is also compressed using the Themida 1.xx Ring-0 engine to help hide the debugger from detection. Be warned it runs quite slowly because of this and it is not very compatible with certain operating systems (WinXP SP2) and applications like anti-virus tools. Blue Screens of Death (BOD) are quite common with this Olly.

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:19 PM
It is a version of "Emergency" is the basics to make a good crackeo, this is a package "Reduced", but I want to make portable versions of several programs, and As ultraedit and others that require installation and makes heavy.

THIS OLLYSND PORTABLE NOT NEED CONFIGURARSE, THE ROUTE OF THIS PLUGINS AUTO-CONFIGURADA.

So he can run from anywhere without the need to change Nothing is prepared and ready for use.

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:20 PM
OllyDbg moded for ExeCryptor & THEMIDA

Add the possibility of deleting all points of stopping Remove all breakpoints
Auto path UDD & plugin
Reference search directly from the toolbar
Show offset in status bar
Amendment to show the number of additions to the list
Additions located

1 - advancedolly.dll
2 - analyzethis.dll
3 - API_Break.dll
4 - bookmarks2.dll
5 - cmdbar.dll
6 - HideOD.dll
7 - NonaWrite.dll
8 - ODbgScript.dll
9 - OllyBugfix.dll
10 - OllyDump.dll
11 - OllyMoreMenu.dll
12 - PhantOm.dll
13 - Poison.dll
14 - ustrref.dll
15 - StrongOD.dll

This amendment took me time so there is no difference between them and the original
They accept each others additions modified
Do not forget pray for me and my family

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:20 PM
This version has been modded to work with Themida and EXECryptor. It also has cosmetic changes to make the design and layout of OllyDbg more appealing.

Plugins and scripts provided in the archive for use on the above mentioned protectors.

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:21 PM
Apart from a couple of easthetic modifications Shadow's Olly modification has quite a few bug fixes and changes. Not much is known about exactly what changes have been made but it is regarded as being one of the better modified OllyDbg versions available.

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:22 PM
Another modified version of OllyDbg 1.10. Unfortunately I cannot tell you exactly what has been modified apart from the obvious aesthetics.

[Only registered and activated users can see links]

Reloaded
04-20-2010, 06:23 PM
آخرین نسخه OllyDbg (بدون تغییر)

OllyDbg 2.0.0.7 (Beta 3)

OllyDbg 2.0 is a 32-bit assembler-level analyzing Degugger with intuitive interface. It is especially useful if source code is not available or when you experience problems with your compiler.

Requirements. Developed and tested mainly under Windows 2000 and Windows XP, but should work under any Windows version: 95, 98, ME, NT, 2000, XP, 2003 Server, Vista, Windows 7 and so on. For a comfortable debugging you will need at least 500-MHz processor. OllyDbg is memory hungry. If you debug large application with all features enabled, it may allocate 200-300 megabytes for backup and analysis data.

Supported instruction sets. OllyDbg 2.0 supports all existing 80x86-compatible CPUs: MMX, 3DNow!, including Athlon extentions, and SSE instructions up to SSSE3 and SSE4.

Configurability. More than 120 options (oh, no! This time it's definitely too much!) control OllyDbg's behaviour and appearance.

Data formats. Dump windows display data in all common formats: hexadecimal, ASCII, UNICODE, 16 and 32-bit signed/unsigned/hexadecimal integers, 32/64/80-bit floats, addresses, disassembly (MASM, IDEAL, HLA or AT&T). It also decodes and comments many Windows-specific structures, including PE headers, PEB, Thread data blocks and so on.

Help. OllyDbg 2.0 includes built-in help on all 80x86 integer and floating-point commands. If you possess Windows API help (win32.hlp, not included due to copyright reasons), you can attach it and get instant help on system API calls.

Startup. You can specify executable file in command line, select it from menu, drag-and-drop file to OllyDbg, restart last debugged program or attach to already running application. OllyDbg supports just-in-time debugging and debugging of child processes. You can detach from the debugged process, and it will continue execution. Installation is not necessary!

Code highlighting. Disassembler can highlight different types of commands (jumps, conditional jumps, pushes and pops, calls, returns, privileged and invalid) and different operands (general, FPU/SSE or segment/system registers, memory operands on stack or in other memory, constants). You can create custom highlighting schemes.

Threads. OllyDbg can debug multithread applications. You can switch from one thread to another, suspend, resume and kill threads or change their priorities. Threads window displays errors for each thread (as returned by call to GetLastError).

Analysis. Analyzer is one of the most significant parts of OllyDbg. It recognizes procedures, loops, switches, tables, constants and strings embedded in code, tricky constructs, calls to API functions, number of function’s arguments, import sections and so on. It attempts to determine not only the number of stack arguments in the unknown functions, but even their meaning. Analysis makes binary code much more readable, facilitates debugging and reduces probability of misinterpretations and crashes. It is not compiler-oriented and works equally good with any PE program.

Full UNICODE support. All operations available for ASCII strings are also available for UNICODE, and vice versa. OllyDbg is able to recognize UTF-8 strings.

Names. OllyDbg knows symbolic names of many (currently 7700) constants, like window messages, error codes or bit fields, and decodes them in calls to known functions.

Known functions. OllyDbg recognizes by name more than 2200 frequently used Windows API functions and decodes their arguments. You can add your own descriptions. You may set logging breakpoint on a known or guessed function and protocol arguments to the log.

Calls. OllyDbg can backtrace nested calls on the stack even when debugging information is unavailable and procedures use non-standard prologs and epilogs.

Stack. In the Stack window, OllyDbg uses heuristics to recognize return addresses and stack frames. Notice however that they can be remnants from the previous calls. If program is paused on the known function, stack window decodes arguments of known and guessed functions. Stack also traces and displays the chain of SE handlers.

Search. Plenty of possibilities! Search for command (exact or imprecise) or sequence of commands, for constant, binary or text string (not necessarily contiguous), for all commands that reference address, constant or address range, for all jumps to selected location, for all referenced text strings, for all intermodular calls, for masked binary sequence in the whole allocated memory and so on. If multiple locations are found, you can quickly navigate between them.

Breakpoints. OllyDbg supports all common kinds of breakpoints: INT3, memory and hardware. You may specify number of passes and set conditions for pause. Breakpoints may conditionally protocol data to the log. Number of INT3 and memory breakpoints is unlimited: in the extreme case of hit trace, OllyDbg sometimes sets more than 100000 INT3 breakpoints. On a fast CPU, OllyDbg can process up to 20-30 thousand breakpoints per second.

Watches. Watch is an expression evaluated each time the program pauses. You can use registers, constants, address expressions, boolean and algebraical operations of any complexity.

Execution. You can execute program step-by-step, either entering subroutines or executing them at once. You can run program till next return, to the specified location, or backtrace it from the deeply nested system API call back to the user code. When application runs, you keep full control over it. For example, you can view memory, set breakpoints and even modify code "on-the-fly". At any time, you can pause or restart the debugged program.

Hit trace. Hit trace shows which commands or procedures were executed so far, allowing you to test all branches of your code. Hit trace starts from the actual location and sets INT3 breakpoints on all branches that were not traced so far. The breakpoints are removed when command is reached (hit).

Run trace. Run trace executes program in the step-by-step mode and protocols execution to the large circular buffer. Run trace is fast: when fast command emulation is enabled, OllyDbg traces up to 1 million commands per second! Run trace protocols registers (except for SSE), flags, contents of accessed memory, thread errors and - for the case that your code is self-modifying - the original commands. You may specify the condition to stop run trace, like address range, expression or command. You can save run trace to the file and compare two independent runs. Run trace allows to backtrack and analyse history of execution in details, millions and millions of commands.

Profiling. Profiler calculates how many times some instruction is listed in the run trace buffer. With profiler, you know which part of the code takes most of execution time.

Patching. Built-in assembler automatically selects the shortest possible code. Binary editor shows data simultaneously in ASCII, UNICODE and hexadecimal form. Old good copy-and-paste is also available. Automatical backup allows to undo changes. You can copy modifications directly to executable file, OllyDbg will even adjust fixups.

UDD. OllyDbg saves all program and module-related information to the individual file and restores it when module is reloaded. This information includes labels, comments, breakpoints, watches, analysis data, conditions and so on.

Customization. You can specify custom fonts, colour and highlighting schemes.

And much more! This list is far from complete, there are many features that make OllyDbg 2.0 the friendly debugger.

[Only registered and activated users can see links]

aliiran2008
05-28-2010, 10:54 PM
وقتی میررم تو سایت ای ارورا می ده
Unfortunately Tuts 4 You Encountered A Server Error

Rubiks

The server encountered an unexpected condition that prevented it from fulfilling the request by your browser for access to the requested URL.

This is a 'catch-all' error generated by the server. Unfortunately the server cannot be more specific about the error condition in its response.

Please wait for the server to respond in... 54

Reloaded
05-28-2010, 11:46 PM
وقتی میررم تو سایت ای ارورا می ده
Unfortunately Tuts 4 You Encountered A Server Error

Rubiks

The server encountered an unexpected condition that prevented it from fulfilling the request by your browser for access to the requested URL.

This is a 'catch-all' error generated by the server. Unfortunately the server cannot be more specific about the error condition in its response.

Please wait for the server to respond in... 54

بعضی وقتا سرور Tuts4You بدلیل بازدید بالا Down میشه که بعد از چند ساعت دوباره درست میشه.

aliiran2008
05-29-2010, 09:33 AM
تا حالا دوبار اومدم دانلود کنمئ قطع میشه
میشه اخرین ورژنشا تو سایت اپ کنید

Reloaded
05-29-2010, 06:07 PM
تا حالا دوبار اومدم دانلود کنمئ قطع میشه
میشه اخرین ورژنشا تو سایت اپ کنید

لینک ها سالمه. این رو همین الان از لینک بالا دانلود کردم.

Service Manual
08-02-2010, 11:34 AM
سلام

براي راحتي بيشتر دوستان فايل ها را در انجمن آپلود مي کنم .

OllyDbg - 9 in1 for Themida

Service Manual
08-02-2010, 11:39 AM
OllyDbg - Diablo's Modification Updated 20.09.2008

Service Manual
08-02-2010, 11:45 AM
OllyDbg - FOFF Team Edition 2.0

Service Manual
08-02-2010, 11:48 AM
OllyDbg - LifeODBG 1.4

Service Manual
08-02-2010, 11:51 AM
OllyDbg - Richardo Narvaja

Service Manual
08-02-2010, 11:55 AM
OllyDbg - Sabre-Gold

Service Manual
08-02-2010, 11:58 AM
OllyDbg - Shadow Modification

Service Manual
08-02-2010, 12:02 PM
OllyDbg - TSRh Style

Service Manual
08-02-2010, 12:13 PM
OllyDbg - YPOGEiOS

Service Manual
08-02-2010, 12:17 PM
OllyDbg Execryptor Edition

Service Manual
08-02-2010, 12:30 PM
OllyDbg - Portable OllySnD

Black Dream
09-19-2010, 07:26 PM
درود

در این تاپیک نسخه های تغییر داده شده ی ollydbg رو قرار خواهیم داد. نسخه های تغییر داده شده معمولا دارای ظاهری بهتر و plugin ها و script ها مختلف هستند، در بعضی موارد هم با تغییر دادن جزئی در برنامه کاری کرده اند که این دیباگر از دید بعضی پروتکتور های قوی مخفی بمونه. در این پست ورژن اصلی و بدون تغییر ollydbg رو آپلود کردم.

سلام دوست عزیزمن می خوام بدونم کاراین دیباگر چیه وبه چه دردی می خوره؟ آیا می شه با این برنامه تروجان ها را غیرقابل شناسایی کرد؟آیا می شه آنتی ها راغیرفعال کرد؟لطفاچنتا فیلم آموزشی در این زمینه قراردهید.خیلی خیلی ممنون می شوم

HAMIDx9
01-30-2011, 07:47 PM
0llyDbg v1.10 Modified by Ali.Dbg OllyDbg + Plugins

mahdi_rafatjah
01-13-2012, 06:35 AM
سلام
ممنون واقعا خیلی محشر بود فقط میگم اگه دوست عزیزمون Reloaded می تونستند همه ی این فایل هایی که کینک کرده بودن به تاتس 4 یو رو یه زیپ بکنن بذارن این جا خیلی خوبه آخه من 3 تاشو دانلود کردم دیگه نمی ذاره ممنون

mohammadf255
03-18-2012, 10:34 AM
سلام دوستان
ببخشید تاپیک قدیمی رو بالا میارم ولی خب چه کنم که ورژن جدید اومد دیگه...

ورژن جدید: 2.01 + پلاگین هاشو هم قرار دادم..

ayoub242
05-12-2012, 02:55 PM
برای کسانی که مشکل دارن با دانلود از tuts ، میتون از ایندکس دانلود کنن

[Only registered and activated users can see links]