Joshua de Wet comments

Results 7 comments of


                                            Joshua de Wet

Flaw with the way API set resolution is handled

@TheWover I can't think of one off the top of my head but you could take a look at a few of the core system DLL's i.e. kernel32, kernelbase etc....

WOW64 Stub for D/Invoke

@FuzzySecurity A manual reimplementation shouldn't be as complicated as mentioned above. If you follow `Wow64SystemServiceCall` you will notice it's just a chain of calls into an eventual transition back into...

Elevation - UAC

Correct me if I'm wrong here but I believe UAC elevation is supposed to be handled by the application itself via its embedded manifest?

Consider changing the inferred type of stackalloc to a Span<T> instead of a T* if using a safe context

The above comments make sense and I agree that returning different types between unsafe and safe probably isn't the best idea, however, as mentioned by @CyrusNajmabadi, maybe changing stackalloc to...

Consider changing the inferred type of stackalloc to a Span<T> instead of a T* if using a safe context

@tannergooding I agree with what you are saying, however, I still don't find it great to have a type infer to a pointer in a safe context. From my understanding,...

Consider changing the inferred type of stackalloc to a Span<T> instead of a T* if using a safe context

@Joe4evr does it not make more sense then to return a `Span` for both cases as you can easily get a pointer to the first element in a `Span` if...

Only load PE imports if they are not already loaded

@TheWover a simpler solution is just to query the module list everytime you are thinking about doing a load and if the module is already loaded call `LdrAddRefDll`. You could...