Reply to thread

Message

<blockquote data-quote="ForgottenSeer 97327" data-source="post: 1029902">[USER=74969]@plat[/USER], [USER=80838]@Jan Willy[/USER], [USER=71262]@oldschool[/USER], [USER=61892]@TairikuOkami[/USER] The link posted by Jan Willy of Kees1958 also shows an interesting tweak:Using different uBO-levels hardening in different browser profiles <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />, I had not thought af that either.I also noticed Kees1958&nbsp; used this uBO scriptlet in his most restricted profile: *##+js(noeval) Blocking unsafe eval also limits the risk of XSS attacks, combined with the extra checks Edge can perform by disabling the Javascript Just in Time interpreter, this should block 99,9999% of all&nbsp; javascript attacks (99,9999% because in security 100% does not exist)</blockquote>

[QUOTE="ForgottenSeer 97327, post: 1029902"] [USER=74969]@plat[/USER], [USER=80838]@Jan Willy[/USER], [USER=71262]@oldschool[/USER], [USER=61892]@TairikuOkami[/USER] The link posted by Jan Willy of Kees1958 also shows an interesting tweak: Using different uBO-levels hardening in different browser profiles (y), I had not thought af that either. I also noticed Kees1958 used this uBO scriptlet in his most restricted profile: *##+js(noeval) Blocking unsafe eval also limits the risk of XSS attacks, combined with the extra checks Edge can perform by disabling the Javascript Just in Time interpreter, this should block 99,9999% of all javascript attacks (99,9999% because in security 100% does not exist) [/QUOTE]

Verification