David Heffernan

Sounds like the classic OOP trap of trying to solve all problems with inheritance. Good OOP programmers hardly ever use inheritance to solve problems.

I mean that this thing is named as though it is an affinity mask. And on Windows that makes it pointer sized. So, NativeUInt.

Affinity masks for pointer sized.

Don't try to use more than 48 threads in that case

If the hacker gets the program, and there is a hard coded key in the program, then it's trivial to hack.

Is it 96 cpus, or 48 with 2 threads per core? Is the memory NUMA?

What do you think this does?

Seems like it's not really worthwhile then....

So you don't mind if the security is easily circumvented?

Although do anticipate that any hacker will be able to see the plain text when you decrypt in memory.

So often this is caused by a defect in your code. You supply an argument that is invalid. Perhaps an object that has already been destroyed. So full fastmm4 debug is useful. You would debug this by trying to create a minimal example that reproduces the issue. That's the starting point.

No reason at all to suspect that multithreading is the issue here. You aren't likely to get good leads from people making random guesses. Hard debugging is the way forward.

The WOL packet is also being routed it would seem.

One of many possible explanations, but far from the only one.

How many ports do you have open on your public facing router?