Rigo

Yeah, just want to validate that the prior ones are actually also executing as expected. Because truth be told on sandsifter I've never actually seen a processor execute into that...

Yes this is what I will have to do. We can simply extend the BLACKLIST array in injector.c Most of these instructions should only ever be called by the operating...

This repo purely exists here for legacy(archival) purposes but I will have a look at the issue. There are likely a few python2 to python3 conversion issues and possibly broken...

I never really did make a windows build. It was largely written in Python 2 and for Mac/Linux But since it's just Python it can be ported to Windows relatively...

Thanks for posting this. I will have a look at it.

I just noticed this issue. Is this still occurring on the current version too? I haven't seen it occur myself yet, but there are a number of other problems.

Sorry I was talking about my fork which fixes a number of issues: https://github.com/rigred/sandsifter

Thanks for telling me. Silly me forgot to enable issues. I've just noticed it and enabled that.

I simply compiled the injector as static which solved the problem of ``` /usr/bin/ld: injector.o: relocation R_X86_64_32S against undefined symbol `dummy_stack' can not be used when making a shared object;...

As far as I know, the apparmor logs are somewhat of an issue resulting from the fact that's surprisingly convoluted to deny specific apparmor messages silently in the autogenerated snap...