cracknetproject Discussions Rss Feed

New Post: Non-top level windows?

dawmail333 — Sun, 30 Jan 2011 09:54:22 GMT

I'm trying to nosy into an app, but it's not at the top level, so it doesn't show up.

How can I modify the source to show ALL valid windows?

The program I'm attempting to nosy through is a .Net 2.0 app running on some tripped out UI frameworks.

Thanks!

New Post: .NET 4?

legrit — Wed, 07 Jul 2010 18:08:23 GMT

Does Crack.Net work with .NET4 apps?

It won't load my WPF app targeting .NET 4.

I tryed compiling the sample CrackNET.WpfTestApp targeting .NET 4 and it won't load either. It work when I compile it targetin 3.5

New Post: Attempted to read or write protected memory. This is often an indication that other memory is corrupt

JoshSmithonWpf — Sun, 13 Sep 2009 16:11:13 GMT

If you don't mind, please share some tips here that explain how you got it to work on your machine (so that others with the same problem can know the fix). Thanks!

New Post: Attempted to read or write protected memory. This is often an indication that other memory is corrupt

michaelsync — Sun, 13 Sep 2009 08:58:06 GMT

I have gone throught your code and found that the most of codes are being re-used from Snoop. So, I already found the way to make Snoop work on my machine so no issue for now. Thanks a lot for your reply, Josh.

New Post: Attempted to read or write protected memory. This is often an indication that other memory is corrupt

michaelsync — Sun, 13 Sep 2009 05:41:14 GMT

I'm using .NET 3.5.

I'm using Windows 2008 R2 64 bits as main OS and hyper-V-ing the Vista Business Edition (64 bits) to run VS 2008.

New Post: Attempted to read or write protected memory. This is often an indication that other memory is corrupt

JoshSmithonWpf — Sun, 13 Sep 2009 00:32:56 GMT

I've never seen that before. Does it only occur for one application, or for any cracked app?

What version of the .NET Framework is the application using?

New Post: Attempted to read or write protected memory. This is often an indication that other memory is corrupt

michaelsync — Sat, 12 Sep 2009 18:07:40 GMT

Hi Josh,

I'm getting this error when I click "Refresh" button twice.

System.AccessViolationException was unhandled
Message="Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
Source="mscorlib"
InnerException:

Class Name : MainWindow
Line : 133 (foreach - windows)

New Post: How to compile for 64-bit?

cplotts — Mon, 15 Jun 2009 15:48:19 GMT

There wasn't a 'x64' Solution Platform in the code that I downloaded (Changeset 20231) ... I tried to make one myself ... but things went bad quickly. In particular, there didn't seem to be a 64-bit option for the ManagedInjector project.

Should I download a different set of code ... or something?

New Post: How to compile for 64-bit?

JoshSmithonWPF — Mon, 15 Jun 2009 15:23:03 GMT

Hi,

Have you set the Active Solution Platform to 'x64'? If not, to do that you go to the Build menu, then Configuration Manager, and set it in the dialog window that pops up.

If you already are using that setting, I'm not sure why it isn't working...

Josh

New Post: How to compile for 64-bit?

cplotts — Mon, 15 Jun 2009 15:04:06 GMT

Trying to compile and run the source code for my Windows 7 64-bit platform ... and it dies when I launch the executable. However, when I download the binaries ... those work fine.

Are there any tricks to building it on a 64-bit platform?

New Post: Crack + Snoop

aquaseal — Tue, 07 Apr 2009 00:04:29 GMT

Thanks guys! That's great to know!!! Can't wait for the next version!

New Post: Crack + Snoop

cplotts — Mon, 06 Apr 2009 23:14:26 GMT

aquaseal: If you look at the following post (http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/b99f3db7-540c-43f4-8051-69d2d51a78bc) you will see how Mark fixed property editing in the latest version of Snoop.

And I agree, I would rather use Crack (oh, that is so fun to say).

New Post: Crack + Snoop

JoshSmithonWPF — Mon, 06 Apr 2009 23:13:29 GMT

Hey aquaseal, you're in luck. Part of the next planned version of Crack.NET is to have the ability to edit properties in Memory Explorer. I think it will be something like what Mole exposes for property editing. We'll see how it goes...

New Post: Crack + Snoop

aquaseal — Mon, 06 Apr 2009 22:55:44 GMT

I love this idea! I dislike how the current state of snoop has broken the property changing ability! But alas, I use an older version of snoop on a near daily basis, and if crack implemented this capability then I would surely use crack all the time!!! (the green alien with a blinking eye application, not some other reference).

thanks for all your hard work josh, it is certainly appreciated!

New Post: Crack + Snoop

JoshSmithonWPF — Mon, 06 Apr 2009 19:04:31 GMT

I was thinking about having a "zoom slider" to change the number of elements in the TreeView. Mouse wheel support is a cool idea, too. Thanks, I'll probably add that in. ;)

Your poem resonates with me. I want Crack.NET to be The Tool for WPF devs. I have so many features in mind for it, but adding in element tree sniffing is definitely the highest priority work item.

New Post: Crack + Snoop

cplotts — Mon, 06 Apr 2009 18:59:09 GMT

Oh, I'm not pushing for Kharitonov's solution ... although I do like that he fixed the limitation in Snoop ...

From what I understand, I already like your solution. :) What would be interesting and fun would be some neat way from design standpoint to change how much of the element tree you are displaying ... maybe something akin to zoom. Who knows, maybe you could hook in the mouse wheel ... that would be a slick way to 'zoom' the element tree larger and smaller.

One tool to rule them all,
One tool to find bugs,
One tool to bring them all,
And in the darkness squish them.

:)

New Post: Crack + Snoop

JoshSmithonWPF — Mon, 06 Apr 2009 18:41:52 GMT

Kharitonov's solution is fine, but I didn't like the user experience it creates. I'm thinking more and more that limiting the number of elements in the TreeView is the ideal solution. Once I get a prototype working, I'll let you know and hopefully you'll agree with me.

New Post: Crack + Snoop

cplotts — Mon, 06 Apr 2009 18:38:42 GMT

Again, thanks for the prompt reply ... and, yes, that's right ... good point ... in fact, I know that Mark Kharitonov has previously contacted you about an improvement he has made in Snoop (and was suggesting for Crack.NET) due to the nesting limitation.

New Post: Crack + Snoop

JoshSmithonWPF — Mon, 06 Apr 2009 18:27:22 GMT

:) Thanks for the feedback!

Part of the reason I need to limit the size of the Element TreeView (aside from having it be too heavy), is that WPF has an artificial limitation where you cannot nest elements more than ~255 levels deep. Since TreeViewItems nest within each other, this limitation can become a problem (in rare scenarios). Limiting the number of descendants/ancestors allows me to present a lightweight, safe view of the element tree.

Yeah, the blinking alien is the bomb!

New Post: Crack + Snoop

cplotts — Mon, 06 Apr 2009 18:19:41 GMT

Saw your post (http://groups.google.com/group/wpf-disciples/browse_thread/thread/4f2210616a8ab501/03cb12859b4b9386?show_docid=03cb12859b4b9386) in the WPF Disciples group ... and wanted to thumbs up the idea.

I would love the Ctrl-Shift behavior in Crack.NET.

I don't think you need to limit how much the user can see of the element tree ... but if you do, make sure it is configurable. Given that though, I like the idea. It would just be icing on the cake.

Another thing I like about Snoop is seeing the visual that I'm 'cracking' or 'snooping'.

By the way, love the blinking alien. It is just pure coolness. I know that it is just a simple flip book animation, but it is still the bomb.