Strong mode on reference proxy protection breaks module

[ElektroKill]

Hello,

After applying reference proxy on strong mode onto a module using the latest build (0b7d281) the output module no longer runs.

Thanks in advance.

[mkaring]

Are we talking about the master branch here?

[ElektroKill]

Yes, i faced this issue with latest build(dnlib nugget) from master branch

[XenocodeRCE]

@mkaring still no fixes ? This is considered as a major flaw since your changes broke one of ConfuserEx bests protection so far

[xmoer]

Me, too. But when "encoding = x86" protection is work. In strong mode, both "normal" and "expression" cause errors.

[mkaring]

I can reproduce the error. It's some random error that hits in about 50% of the runs.

[mkaring]

I got this mess sorted out. A new build that contains the fix for this specific issue is available here. It would be great if the fix could be verified in an actually affected project. The unit test I created is very simple.

[ElektroKill]

Hello, I tested the build with an application that targets .NET 2.0 and it crashes on startup. I tried with the same application but with the target framework set to .NET 4.0 and it worked flawlessly. I think there is still a problem here.

I used the following configuration:

<protection id="ref proxy">
  <argument name="mode" value="strong" />
  <argument name="encoding" value="expression" />
</protection>

Here are both of the files I used for testing:
(NOTE: I didn't create this application, it's just some file I had laying around)
testsamples.zip

Hypothesis:
After processing the .NET 2.0 file has two mscorlib references, one pointing to .NET 2.0 and the other one to .NET 4.0.

[mkaring]

That is an unrelated error. This problem is caused by the changes for #144.

[mkaring]

Not done yet.