Page 1 of 5
VMProtect for .NET released
Posted: Sat Jul 20, 2019 5:52 am
by Admin
VMProtectDemo (build 1167):
http://vmpsoft.com/files/VMProtectDemo.exe
P.S. Mixed assemblies are not supported.
Re: VMProtect for .NET (сoming soon)
Posted: Tue Jul 23, 2019 11:45 pm
by newmecha
I downloaded the demo from above however it is not the 1125 build.
If I were purchase a new license today, would I be eligible for the update that includes the dotnet protection ? Or is that going to be a separate add on ? Is there any ETA on this as well ?
Re: VMProtect for .NET (сoming soon)
Posted: Thu Jul 25, 2019 4:37 am
by Admin
Please download the demo again (now it's the 1125 build).
P.S. The full version with the .NET support isn't available.
Re: VMProtect for .NET (сoming soon)
Posted: Thu Jul 25, 2019 1:22 pm
by Mecanik
AMAZING! This is something I have been waiting for a very long time
Re: VMProtect for .NET released
Posted: Sat Aug 03, 2019 11:52 am
by Admin
Re: VMProtect for .NET released
Posted: Sat Aug 03, 2019 8:24 pm
by Lafko
Where i can see .net SDK examples?
Re: VMProtect for .NET released
Posted: Sat Aug 03, 2019 8:32 pm
by Admin
Look at this:
C:\Users\Public\Documents\VMProtect\Code Markers\Net
C:\Users\Public\Documents\VMProtect\Licensing\Net
Re: VMProtect for .NET released
Posted: Sat Aug 03, 2019 9:09 pm
by Lafko
Даже если я пытаюсь защитить приложение из примера C:\Users\Public\Documents\VMProtect\Code Markers\Net\bin\Project1.exe VMProtect Professional зависает на моменте сохранения .net, версия VMProtect 1130. Любая функция SDK вызывает проблему зависания VMProtect в момент сохранения.
Re: VMProtect for .NET released
Posted: Sat Aug 03, 2019 9:20 pm
by Admin
VMProtect for .NET БАГИ
Posted: Sat Aug 03, 2019 9:31 pm
by Lafko
Тут я напишу все те баги которые я смог найти в VMProtect for .NET версии 1130. Я создал стандартное пустое приложение .net Forms версии 4.0
Добавил функции:
1. "Защита памяти";
2. "Упаковать выходной файл";
3. "Удалять отладочную информацию";
4. "Водяной знак".
1. Добавил функцию "Отладчик" User-mode или User-mode + Kernel-mode.
1. Добавил функцию Отладчик User-mode.
1. Добавил функцию "Инструменты виртуализации".
Code: Select all
После закрытия приложение выдаёт ошибку. Ошибку вызывает Dispose(bool)
1. Оставил рабочие функции и добавил все "Функции для защиты";
Code: Select all
Зависает VMProtect на моменте создании при попытки использование методов из библиотеки VMProtect.SDK.dll
Файл с которым я работал
https://yadi.sk/d/ldqEG5YR_St0Ug
Re: VMProtect for .NET released
Posted: Sat Aug 03, 2019 9:52 pm
by Lafko
/del
Re: VMProtect for .NET released
Posted: Sun Aug 04, 2019 6:28 am
by Lafko
После защиты 1031 в .net перестаёт работать соединение с сервером
Соединение не происходит даже если отключить все функции защиты и отключит SDK
Использую .net 4.7.2
Code: Select all
public static string CheckForInternetConnection()
{
Version version = Assembly.GetEntryAssembly().GetName().Version;
try
{
using (var client = new WebClient())
using (client.OpenRead("https://***.ru/" + version + ".php"))
{
return "https://***.ru/" + version + ".php";
}
}
catch
{
try
{
using (var client = new WebClient())
using (client.OpenRead("https://***.ru/" + version + ".php"))
{
return "https://***.ru/" + version + ".php";
}
}
catch
{
try
{
using (var client = new WebClient())
using (client.OpenRead("https://***.ru/" + version + ".php"))
{
return "https://***.ru/" + version + ".php";
}
}
catch (Exception ex)
{
MessageBox.Show(ex.ToString());
Process.GetCurrentProcess().Kill();
return "";
}
}
}
}
Re: VMProtect for .NET released
Posted: Sun Aug 04, 2019 9:15 am
by zds
зависает на этапе компиляции на 7%
Re: VMProtect for .NET released
Posted: Sun Aug 04, 2019 2:36 pm
by Admin
После защиты 1031 в .net перестаёт работать соединение с сервером
Присылайте простейший пример.
Re: VMProtect for .NET released
Posted: Sun Aug 04, 2019 4:06 pm
by 3dsboy08
While the new .NET mode works quite well, there is quite a few suggestions I have:
- Renaming: I don't want to have to run my executable through another obfuscator before VMProtect. Class/method/field renaming is standard on even free .NET obfuscators and VMProtect should have it too. (maybe have it be apart of the 'Strip debug information' option?)
- String encryption by default: Most .NET protectors allow you to have an option to protect all strings in the executable. Would be a nice convenience feature instead of doing SDK.DecryptString for every single string you use.
- Native VMs: While probably quite hard to implement, having a native VM for .NET CIL would make the protection much stronger and also differentiate you guys from the rest of .NET protectors. (the only other product that does this costs 2000$ and having that would make you guys the top of the line for .NET right now)