HadesMem - A Windows Memory Hacking Library for C++ menu

Shout-Out

User Tag List

Page 6 of 6 FirstFirst ... 23456
Results 76 to 82 of 82
  1. #76
    Cypher's Avatar Kynox's Sister's Pimp
    Reputation
    1356
    Join Date
    Apr 2006
    Posts
    5,368
    Thanks G/R
    0/4
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by GliderPro View Post
    HadesMem has changed a lot since I worked with it last. Here are the steps I had to perform to get it to build completely.

    1) Get boost
    2) Get DirectX SDK
    3) Get WTL
    4) Edit the Microsoft.Cpp.Win32.user/Microsoft.Cpp.x64.user property sheets and add the include and library paths from the libraries above to the VC++ Directories property.
    5) Disable signing of the Hades-AD project. I tried creating a new key file but I kept getting "access denied".

    EDIT: For step 5 above you can create a new key if you start VS2010 with elevated privileges.
    Correct. I should probably write up some instructions somewhere, lol.

    Come to think of it, I could make the process a little easier if I bundled WTL. It's under a license that permits that I think... I'll check tomorrow.

    As for disabling the signing of Hades-AD, that will only work if you don't use the .NET layer of the injected portion of Hades.

    HadesMem - A Windows Memory Hacking Library for C++
  2. #77
    Apoc's Avatar Angry Penguin
    Reputation
    1387
    Join Date
    Jan 2008
    Posts
    2,750
    Thanks G/R
    0/12
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by Cypher View Post
    Correct. I should probably write up some instructions somewhere, lol.

    Come to think of it, I could make the process a little easier if I bundled WTL. It's under a license that permits that I think... I'll check tomorrow.

    As for disabling the signing of Hades-AD, that will only work if you don't use the .NET layer of the injected portion of Hades.
    You probably shouldn't be signing Hades-AD by default anyway. Include the option though.

    Signing the assembly won't do you much good if you're not inserting it into the GAC so you can load it from anywhere. (Definitely won't stop people from ripping it)

  3. #78
    adaephon's Avatar Active Member
    Reputation
    76
    Join Date
    May 2009
    Posts
    167
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by Apoc View Post

    Signing the assembly won't do you much good if you're not inserting it into the GAC so you can load it from anywhere.
    He is inserting it into the GAC so he can load it from anywhere

  4. #79
    Cypher's Avatar Kynox's Sister's Pimp
    Reputation
    1356
    Join Date
    Apr 2006
    Posts
    5,368
    Thanks G/R
    0/4
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Originally Posted by Apoc View Post


    You probably shouldn't be signing Hades-AD by default anyway. Include the option though.

    Signing the assembly won't do you much good if you're not inserting it into the GAC so you can load it from anywhere. (Definitely won't stop people from ripping it)
    I do insert it into the GAC. I use a build event to do that when it's compiled. I also provide a batch script in the Util directory to do it.

    Also, did you REALLY think that I'd think signing it would 'protect' it from rippers somehow? Lol.


    ---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------

    Oh, one more thing.

    To compile Hades properly you'll need the Windows 7 SDK available here:
    Download details: Microsoft Windows SDK 7.1

    This is NOT the one that comes with VS2010.

    I'll write up some proper compilation and setup instructions soon. I'm leaving the US and going back to Australia on the 2nd of August, arriving on the 4th. So some time between the 4th and about a fortnight from then I should have some instructions up (with pretty pictures etc for people like Apoc ).

  5. #80
    Cypher's Avatar Kynox's Sister's Pimp
    Reputation
    1356
    Join Date
    Apr 2006
    Posts
    5,368
    Thanks G/R
    0/4
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Improved a ****load of stuff since my last post. Can't be bothered to explain it all here, check my blog (there's a few posts on what I've been working on in HadesMem) and the subversion log (on the project page) for more info.

  6. #81
    GliderPro's Avatar Member
    Reputation
    -1
    Join Date
    Mar 2009
    Posts
    93
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Started messing around with HadesMem again. I was able to get it working with Stackless Python 2.7. The biggest pain was getting Boost to accept an extra include path for the Python header files.

    I did have to make one change to the sandbox application to get it to run though. I inserted "Py_NoSiteFlag = 1;" before the Py_Initialize() call. Without it the initialization would fail because I'm working off a build tree for Python instead of an official install; i.e. I don't have site.py in the Python path.



    Do you know if boost:: python can dynamically bind to a Python DLL (in the injected process) or does it require an import library to link against?

  7. #82
    GliderPro's Avatar Member
    Reputation
    -1
    Join Date
    Mar 2009
    Posts
    93
    Thanks G/R
    0/0
    Trade Feedback
    0 (0%)
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Here is a Visual Studio project to build HadesMem v2. Just drop it in the build directory and go. I know it does the same thing as the batch files but batch files annoy me. The file would be a lot smaller if Visual Studio didn't require so much extra crap in it's MSBuild projects.

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
      <ItemGroup Label="ProjectConfigurations">
        <ProjectConfiguration Include="Debug|Win32">
          <Configuration>Debug</Configuration>
          <Platform>Win32</Platform>
        </ProjectConfiguration>
        <ProjectConfiguration Include="Debug|x64">
          <Configuration>Debug</Configuration>
          <Platform>x64</Platform>
        </ProjectConfiguration>
        <ProjectConfiguration Include="Release|Win32">
          <Configuration>Release</Configuration>
          <Platform>Win32</Platform>
        </ProjectConfiguration>
        <ProjectConfiguration Include="Release|x64">
          <Configuration>Release</Configuration>
          <Platform>x64</Platform>
        </ProjectConfiguration>
      </ItemGroup>
      <PropertyGroup Label="Globals">
        <ProjectGuid>{6DA36AB6-B388-4BB9-BC4D-5B85AD3B37D0}</ProjectGuid>
        <Keyword>MakeFileProj</Keyword>
      </PropertyGroup>
      <Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
      <PropertyGroup>
        <ConfigurationType>Makefile</ConfigurationType>
        <PlatformToolset>v110</PlatformToolset>
      </PropertyGroup>
      <PropertyGroup Condition="'$(Platform)'=='Win32'">
        <address-model>32</address-model>
      </PropertyGroup>
      <PropertyGroup Condition="'$(Platform)'=='x64'">
        <address-model>64</address-model>
      </PropertyGroup>
      <Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
      <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="Exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" />
      <PropertyGroup>
        <NMakeBuildCommandLine>cd $(MSBuildProjectDirectory)\.. &amp; %BOOST_ROOT%\b2 -j %NUMBER_OF_PROCESSORS% toolset=msvc address-model=$(address-model) $(Configuration.ToLower())</NMakeBuildCommandLine>
        <NMakeCleanCommandLine>cd $(MSBuildProjectDirectory)\.. &amp; %BOOST_ROOT%\b2 -j %NUMBER_OF_PROCESSORS% toolset=msvc address-model=$(address-model) --clean $(Configuration.ToLower())</NMakeCleanCommandLine>
        <NMakeReBuildCommandLine>cd $(MSBuildProjectDirectory)\.. &amp; %BOOST_ROOT%\b2 -j %NUMBER_OF_PROCESSORS% toolset=msvc address-model=$(address-model) -a $(Configuration.ToLower())</NMakeReBuildCommandLine>
        <NMakePreprocessorDefinitions>WIN32;_DEBUG;$(NMakePreprocessorDefinitions)</NMakePreprocessorDefinitions>
      </PropertyGroup>
      <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
    </Project>

Page 6 of 6 FirstFirst ... 23456

Similar Threads

  1. Memory Hacking Library List
    By Cypher in forum WoW Memory Editing
    Replies: 27
    Last Post: 08-30-2021, 07:07 PM
  2. [Release] SHInject - A small Memory Editing library for 3.3.5:12340
    By Blackplayer27 in forum WoW Memory Editing
    Replies: 4
    Last Post: 09-22-2020, 06:06 PM
  3. [source][C++]Blackbone - windows memory hacking library
    By DarthTon in forum WoW Memory Editing
    Replies: 15
    Last Post: 02-21-2015, 07:39 AM
  4. [Release] [D] Hydra - Memory manipulation library for the D language
    By Hybro in forum WoW Memory Editing
    Replies: 1
    Last Post: 09-01-2013, 11:18 AM
  5. [C#] NWOHack - An open-source in-process memory hack for NeverWinter
    By Jadd in forum Neverwinter Bots and Programs
    Replies: 23
    Last Post: 06-28-2013, 10:01 AM
All times are GMT -5. The time now is 03:22 AM. Powered by vBulletin® Version 4.2.3
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved. User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search