Reply to thread

Message

<blockquote data-quote="n8chavez" data-source="post: 993771" data-attributes="member: 90863">Well, off the top of my head I can think of one important rule parameter I&#039;d like to see.&nbsp; I use, and will&nbsp; always only use, VS with SBIE on a RAM disk.&nbsp; It woiuld be awesome to see an &quot;except&quot; rule.&nbsp; Meaning, I&#039;d like the ability to create a rule that blocks things from running on my RAM&nbsp; disk that does not have a valid signature (+ maybe even VS AI)&nbsp; Currently, I can block all things on s: (my ram drive).&nbsp; And because it&#039;s a hard rule, every thing gets blocked no matter what.&nbsp; An exception parameter allowing anything with a valid signature, but blocking everything else, would be nice.&nbsp; Make sense, or am I retarded?(I assume a little bit of column A and B <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> )</blockquote>

[QUOTE="n8chavez, post: 993771, member: 90863"] Well, off the top of my head I can think of one important rule parameter I'd like to see. I use, and will always only use, VS with SBIE on a RAM disk. It woiuld be awesome to see an "except" rule. Meaning, I'd like the ability to create a rule that blocks things from running on my RAM disk that does not have a valid signature (+ maybe even VS AI) Currently, I can block all things on s: (my ram drive). And because it's a hard rule, every thing gets blocked no matter what. An exception parameter allowing anything with a valid signature, but blocking everything else, would be nice. Make sense, or am I retarded? (I assume a little bit of column A and B :) ) [/QUOTE]

Verification