Reply to thread

Message

<blockquote data-quote="LeMinhThanh" data-source="post: 987479" data-attributes="member: 86954">Hi!LMT AntiMalware 6.1.4 released.Changelog:<ul>
<li data-xf-list-type="ul">Fixed: The software might crash when selecting a folder in the Folder Protection feature, when activating the Anti Keylogger feature, when disabling Microphone Guard.</li>
<li data-xf-list-type="ul">Updated to .NET Framework 4.8.</li>
<li data-xf-list-type="ul">A few other minor updates.</li>
</ul>Homepage: <a href="https://www.leminhthanh.me/antimalware" target="_blank">LMT AntiMalware</a>----------------------------------About the issue between Web Protection and Cloudflare, there is an issue when LMT AntiMalware handles the header of requests from the browser, leading Cloudflare to think the user is a spam bot. Working with headers gave me so much headache that I decided not to deal with this anymore <img class="smilie smilie--emoji" loading="lazy" alt="😂" title="Face with tears of joy&nbsp; &nbsp; :joy:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f602.png" data-shortname=":joy:" />I think the best way is to create a browser extension, instead of using HTTPS Scanning. Maybe I will add it in the next version <img class="smilie smilie--emoji" loading="lazy" alt="😁" title="Beaming face with smiling eyes&nbsp; &nbsp; :grin:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f601.png" data-shortname=":grin:" /></blockquote>

[QUOTE="LeMinhThanh, post: 987479, member: 86954"] Hi! LMT AntiMalware 6.1.4 released. Changelog: [LIST] [*]Fixed: The software might crash when selecting a folder in the Folder Protection feature, when activating the Anti Keylogger feature, when disabling Microphone Guard. [*]Updated to .NET Framework 4.8. [*]A few other minor updates. [/LIST] Homepage: [URL='https://www.leminhthanh.me/antimalware']LMT AntiMalware[/URL] ---------------------------------- About the issue between Web Protection and Cloudflare, there is an issue when LMT AntiMalware handles the header of requests from the browser, leading Cloudflare to think the user is a spam bot. Working with headers gave me so much headache that I decided not to deal with this anymore 😂 I think the best way is to create a browser extension, instead of using HTTPS Scanning. Maybe I will add it in the next version 😁 [/QUOTE]

Verification