FEED Validator

for Atom and RSS and KML

Congratulations!

This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 43, column 0: description should not contain itemprop attribute (12 occurrences) [help]
```
<a class='resized_img' rel='lightbox[10388759]' id='ipb-attach-url-5616-0 ...
```
line 52, column 3: description should not contain relative URL references: /discuss/uploads/monthly_02_2024/post-32128-0-31700100-1708088264_thumb.png (12 occurrences) [help]
```
]]></description>
   ^
```

line 643, column 0: description should not contain iframe tag [help]

<p><iframe id="ytplayer" class="EmbeddedVideo" type="text/html" width="640"  ...

line 695, column 0: Missing atom:link with rel="self" [help]
```
</channel>
```

Source: http://www.rohitab.com/discuss/rss/forums/1-new-topics/

<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
<title>New Topics</title>
<description>New topics from all forums</description>
<link>http://www.rohitab.com/discuss</link>
<pubDate>Fri, 16 Feb 2024 12:54:43 +0000</pubDate>
<ttl>10</ttl>
<item>
<title>Custom API Definitions Not Working</title>
<link>http://www.rohitab.com/discuss/topic/63784-custom-api-definitions-not-working/</link>
<description><![CDATA[I've been monitoring an executable which uses a 3rd party DLL and I can see the function names in the summary window.
 
If I create a custom XML definitions file for the DLL and specify only one of the API calls I'm interested in (very simple function, one parameter and a return value) then when I restart API Monitor, although the XML file loads successfully, when I monitor the executable again, the API function from the definition file is no longer shown in the summary window and other API functions not documented are also no longer present.
 
What may cause this?
 
There are no errors with the XML definition and it appears within the "API Filter" in an "uncategorized" group.
 
For reference, this is the XML definition:
<pre title='Extensible Markup Language (XML)' class='brush:xml'>
<ApiMonitor>
<Include Filename="Headers\windows.h.xml" />
<Module Name="brom.dll" CallingConvention="STDCALL">
<Variable Name="OTP_OPERATION" Type="Alias" Base="UINT">
<Enum>
<Set Name="OTP_READ" Value="0" />
<Set Name="OTP_WRITE" Value="1" />
<Set Name="OTP_LOCK" Value="2" />
<Set Name="OTP_WRITE_AND_LOCK" Value="3" />
<Set Name="OTP_OPERATION_END" Value="4" />
</Enum>
</Variable>
<Api Name="OTPOpToString" CallingConvention="STDCALL">
<Param Type="OTP_OPERATION" Name="op" />
<Return Type="char*" />
<Success Return="NotEqual" Value="0" />
</Api>
</Module>
</ApiMonitor>
</pre>
<a class='resized_img' rel='lightbox[10388759]' id='ipb-attach-url-5616-0-04240200-1716144437' href="/discuss/uploads/monthly_02_2024/post-32128-0-31700100-1708088264.png" title="Capture2.PNG - Size: 62.98KB, Downloads: 10"><img itemprop="image" src="/discuss/uploads/monthly_02_2024/post-32128-0-31700100-1708088264_thumb.png" id='ipb-attach-img-5616-0-04240200-1716144437' style='width:100;height:43' class='attach' width="100" height="43" alt="Capture2.PNG" /></a>
is what the summary windows looks like when the new XML definition is selected in the filter:
 
<a class='resized_img' rel='lightbox[10388759]' id='ipb-attach-url-5615-0-03332300-1716144437' href="/discuss/uploads/monthly_02_2024/post-32128-0-46029900-1708088258.png" title="Capture1.PNG - Size: 85.78KB, Downloads: 8"><img itemprop="image" src="/discuss/uploads/monthly_02_2024/post-32128-0-46029900-1708088258_thumb.png" id='ipb-attach-img-5615-0-03332300-1716144437' style='width:100;height:58' class='attach' width="100" height="58" alt="Capture1.PNG" /></a>
is what the summary window looks like when API Monitor knows nothing about the XML definition but with the DLL loaded into the "External DLL" window:
 
 
]]></description>
<pubDate>Fri, 16 Feb 2024 12:54:43 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/63784-custom-api-definitions-not-working/</guid>
</item>
<item>
<title><![CDATA[[C/C++] Reverse Engineering Tutorial for newbies]]></title>
<link>http://www.rohitab.com/discuss/topic/35537-cc-reverse-engineering-tutorial-for-newbies/</link>
<description><![CDATA[ --------------------------------------------------------- ---===> Reverse Engineering Tutorial <===--- --==> For Beginners <==-- on Windows --------------------------------------------------------- -= SECTION 1 (Misc. information) =- I. WHAT THIS TUTORIAL WILL COVER II. PREFACE III. REQUIREMENTS IV. RECOMMENDATIONS -= SECTION 2 (WPM hack) =- I. WHAT TO HACK/HOW TO DO IT II. THE "GAME" III. THE MEMORY SEARCHER IV. TYING IT ALL TOGETHER (WPM) -= SECTION 3 (DLL hack) =- I. ADVANTAGES TO CODE INJECTION II. HOW TO CREATE A BASIC DLL III. DLL FILES -> MORE IN DEPTH IV. FINDING MEMORY ADDRESSES (OllyDbg) V. HOW 'JUMP PATCHING' WORKS VI. CALLING A FUNCTION FROM WITHIN APPENDIXES: A. How to create a DLL project (MSVC, Dev-C++, etc) B. TextControl header file C. Links to function prototypes used (MSDN site) D. WPM Hack (source code) E. DLL Hack (source code) F. DLL Injector (source code) - I take no credit for this G. The game (source code, "Hack me") ------------------------------------------------------------------------------------------------------------------- Section 1 WHAT THIS TUTORIAL WILL COVER: - General theory behind 'hacking' games - Usage of (C/C++) WriteProcessMemory function - Injection of code (patch jumping to a user-defined *.dll) PREFACE (skip if you want): This tutorial is aimed in a very general direction, towards helping people who have never really 'hacked' anything before, but want to try. Somebody who may, or may not have knowledge in the 'field' area, of hacking. If you've never hacked before, but used them, and used memory searchers before, this is for you to read! If you've created a few hacks before, but never tried to inject a *.dll before, or created a patch jump... This tutorial might be for you, but then again, you may already know, but never really have done it. REQUIREMENTS: - Knowledge of C or C++ (if you've only coded in C, know that "naked" is a C++ only keyword) - A compiler that is capable of inline, Intel syntax Assembly (MSVC is, but is not share/freeware) RECOMMENDATIONS: - Knowledge of basic Assembly (extremely helpful) - Knowledge of how to use a memory searcher (TSearch, ArtMoney, or another) - Knowledge of how to use a debugger (OllyDbg, SoftIce) - Knowledge of how computers function, in general (memory addresses, virtual memory addresses, etc) Section 2 WHAT TO HACK/HOW TO DO IT: Usually games have something very significant in them, that you'd like to modify. In this tutorial, I've created a very specific program, for you to reverse engineer. You may be thinking right now, "Oh, so this will teach me absolutely nothing? Just waste my time...?" If you thought that, you're completely right! Quit reading right now, and go read something else! :) No, but really, it's the same logic! In order to hack a game, you need to do the following: - Find something you want to modify (a "target"), such as life, or a name - Find a way to find it, such as a memory searcher (this does NOT always work) - Find a main loop of code where stuff is constantly executed THE "GAME": As mentioned, there is a "game" or program, you'll be using to hack ('reverse engineer'), that I wrote. All it does, is displays some text, sleeps for a little bit, 'erases' it with spaces, and writes it again. Your objectives (that I will NOT help with) will be the following: - Find and remove the function that removes the text - Modify the placement of the text that is blinking (X, Y coordinates) - Modify the persons name with WriteProcessMemory THE MEMORY SEARCHER: I've chosen to specifically use ArtMoney, but you can use whatever you're comfortable with. Now, in a "real" game, the first thing you'll want to do, is to find a specific value, such as your life... But in this case, since I wrote this (for all intents and purposes): It'll be the "age" being displayed (21). You're able to increase, and decrease the age's actual value, by using the +/- keys (numpad). In a real game, the only way you could get the value to change, is by dying, or leveling up, or whatever. Again: For all intents and purposes of learning, I did this, so please, do not complain, be thankful! :P In ArtMoney (ArtMoney SE v7.32), this is the following steps you'd take to find the actual "age" value: Select process -> ABCD (Hack me.exe) Search -> "Exact value" -> 21 -> Type "Custom" -> Address Range "All" -> OK Filter -> "Exact value" -> 22 (assuming you increased, else 20 if you decrease) -> Type "Custom" Now, it should pop out at you, with a single address, but if it doesn't, try again from the beginning. The address for me (and I'm sure it'll change for every reader) is: 0x012FF7C I will hence fourth use this address, even though it will change per reader, just remember that! WE HAVE THE ADDRESS, NOW WHAT? Now that you have the memory address of the value you'd like to modify, you're done! You simply write a program that will modify that program accordingly, and that's as easy-as-pie! You can do this many ways... I've chosen to show you how to do it both ways, and the first way I shall teach, is the infamous: WPM (WriteProcessMemory) - it's a little more "limited" than other methods, but if it works, use it! ;) WRITEPROCESSMEMORY FUNCTION: There's no real way to explain this, other than: Always look up functions on Google. Since there isn't much to say, I'll simply post the function prototype, and a potential example of use. The prototype for WriteProcessMemory is: <pre title='C Source' class='brush:c'>BOOL WINAPI WriteProcessMemory(
__in HANDLE hProcess, // The target process
__in LPVOID lpBaseAddress, // The memory address IN the target
__in LPCVOID lpBuffer, // A pointer to a null-terminated string to write
__in SIZE_T nSize, // The size of the buffer to write
__out SIZE_T *lpNumberOfBytesWritten // [Optional] NULL if not used, returns how many bytes were wrote
);</pre> It is defined in "Winbase.h" although you include "Windows.h" to use it. Now, to use WPM, you need one very important piece of information, and that is the process handle! To obtain the process handle, you could go a few various ways, but the method I much prefer is, to use FindWindow (to obtain a window handle), then GetWindowThreadProcessId (to obtain a PID (process ID)), and finally! You'd call upon OpenProcess to obtain a handle, to the window. TYING IT ALL TOGETHER (WPM): By now, you should have looked up the other two functions (FindWindow, GetWindowThreadProcessId), and realized that they require a HWND variable, and a DWORD variable to use, to be put together with the HANDLE variable, for use with the actual WriteProcessMemory function, so you can modify the process memory! Now, there is sometimes, where you actually need to use yet another function, called VirtualProtectEx function, but I'll leave that, for you to look into all on your own (it's VERY simple, I assure you). This is what you should have by now (code snippet): <pre title='C Source' class='brush:c'>int main() {
HWND hwnd; // Holding the window title
HANDLE handle; // Holding the handle to the process
DWORD pid; // Holding the PID of the process
hwnd = FindWindow(0, "ABCD");
GetWindowThreadProcessId(hwnd, &pid);
handle = OpenProcess(PROCESS_ALL_ACCESS, FALSE, pid);
return 0;
}</pre> There are ways to make this better, but that's up to you to find (one is very unapparent). With this small snippet of code, you now have all the tools necessary to modify the games variable (age)! :) As I've said before: This address may not be the same for you, but bare with me, and know that I'm only referencing what I personally see, and use, on my own machine, and it will most likely change from CPU to CPU. To modify (at this point) specifically the age variable, we could go about it something like this: <pre title='C Source' class='brush:c'>BYTE NewAge = 99; // New age to be assigned
if (!WriteProcessMemory(handle, (void *)0x012FF7C, &NewAge, sizeof(NewAge), NULL)) { // If it fails
printf("Failed to write to memory!"); // Let the person know, but if it works, nothing pops up!
}</pre> This might/might not come in handy, but you could also check to see if a variable changed a value, just by using the opposite function (I know, 'retarded', but whatever): ReadProcessMemory! It stores a value from a process memory, into a variable, of your own program, so you could if statement it, and potentially warn a user, that their resource is getting low? or just have it auto-increase their resource? Section 3 ADVANTAGES TO CODE INJECTION: There is clearly! Always advantages, and disadvantages to code injection. The ability to 'detect' that you're hacking will differ very little (if none at all) whether you're injecting a *.dll, or using native API library calls such as WriteProcessMemory! By loading a new library ('injecting' a *.dll) into the game's process, you meld yourself together with the process (game), unifying yourself into one! Which allows you to easily modify registers (eax, esi, edx, ETC), and see their values, copy them, or execute functions... Without much effort at all! You can even jump to your own *.dll file by modifying the game's process (this is what is called a "hook" or "jump patch"). This would allow you to significantly modify stuff within the game without much overhead, or confusion... except game patch updates modify the offsets, updating them isn't very hard (just do what you did the first time, to get the offsets back again), and presto! It should be good (unless they drastically changed stuff, like the arguments/function it calls/etc). But anyways, back to the topic! HOW TO CREATE A BASIC DLL: As you know, the entire "dll injection" method revolves around a dynamic link library (*.dll), and you're probably wondering how to create one, or perhaps you're wondering what it is. In a nutshell, a *.dll is a file, that's full of precompiled functions, that you can access with an executable program - the idea is that you make a very generic, or useful function, that gets called tons of times (such as SendMessage, or WriteProcessMemory), and compile it into a tiny 512 KB (probably less) *.dll file (with tons of other functions), and presto! Now you only have one function precompiled, that's simply called by 30,000 programs rather than 30,000 programs recreating the same function over and over! This can also save on compilation time, because it's one less thing that must be translated, instead it's just a simple, plain call to the dynamic link library (although you have to link to it). :P An extremely basic (the MOST basic) DLL you can possibly compile would look like this: <pre title='C Source' class='brush:c'>BOOL APIENTRY DllMain(HANDLE hModule, DWORD reason, LPVOID lpReserved) {
return true;
}</pre> APIENTRY is actually #defined as, "FAR PASCAL" - FAR is #defined as, "FAR __far" - PASCAL is #defined as, "PASCAL __pascal" You may find the definitions in WinDef.h for yourself! :) However! As extremely simple as this very compilable *.dll file is, it's rather useless like this! It can be loaded into any given executable program, but it won't do anything, so to fix that... Well, before I continue, you should know what the actual arguments passed to DllMain are/are for. The only valid, and useful one to us is "reason," and that is, 'the reason' the DLL is being called. There are four potential values it could be, but probably the most important one is: DLL_PROCESS_ATTACH To be more clear, the four possible values that 'reason' could be, are: - DLL_PROCESS_ATTACH (0x01) - DLL_PROCESS_DETACH (0x00) - DLL_THREAD_ATTACH (0x02) - DLL_THREAD_DETACH (0x03) If you'd like, feel free to refer to appendix c and follow the MSDN link that explains more in-depth. But for the sake of explaining how to write a DLL, and how to get it to 'do stuff,' I won't explain it. DLL FILES -> MORE IN DEPTH: OK! A *.dll is pretty much no different than any runnable program (command, or executable)... It can execute instructions to the machine, and do anything, and everything else, so at this point, if you haven't figured it out yet, I shall explain it even more for you! Add functions to your *.dll! <pre title='C Source' class='brush:c'>void __declspec(naked) FindMe() {
__asm {
pushad
pushfd
test eax, eax
test eax, eax
test eax, eax
test eax, eax
test eax, eax
test eax, eax
test eax, eax
test eax, eax
test eax, eax
test eax, eax
popfd
popad
ret
}
}
void MyFunction() {
FindMe();
return;
}
bool APIENTRY DllMain(HANDLE hModule, DWORD reason, LPVOID lpReserved) {
if (reason == DLL_PROCESS_ATTACH) {
MyFunction();
}
return true;
}</pre> There isn't much more to say about *.dlls in this sense, as you can clearly see, you can add functions! The next step honestly, is to modify the target (game!) program, and inject your *.dll (even though there isn't any 'code patching' occuring yet, it'll allow you to use a debugger to 'see inside'). You may refer to appendix F to aquire the DLL Injector; If you don't know how it works, worry not! Know that it'll inject your *.dll into the target process (you must recompile it with your *.dll/*.exe). Now, run the game, run the DLL injector (to inject your DLL into a process), open up OllyDbg, and attach it to the DLL! (Alt + E is to "Open executables") From here, you should be able to find your function, "MyFunction" and a lot easier, "FindMe," and if you did, you SHOULD see all the "test eax, eax" statements, and at this point, you should feel happy, proud, and give yourself a pat on your own back, for having such a huge accomplishment! You found your own function, in your DLL file! :P FINDING MEMORY ADDRESSES (OllyDbg): I surely do hope you're familiar enough with OllyDbg now that you'll be able to follow along... If you're using another debugger, other than OllyDbg, I sincerely apologize, because I do not 'support,' or use any other debuggers in this tutorial for beginners, but if you are/do using/use OllyDbg, 'grats! ^_^ Crack open OllyDbg, run the game, and attach the debugger (OllyDbg!) to the game, and here's where the magic really begins, and it all starts falling together (hopefully)! You know that the age is 21, right? You know where that address specifically is (for me, it is 0x012FF7C), and what you can do, is go to the "hex dump" in OllyDbg, hold CTRL + G (enter expression in dump), and enter the memory address. This will take you to the actual address that the "21" (0x15 in hex) value is being stored, and from there you can place a memory access breakpoint on it (meaning the program will STOP ("Paused") if it is read from, or written, or whatever). For me, this popped on the offset: 0x0401006 If you press CTRL + F9 (execute 'til return) twice, then F8 (Step over) once, you'll land upon a "ADD ESP, 8h" Assembly command, and here, you can clearly see as bright as day, that you have exited the function that prints the number "21," you'll also notice you've entered the main loop of the game! :) HOW 'JUMP PATCHING' WORKS: Let's pause on creating that *.dll, and finding memory addresses (since we've aquired the main game loop, and another potentially useful function address), and step back a bit, and think about it from a new light. We have the addresses, but how do we put these to use? We can't without redirecting the game's main code! To redirect the games code to our *.dll, sort of like a detour on the road... we need to have it 'jump' accross the lane, and veer into our little cubby hole of code! We need it to obey us, but before we can even do that, we need to find a location that's suitable, and since there's a million and one things I need to explain, I'd better quit blabbering and start explaining! To quote somebody, who helped me extremely in understanding: "(ebx - ecx) == (source - (destination + 5h))" "ebx" is 'your function' and "ecx" is a memory offset from the game, if that helps explain it any. I honestly just use this function, which I take NO credit for writing (although I was writing my own): <pre title='C Source' class='brush:c'>void JmpPatch(void *pDest, void *pSrc, int nNops = 0) {
DWORD OldProt;
VirtualProtect(pSrc, 5 + nNops, PAGE_EXECUTE_READWRITE, &OldProt);
*(char*)pSrc = (char)0xE9;
*(DWORD*)((DWORD)pSrc + 1) = (DWORD)pDest - (DWORD)pSrc - 5;
for (int i = 0; i < nNops; ++i) { *(BYTE*)((DWORD)pSrc + 5 + i) = 0x90; }
VirtualProtect(pSrc, 5 + nNops, OldProt, &OldProt);
}</pre> An example of use: <pre title='C Source' class='brush:c'>
if (reason == DLL_PROCESS_ATTACH) {
JmpPatch(&FindMe, (PBYTE)0x0401006, 0);
}</pre> This will cause a "jmp" command to be placed in the "Hack me.exe" game's actual code, and that's it! :) I sincerely apologize for the extremely poor, and lacking explanation, I am not that good at explaining it. As I've said before: I honestly do not think about it a lot, and personally just use the function. You would probably like to find an op-code that will hold just enough room for the jump. If there's any extra spaces, just nop (no operation) them. Remember: The program does not know that it is being taken away from its "normal" cycle of instructions, the op-code you over write must be "replaced" right before you jump BACK to the location in the game (you must jump back to where you had left off, except one instruction infront of the "jump" command, so it doesn't just jump back). CALLING A FUNCTION FROM WITHIN: Like with any language, all functions require arguments to be passed to them, and in C, this is rather simple! But when you translate from C to Assembly, it may seem a little weird at first, especially based on the different calling conventions (__naked is as it sounds: it does nothing). You can look 'em up on MSDN's site, or Wikipedia, or probably even google around on your own (remember: GOOGLE IS YOUR FRIEND). If you would please, open up your favorite debugger (I will be using OllyDbg), and attach it to "Hack me.exe." If you hold "CTRL + A," after you've attached it to the process, and opened up the executable module, you will see that it shows the "analyases code" from the debugger - this helps from time to time, especially when you're trying to find something as simple as a native GetAsyncKeyState function call! If you look around for a bit, you'll notice that the "Sleep(500);" function call you wrote in C, is actually translated to, "PUSH 1F4, CALL <sleep offset>" but that might not be very clear to you. Now let's say you created a jump patch, and you wanted to make the program display some text else-where... What you'd want to do, is find the function that displays text, and call upon it! But you must realize, it has to take some sort of arguments, and you must match these arguments (if it's text, it will differ obviously)! Lucky for us, there's a function created specifically for this purpose, just to learn. PrintTextXY takes a character pointer, and two integers, and it will do the rest for you (placing/displaying). I'll assume you've already found a location (somewhere) in the game, and created your own jump patch, so continuing on from that point (actually, I will be using the "DLL" from earlier as an example, and add on): <pre title='C Source' class='brush:c'>void PrintText(int X, int Y, char *szText) {
static int PrintXY_Offset = 0x04011D3;
__asm {
pushad
pushfd
push X
push Y
push szText
call DWORD PTR DS:[PrintXY_Offset]
popfd
popad
ret
}
return;
}
void __declspec(naked) FindMe() {
__asm {
pushad
pushfd
}
PrintText("Hello World!");
__asm {
popfd
popad
<replace op-code>
jmp <one op-code above jump patch>
}
}</pre>]]></description>
<pubDate>Sun, 11 Jun 2023 12:46:06 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/35537-cc-reverse-engineering-tutorial-for-newbies/</guid>
</item>
<item>
<title>Win32 - Increased CPU usage when using multiple buffers</title>
<link>http://www.rohitab.com/discuss/topic/51073-win32-increased-cpu-usage-when-using-multiple-buffers/</link>
<description><![CDATA[First post here. Can someone take a look at my code? I have created a bunch of sine distortion graphic effects, but I've noticed that the two effects which distort the x and y axis at the same time use more CPU. I am using two buffers to get those working. The gameloop is by EternalWindows with some changes. Also, I may be wrong, but I get the impression that the animation isn't as smooth as It should be. Any corrections are welcome. Thanks!
<pre title='C Source' class='brush:c'>
#include <windows.h>
#include <math.h>
#define WINDOW_CLASS_NAME "DEMOCLASS"
#define WINDOW_TITLE "GDI Demo"
#define WINDOW_WIDTH 405
#define WINDOW_HEIGHT 290
struct BACKBUFFER {
HWND hwnd;
HDC hdc;
HDC hdc2;
HBITMAP hbmp;
HBITMAP hbmp2;
HBITMAP hbmpPrev;
HBITMAP hbmpPrev2;
HBRUSH hbr;
int cx;
int cy;
};
typedef struct BACKBUFFER BACKBUFFER;
struct OBJECT {
HDC hdc;
HBITMAP hbmp;
HBITMAP hbmpPrev;
float amplitude;
float frequency;
float offset;
int x;
int y;
int cx;
int cy;
};
typedef struct OBJECT OBJECT;
BOOL g_bPause = FALSE;
BOOL g_bLostFocus = FALSE;
BOOL g_bRunning = FALSE;
BACKBUFFER g_backBuffer = {0};
OBJECT g_background = {0};
int Run(void);
BOOL CreateBackbuffer(HWND hwnd);
void DestroyBackbuffer();
BOOL CreateObjects(HWND hwnd);
void DestroyObjects();
void Update(void);
void Render(void);
void Show(void);
void Distort_Bitmap(void);
LRESULT CALLBACK WindowProc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam);
int WINAPI WinMain(HINSTANCE hinst, HINSTANCE hinstPrev, LPSTR lpszCmdLine, int nCmdShow)
{
TCHAR szAppName[] = TEXT("sample");
HWND hwnd;
WNDCLASSEX wc;
RECT rc;
DWORD dwStyle;
wc.cbSize = sizeof(WNDCLASSEX);
wc.style = 0;
wc.lpfnWndProc = WindowProc;
wc.cbClsExtra = 0;
wc.cbWndExtra = 0;
wc.hInstance = hinst;
wc.hIcon = (HICON)LoadImage(NULL, IDI_APPLICATION, IMAGE_ICON, 0, 0, LR_SHARED);
wc.hCursor = (HCURSOR)LoadImage(NULL, IDC_ARROW, IMAGE_CURSOR, 0, 0, LR_SHARED);
wc.hbrBackground = (HBRUSH)GetStockObject(NULL_BRUSH);
wc.lpszMenuName = NULL;
wc.lpszClassName = szAppName;
wc.hIconSm = (HICON)LoadImage(NULL, IDI_APPLICATION, IMAGE_ICON, 0, 0, LR_SHARED);
if (RegisterClassEx(&wc) == 0) return 0;
dwStyle = WS_OVERLAPPEDWINDOW & ~WS_THICKFRAME & ~WS_MAXIMIZEBOX;
SetRect(&rc, 0, 0, 640, 480);
AdjustWindowRect(&rc, dwStyle, FALSE);
hwnd = CreateWindowEx(0, szAppName, WINDOW_TITLE, dwStyle, CW_USEDEFAULT, CW_USEDEFAULT, rc.right - rc.left, rc.bottom - rc.top, NULL, NULL, hinst, NULL);
if (hwnd == NULL)
return 0;
ShowWindow(hwnd, nCmdShow);
UpdateWindow(hwnd);
return Run();
}
LRESULT CALLBACK WindowProc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
switch (uMsg) {
case WM_CREATE:
if (!CreateBackbuffer(hwnd))
return -1;
if (!CreateObjects(hwnd))
return -1;
case WM_KEYDOWN:
if (wParam == VK_PAUSE) {
g_bPause = !g_bPause;
if (g_bPause)
Show();
}
return 0;
case WM_PAINT:
Show();
break;
case WM_NCLBUTTONDOWN:
Show();
break;
case WM_ERASEBKGND:
return 0;
case WM_SETFOCUS:
g_bLostFocus = FALSE;
return 0;
case WM_KILLFOCUS:
g_bLostFocus = TRUE;
return 0;
case WM_DESTROY:
DestroyBackbuffer();
DestroyObjects();
PostQuitMessage(0);
return 0;
default:
break;
}
return DefWindowProc(hwnd, uMsg, wParam, lParam);
}
int Run(void)
{
MSG msg;
BOOL bMove;
DWORD dwInterval = 15;
DWORD dwCurTime, dwNextTime;
g_bRunning = TRUE;
bMove = TRUE;
dwNextTime = timeGetTime();
while (g_bRunning) {
if (g_bPause || g_bLostFocus || PeekMessage(&msg, NULL, 0, 0, PM_NOREMOVE)) {
if (GetMessage(&msg, NULL, 0, 0) > 0)
DispatchMessage(&msg);
else
break;
}
else {
if (bMove) {
Update();
Render();
bMove = FALSE;
}
dwCurTime = timeGetTime();
if (dwCurTime > dwNextTime) {
Show();
dwNextTime += dwInterval;
if (dwNextTime < dwCurTime)
dwNextTime = dwCurTime + dwInterval;
bMove = TRUE;
}
else
Sleep(dwNextTime - dwCurTime);
}
}
return (int)msg.wParam;
}
BOOL CreateBackbuffer(HWND hwnd)
{
HDC hdc;
hdc = GetDC(hwnd);
g_backBuffer.hdc = CreateCompatibleDC(hdc);
g_backBuffer.hbmp = CreateCompatibleBitmap(hdc, 640, 480);
g_backBuffer.hdc2 = CreateCompatibleDC(hdc);
g_backBuffer.hbmp2 = CreateCompatibleBitmap(hdc, 640, 480);
if (g_backBuffer.hbmp == NULL) {
ReleaseDC(hwnd, hdc);
return FALSE;
}
g_backBuffer.hbmpPrev = (HBITMAP)SelectObject(g_backBuffer.hdc, g_backBuffer.hbmp);
g_backBuffer.hbmpPrev2 = (HBITMAP)SelectObject(g_backBuffer.hdc2, g_backBuffer.hbmp2);
ReleaseDC(hwnd, hdc);
g_backBuffer.hwnd = hwnd;
g_backBuffer.hbr = (HBRUSH)GetStockObject(BLACK_BRUSH);
g_backBuffer.cx = 640;
g_backBuffer.cy = 480;
return TRUE;
}
void DestroyBackbuffer()
{
if (g_backBuffer.hdc || g_backBuffer.hdc2 != NULL) {
if (g_backBuffer.hbmp || g_backBuffer.hbmp2 != NULL) {
SelectObject(g_backBuffer.hdc2, g_backBuffer.hbmpPrev2);
DeleteObject(g_backBuffer.hbmp2);
SelectObject(g_backBuffer.hdc, g_backBuffer.hbmpPrev);
DeleteObject(g_backBuffer.hbmp);
}
DeleteDC(g_backBuffer.hdc2);
DeleteDC(g_backBuffer.hdc);
}
}
BOOL CreateObjects(HWND hwnd)
{
HDC hdc;
BITMAP bm;
hdc = GetDC ( hwnd );
g_background.hdc = CreateCompatibleDC(hdc);
g_background.hbmp = (HBITMAP)LoadImage(NULL, "pic.bmp", IMAGE_BITMAP,0,0,LR_LOADFROMFILE | LR_DEFAULTSIZE);
if (g_background.hbmp == NULL) {
ReleaseDC(hwnd, hdc);
return FALSE;
}
g_background.hbmpPrev = (HBITMAP)SelectObject(g_background.hdc, g_background.hbmp);
g_background.amplitude = 10.0;
g_background.frequency = 1 * ((3.14 * 2)/320);
GetObject(g_background.hbmp, sizeof(BITMAP), &bm);
g_background.x = 0;
g_background.y = 0;
g_background.cx = bm.bmWidth+320;
g_background.cy = bm.bmHeight;
ReleaseDC(hwnd, hdc);
return TRUE;
}
void DestroyObjects()
{
if (g_background.hdc != NULL){
if (g_background.hbmp != NULL){
SelectObject(g_background.hdc, g_background.hbmpPrev);
DeleteObject(g_background.hbmp);
}
DeleteDC(g_background.hdc);
}
}
void Update(void)
{
Distort_Bitmap();
}
void Render(void)
{
RECT rc;
SetRect(&rc, 0, 0, g_backBuffer.cx, g_backBuffer.cy);
FillRect(g_backBuffer.hdc, &rc, g_backBuffer.hbr);
FillRect(g_backBuffer.hdc2, &rc, g_backBuffer.hbr); //added
Update();
}
void Show(void)
{
HDC hdc;
hdc = GetDC(g_backBuffer.hwnd);
BitBlt(hdc, 0, 0, g_backBuffer.cx, g_backBuffer.cy, g_backBuffer.hdc2, 0, 0, SRCCOPY);
ReleaseDC(g_backBuffer.hwnd, hdc);
}
void Distort_Bitmap(void)
{
for (int i=0; i < g_background.cy; i++) {
int stretchFactor = g_background.amplitude*(sin(g_background.frequency*(i+g_background.offset)));
BitBlt(g_backBuffer.hdc,g_background.frequency*sin(3.14)+80,i+(stretchFactor)+80, 320, 2, g_background.hdc, 0, i, SRCCOPY);
g_background.offset+=0.2;
if (g_background.offset >=g_background.cx) g_background.offset =0;
}
for (int i=0; i < g_background.cx; i++) {
int stretchFactor = g_background.amplitude*(sin(g_background.frequency*(i+g_background.offset)));
BitBlt(g_backBuffer.hdc2,g_background.x+(i+stretchFactor)+80,g_background.y+80, 2,255, g_backBuffer.hdc, i, 0, SRCCOPY);
g_background.offset+=0.2;
if (g_background.offset >=g_background.cx) g_background.offset =0;
}
}
</pre>

 
]]></description>
<pubDate>Sun, 15 Jan 2023 16:22:40 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/51073-win32-increased-cpu-usage-when-using-multiple-buffers/</guid>
</item>
<item>
<title>Wireless Wep Key Cracking</title>
<link>http://www.rohitab.com/discuss/topic/29793-wireless-wep-key-cracking/</link>
<description><![CDATA[WEP Cracking by %ebx DISCLAIMER: I DO NOT encourage cracking others wireless protection!. This is illegal! The AP I'm cracking belongs to me and I wrote this as a proof of concept. There's a reason they have a key, they don't want you stealing their bandwidth! That beeing said: Why would you want to crack WEP protected wireless networks? 1. Because you don't have a internet connection and that bastard neighbor of yours has the money to get one 2. Your dad pulls your ethernet cable out every night at 10 so you don't stay up all night talking to some bimbo 3. Because you can and you want to! What do you need? 1. A wireless network card(obviouslly) with drivers up and running. Your need your driver to be able to inject packets, otherwise you're gonna spend days gathering enough packets for a successful crack. I had to recompile my kernel module because I use a damn Broadcom card, and injection wouldn't work..not sure why. 2. Linux (Ubuntu Gutsy in this case), though you can do this from Windows and MacOS too, with the appropriate software. 3. The aircrack-ng suite <pre title='C Source' class='brush:c'>$sudo apt-get install aircrack-ng</pre> Ok..off we go [NOTE] I color coded the "sensitive" information: AP MAC address, AP Name, miscelaneous MAC addresses and my MAC address. There's a legend on the bottom with the colours and what they correspond to So..how do we crack WEP? Well basically...whenever a wireless card "talks" to a access point (AP from now on), it sends/receives some interesting info along with the packets, info that can be used to get the actual WEP key(using the aircrack utility). What we need is to gather enough packets so that aircrack can do it's job [NOTE] eth0 is our wireless card for the remaining of this tutorial STEP 1: We must put the wireless card in monitor mode. A wireless card in monitor mode basically allows us to sniff all the wireless traffic around us We do this by issuing the following command: [check screenshot 1] <pre title='C Source' class='brush:c'>ebx@skynet:-$ sudo airmon-ng start eth0</pre>You should see "monitor mode enabled" in there. That means we're good and can proceed to the next step Step 2: In this step we need to get the MAC address of the AP we're after, the AP name and the channel it's on. To do this we first sniff all the traffic so we can see what AP we're gonna focus on(the one with more beacons/data usually, if we want a random crack, or a specific one if you're set on someone "special") We do this by running: [check screenshot 1] <pre title='C Source' class='brush:c'>ebx@skynet:-$ sudo airodump-ng eth0</pre>You should get a screen similar to the one in screenshot 2 I grayed out everything I don't need. The important part is the line with the AP I got my eyes on, the one with red. We just make a note of the MAC address, the AP name and the channel the AP is on. Step 3: This is the step where we actually start capturing packets for use in the cracking We do this by running: [check screenshot 3] <pre title='C Source' class='brush:c'>ebx@skynet:-$ sudo airodump-ng -c 1 --bssid [THE AP MAC ADDRESS] -w capture eth0</pre>This starts the actual capture of packets. It captures all traffic on channel 1 (the channel the AP was on), but only the traffic going to our AP, and saves the packets in a file called capture-01.cap (airodump-ng adds the -01.cap) You should get something similar to screenshot 4. The "#Data" field is what were's interested in getting high enough. We need thousands of packets to have a successful crack. This is all fine and dandy, and we could just leave this for...hmmm...days 'till it gathers enough packets...Or we could speed the process QUITE A LOT! by using aireplay-ng <img class='bbc_img' src='http://www.rohitab.com/discuss/public/style_emoticons/default/smile.gif' class='bbc_emoticon' alt=':)' /> Step 4: In this step we speed things up by sending a lot of packets to the AP, so we get responses from it (responses that contain that interesting data we're after <img class='bbc_img' src='http://www.rohitab.com/discuss/public/style_emoticons/default/wink.gif' class='bbc_emoticon' alt=';)' /> This is done in 2 steps I'm not going to explain the options I use, just trust me <img class='bbc_img' src='http://www.rohitab.com/discuss/public/style_emoticons/default/smile.gif' class='bbc_emoticon' alt=':)' /> . Or run aireplay-ng with no options so you can see the available options A. First we need to associate out wireless card with the AP so it accepts packets from us [check screenshot 5] <pre title='C Source' class='brush:c'>ebx@skynet:-$ sudo aireplay-ng -1 0 -e [AP NAME] -a [AP MAC ADDRESS] -h [MY MAC ADDRESS] eth0</pre> If we get "Association successful :-)" then we can proceed to the next step of the packet sending speed up, otherwise something is wrong, eiter you're to far away from the AP, or it has MAC filtering enabled. If we have a successful association, then we can see our MAC address appears as associated to the AP (check screenshot 5 - the left terminal) B. Now we need to start sending packets. Again I'm not going to explain the options used, just RTFM! <img class='bbc_img' src='http://www.rohitab.com/discuss/public/style_emoticons/default/tongue.gif' class='bbc_emoticon' alt=':P' /> [check screenshot 6] <pre title='C Source' class='brush:c'>ebx@skynet:-$ sudo aireplay-ng -3 -b [AP MAC ADDRESS] -h [MY MAC ADDRESS] -x 100 eth0</pre> After a bit of packet reading you should see the sent packets run like crazy, wich also makes our "#Data" field go up like there's no tomorrow!. This is good news. If this step fails, your card/driver probably doesn't have injection capabilities..wich is bad news. But not entirely, just means that you're gonna spend a whole lot more time in cracking because packets come in A LOT slower! This is it...now we just need to sit and wait for enough packets so we can begin our crack. You can just wait and try running the next step from time to time, or do it like I do, run the next step now as it updates the reading realtime. Step 5: In this step we start cracking the WEP using aircrack-ng [check screenshot 7] <pre title='C Source' class='brush:c'>ebx@skynet:-$ sudo aircrack-ng -n 64 -f 4 capture-01.cap</pre>"-n 64" tells aircrack-ng to crack a 64 bit WEP (I already know the key is 64 bit as I have cracked it before <img class='bbc_img' src='http://www.rohitab.com/discuss/public/style_emoticons/default/tongue.gif' class='bbc_emoticon' alt=':P' /> ). If not sure test with "-n 64" of with no "-n" at all if that fails. "-f" is the fudge factor. If cracking doesn't work, try raising this to some other value(below 32) If enough packets were gathered, you WILL have a successfull crack. With 250.000 packets I (well aircrack-ng) cracked the key in 3 seconds! [check screenshot 8] We get the key in HEX and ASCII. We will be using the ASCII one. This is it. We have the key, now all there's left is to use it! Now we can just stop capturing (CTRL+C in the other 2 terminals, then close them). After packet capturing is over, we need to take our card OUT of monitor mode <pre title='C Source' class='brush:c'>ebx@skynet:-$ sudo airmon-ng stop eth0</pre> Step 6: This is optional. You could use any GUI manager to set things up, but I prefer doing it manually <pre title='C Source' class='brush:c'>ebx@skynet:-$ sudo iwconfig eth0 essid [AP NAME]
ebx@skynet:-$ sudo iwconfig eth0 ap [AP MAC ADDRESS]
ebx@skynet:-$ sudo iwconfig eth0 key on
ebx@skynet:-$ sudo iwconfig eth0 key s:[THE ASCII KEY]
ebx@skynet:-$ sudo dhclient eth0</pre> Enjoy <img class='bbc_img' src='http://www.rohitab.com/discuss/public/style_emoticons/default/smile.gif' class='bbc_emoticon' alt=':)' /><div id='attach_wrap' class='clearfix'>
<h4>Attached Thumbnails</h4>
<ul>
<li class=''>
<a class='resized_img' rel='lightbox[10036155]' id='ipb-attach-url-1907-0-12390200-1716144437' href="/discuss/uploads/monthly_03_2008/post-9807-1206026136.jpg" title="1.jpg - Size: 477.98KB, Downloads: 1039"><img itemprop="image" src="/discuss/uploads/monthly_03_2008/post-9807-1206026136_thumb.jpg" id='ipb-attach-img-1907-0-12390200-1716144437' style='width:100;height:63' class='attach' width="100" height="63" alt="1.jpg" /></a>
</li>
<li class=''>
<a class='resized_img' rel='lightbox[10036155]' id='ipb-attach-url-1908-0-12397700-1716144437' href="/discuss/uploads/monthly_03_2008/post-9807-1206026147.jpg" title="2.jpg - Size: 500.89KB, Downloads: 853"><img itemprop="image" src="/discuss/uploads/monthly_03_2008/post-9807-1206026147_thumb.jpg" id='ipb-attach-img-1908-0-12397700-1716144437' style='width:100;height:63' class='attach' width="100" height="63" alt="2.jpg" /></a>
</li>
<li class=''>
<a class='resized_img' rel='lightbox[10036155]' id='ipb-attach-url-1909-0-12401500-1716144437' href="/discuss/uploads/monthly_03_2008/post-9807-1206026157.jpg" title="3.jpg - Size: 512.07KB, Downloads: 640"><img itemprop="image" src="/discuss/uploads/monthly_03_2008/post-9807-1206026157_thumb.jpg" id='ipb-attach-img-1909-0-12401500-1716144437' style='width:100;height:63' class='attach' width="100" height="63" alt="3.jpg" /></a>
</li>
<li class=''>
<a class='resized_img' rel='lightbox[10036155]' id='ipb-attach-url-1910-0-12405000-1716144437' href="/discuss/uploads/monthly_03_2008/post-9807-1206026166.jpg" title="4.jpg - Size: 492.87KB, Downloads: 572"><img itemprop="image" src="/discuss/uploads/monthly_03_2008/post-9807-1206026166_thumb.jpg" id='ipb-attach-img-1910-0-12405000-1716144437' style='width:100;height:63' class='attach' width="100" height="63" alt="4.jpg" /></a>
</li>
<li class=''>
<a class='resized_img' rel='lightbox[10036155]' id='ipb-attach-url-1911-0-12408200-1716144437' href="/discuss/uploads/monthly_03_2008/post-9807-1206026176.jpg" title="5.jpg - Size: 479.45KB, Downloads: 569"><img itemprop="image" src="/discuss/uploads/monthly_03_2008/post-9807-1206026176_thumb.jpg" id='ipb-attach-img-1911-0-12408200-1716144437' style='width:100;height:63' class='attach' width="100" height="63" alt="5.jpg" /></a>
</li>
<li class=''>
<a class='resized_img' rel='lightbox[10036155]' id='ipb-attach-url-1912-0-12411400-1716144437' href="/discuss/uploads/monthly_03_2008/post-9807-1206026185.jpg" title="6.jpg - Size: 519.63KB, Downloads: 550"><img itemprop="image" src="/discuss/uploads/monthly_03_2008/post-9807-1206026185_thumb.jpg" id='ipb-attach-img-1912-0-12411400-1716144437' style='width:100;height:63' class='attach' width="100" height="63" alt="6.jpg" /></a>
</li>
<li class=''>
<a class='resized_img' rel='lightbox[10036155]' id='ipb-attach-url-1913-0-12414600-1716144437' href="/discuss/uploads/monthly_03_2008/post-9807-1206026197.jpg" title="7.jpg - Size: 537.09KB, Downloads: 561"><img itemprop="image" src="/discuss/uploads/monthly_03_2008/post-9807-1206026197_thumb.jpg" id='ipb-attach-img-1913-0-12414600-1716144437' style='width:100;height:63' class='attach' width="100" height="63" alt="7.jpg" /></a>
</li>
<li class=''>
<a class='resized_img' rel='lightbox[10036155]' id='ipb-attach-url-1914-0-12418700-1716144437' href="/discuss/uploads/monthly_03_2008/post-9807-1206026209.jpg" title="8.jpg - Size: 593.21KB, Downloads: 713"><img itemprop="image" src="/discuss/uploads/monthly_03_2008/post-9807-1206026209_thumb.jpg" id='ipb-attach-img-1914-0-12418700-1716144437' style='width:100;height:63' class='attach' width="100" height="63" alt="8.jpg" /></a>
</li>
<li class=''>
<a class='resized_img' rel='lightbox[10036155]' id='ipb-attach-url-1915-0-12423700-1716144437' href="/discuss/uploads/monthly_03_2008/post-9807-1206026215.jpg" title="legend.jpg - Size: 54.04KB, Downloads: 650"><img itemprop="image" src="/discuss/uploads/monthly_03_2008/post-9807-1206026215_thumb.jpg" id='ipb-attach-img-1915-0-12423700-1716144437' style='width:100;height:36' class='attach' width="100" height="36" alt="legend.jpg" /></a>
</li>
</ul>
</div>]]></description>
<pubDate>Sat, 14 Jan 2023 08:43:03 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/29793-wireless-wep-key-cracking/</guid>
</item>
<item>
<title>A small gfx engine with fireworks</title>
<link>http://www.rohitab.com/discuss/topic/55614-a-small-gfx-engine-with-fireworks/</link>
<description><![CDATA[Hello! 
It's been a long time my friends but hopefully some of you old-timer's still lurking around here.  <img src='http://www.rohitab.com/discuss/public/style_emoticons/default/thumbsup.gif' class='bbc_emoticon' alt=':thumbsup:' />
Just recently I browsed through this forum, re-read some of my old posts and topics and figured I might as well post something for old times sake.
 
Attached to this post is a small and simple graphics engine for software rendering I wrote a long time ago, there's some fireworks and some very basic reflections to look at.
For those interested in getting into some graphics development, it could be a useful resource.
 
Happy coding!
 
Screenshot
<a class='resized_img' rel='lightbox[10182447]' id='ipb-attach-url-5191-0-13123800-1716144437' href="/discuss/uploads/monthly_10_2022/post-19354-0-47479600-1665510092.png" title="gfxeEngine.png - Size: 218.17KB, Downloads: 95"><img itemprop="image" src="/discuss/uploads/monthly_10_2022/post-19354-0-47479600-1665510092_thumb.png" id='ipb-attach-img-5191-0-13123800-1716144437' style='width:100;height:73' class='attach' width="100" height="73" alt="gfxeEngine.png" /></a>

 
<a href="http://www.rohitab.com/discuss/index.php?app=core&module=attach&section=attach&attach_id=5193" title="Download attachment"><img src="http://www.rohitab.com/discuss/public/style_extra/mime_types/zip.gif" alt="Attached File" /></a>
 <a href="http://www.rohitab.com/discuss/index.php?app=core&module=attach&section=attach&attach_id=5193" title="Download attachment">gfxEngine.zip</a>   206.3KB
  395 downloads
<div id='attach_wrap' class='clearfix'>
<h4>Attached Files</h4>
<ul>
<li class='attachment'>
<a href="http://www.rohitab.com/discuss/index.php?app=core&module=attach&section=attach&attach_id=5192" title="Download attachment"><img src="http://www.rohitab.com/discuss/public/style_extra/mime_types/zip.gif" alt="Attached File" /></a>
 <a href="http://www.rohitab.com/discuss/index.php?app=core&module=attach&section=attach&attach_id=5192" title="Download attachment">gfxEngine.zip</a>   195.21KB
  419 downloads
</li>
</ul>
</div>]]></description>
<pubDate>Sat, 12 Nov 2022 01:46:09 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/55614-a-small-gfx-engine-with-fireworks/</guid>
</item>
<item>
<title>What you Listened today, Megathread</title>
<link>http://www.rohitab.com/discuss/topic/42296-what-you-listened-today-megathread/</link>
<description><![CDATA[Let's start a thread for posting our daily picks of music.
 
 
I'll start it off with some
 
Vials of Wrath
 
<iframe id="ytplayer" class="EmbeddedVideo" type="text/html" width="640" height="390" src="http://youtube.com/embed/B7pkYFwZcD8?html5=1&fs=1" frameborder="0" allowfullscreen webkitallowfullscreen /></iframe>
]]></description>
<pubDate>Thu, 21 Apr 2022 15:56:12 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/42296-what-you-listened-today-megathread/</guid>
</item>
<item>
<title><![CDATA[Can't Post?]]></title>
<link>http://www.rohitab.com/discuss/topic/8249-cant-post/</link>
<description><![CDATA[Some members seem to not be able to post, they can post in the "BOSS" Section but cant post/topic any where else, if you have this problem this SHOULD work: Clear all your cookies and temp files I believe there is some thing wrong with the cookie script, if you have this problem and still isnt fixed, email <a href='mailto:bunny@dumbtech.com' class='bbc_url' title='External link' rel='nofollow external'>bunny@dumbtech.com</a> or <a href='mailto:mott@secure-security.com' class='bbc_url' title='External link' rel='nofollow external'>mott@secure-security.com</a>]]></description>
<pubDate>Thu, 13 Jan 2022 14:20:28 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/8249-cant-post/</guid>
</item>
<item>
<title>hello</title>
<link>http://www.rohitab.com/discuss/topic/44224-hello/</link>
<description><![CDATA[<div>Hello Everyone.</div>
<div>I am here to introduce myself.</div>
<div>I am from India.I love exploring about new things,gaining knowledge,Uhani I am the explorer of Knowledge.</div>
<div>Waiting for someone to welcome me.</div>
<div> </div>
<div> </div>
<div>Regards,</div>
<div>Ohani</div>
<div> </div>
<div> </div>
<div><a href='http://www.admissioninfo.co.in/bms-college-of-engineering.html' class='bbc_url' title='External link' rel='nofollow external'>bms college of engineering management quota admission</a><a href='http://www.admissioninfo.co.in/bms-college-of-engineering.html' class='bbc_url' title='External link' rel='nofollow external'>bms college of engineering direct admission</a><a href='http://www.admissioninfo.co.in/new-horizon-college-of-engineering.html' class='bbc_url' title='External link' rel='nofollow external'>New Horizon college of Engineering  Admission</a><a href='http://www.admissioninfo.co.in/sir-mvit-m-visvesvaraya-institute-of-technology-bangalore-b-e-mba-mca-m-tech.html' class='bbc_url' title='External link' rel='nofollow external'>Sir M Visvesvaraya Institute of Technology Admission</a><a href='http://www.admissioninfo.co.in/rv-college-of-engineering.html' class='bbc_url' title='External link' rel='nofollow external'>RV College of Engineering Direct Admission</a></div>]]></description>
<pubDate>Tue, 11 Jan 2022 07:39:16 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/44224-hello/</guid>
</item>
<item>
<title><![CDATA[I've waited weeks for my post to show up]]></title>
<link>http://www.rohitab.com/discuss/topic/44591-ive-waited-weeks-for-my-post-to-show-up/</link>
<description><![CDATA[Like for real, weeks. if you dont have any moderators to approve the posts, at least remove the restriction. This is a good way to make your forum die.
]]></description>
<pubDate>Sat, 08 Jan 2022 18:55:45 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/44591-ive-waited-weeks-for-my-post-to-show-up/</guid>
</item>
<item>
<title>How to play with virtual memory? write to randomized places?</title>
<link>http://www.rohitab.com/discuss/topic/42575-how-to-play-with-virtual-memory-write-to-randomized-places/</link>
<description><![CDATA[Hello rohitabs,
 
I am very interested in playing with windows processes' memory but I don't know enough about the windows API. Firstly I would like to know how to map virtual memory, I don't know if this is really useful, but I would like to use that knowledge to map the memory and create memory dumps (Even I know of the existence of minidumps) probably using ReadProcessMemory() ?
 
Also, there's something I can't understand completely. If I found the address of a value which changes in every boot (because of ASLR) how would I do to change it from my program? Thanks <img src='http://www.rohitab.com/discuss/public/style_emoticons/default/thumbsup.gif' class='bbc_emoticon' alt=':thumbsup:' />
 
Regards,
Pedro.
]]></description>
<pubDate>Sat, 08 Jan 2022 18:54:47 +0000</pubDate>
<guid>http://www.rohitab.com/discuss/topic/42575-how-to-play-with-virtual-memory-write-to-randomized-places/</guid>
</item>
</channel>
</rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

Download the "valid RSS" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src attribute if necessary):

<a href="http://www.feedvalidator.org/check.cgi?url=http%3A//www.rohitab.com/discuss/rss/forums/1-new-topics/"><img src="valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.rohitab.com/discuss/rss/forums/1-new-topics/

Home · About · News · Docs · Terms