Index
> Projects and Ideas > packet editor like wpepro |
| Author |
|
|
revolution 10 Apr 2015, 05:02
For which OS?
Current versions of Windows would require a signed driver to access the data stream. |
|||
10 Apr 2015, 05:02 |
|
|
KevinN 10 Apr 2015, 05:05
Windows - Windows 7,8,8.1,10 yea..Guess that's why WPE doesn't work anymore, huh?
 |
|||
|
10 Apr 2015, 05:05 |
|
|
HaHaAnonymous 10 Apr 2015, 05:10
Quote:
It works if you set up like this: "Compatibility mode WinXP", "Run as Admin." It will work buggy, but will work... Last time I checked it in 2013. That is Microsoft business, let your old programs unrunable so you are forced to buy their latest version. Pure marketing strategy! |
|||
|
10 Apr 2015, 05:10 |
|
|
KevinN 10 Apr 2015, 05:17
HaHaAnonymous wrote:
Don't think it has anything to do with security issues? |
|||
|
10 Apr 2015, 05:17 |
|
|
revolution 10 Apr 2015, 05:17
HaHaAnonymous wrote: That is Microsoft business, let your old programs unrunable so you are forced to buy their latest version. Pure marketing strategy!  |
|||
|
10 Apr 2015, 05:17 |
|
|
KevinN 10 Apr 2015, 05:18
I don't wanna believe it
|
|||
|
10 Apr 2015, 05:18 |
|
|
HaHaAnonymous 10 Apr 2015, 05:21
Quote:
I will tell you why it does not work properly on Windows above XP: The last time I checked, the technique used by WPE, which was to patch the send and recv functions to intercept the parameters and read the packet being sent was changed in Windows 7, for example and the hook doesn't work properly. So it is injecting erroneous code to the process. That is last time I checked. Running as Compat. Mode Fixed the problem as I can remember... Not sure. |
|||
|
10 Apr 2015, 05:21 |
|
|
KevinN 10 Apr 2015, 05:25
I'm confused. If to succeed in something like this now requires signed drivers how does it work in XP compatible mode?
|
|||
|
10 Apr 2015, 05:25 |
|
|
HaHaAnonymous 10 Apr 2015, 05:28
Quote:
WPE has no drivers as far as I can remember. |
|||
|
10 Apr 2015, 05:28 |
|
|
KevinN 10 Apr 2015, 05:29
HaHaAnonymous wrote:
I don't recall anything like that either. Does it just hook the target program and monitor/alter/add to the winsock calls? I'm not really sure how it works/worked. |
|||
|
10 Apr 2015, 05:29 |
|
|
revolution 10 Apr 2015, 05:29
I may have erred in my assumption. Perhaps it is possible to register a system wide DLL and use that to inject/patch each process on the fly. I never realised that XP compatibility mode would permit that though.
|
|||
|
10 Apr 2015, 05:29 |
|
|
KevinN 10 Apr 2015, 05:33
revolution wrote: I may have erred in my assumption. Perhaps it is possible to register a system wide DLL and use that to inject/patch each process on the fly. I never realised that XP compatibility mode would permit that though. Hmm now I gotta redownload that old thing and take a look and see if I can "get it". |
|||
|
10 Apr 2015, 05:33 |
|
|
KevinN 10 Apr 2015, 05:34
Anyone here every recreate the functionality like it had - on XP or whatever version of windows?
|
|||
|
10 Apr 2015, 05:34 |
|
|
KevinN 10 Apr 2015, 05:38
There are two dlls in the package. SetPriv.dll and WpeSpy.dll. Found some kind of premature open source packet editor project in c# too; www.packeteditor.com
|
|||
|
10 Apr 2015, 05:38 |
|
< Last Thread | Next Thread > |
Forum Rules:
|