Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
General Security Discussions
Default Deny VS traditional AVs
Message
<blockquote data-quote="Libera Milanesi" data-source="post: 759301" data-attributes="member: 74385"><p>The hilarious part about all of this is that I've actually worked with engineers from AV vendors and I have friends who are currently engineers at Microsoft. You'd think I know a bit about what I'm talking about. Whether you believe me or not is irrelevant, it's the truth. I may or may not have audited parts of the Windows source code as well. We'll leave it a mystery. Spooky! Boo!</p><p></p><p>You didn't need to mention the FileSystemWatcher. It's obvious. I'm aware of the .NET Framework and your description matches it perfectly. The FileSystemWatcher even has an easier naming of the events for you, which is what you referred to. Instead of the I/O Request Packet naming used for registering callbacks in an actual Filesystem Mini-Filter.</p><p></p><p>If you don't want to listen to what I've told you and you want to shine your ego, then you can do that. My post still stands. I saw you struggling and decided to be kind enough to chime in and help everyone.</p><p></p><p>I'm not trying to look like the "best" here. The only person I see doing this is you. This is why you felt the need to point out your programming threads and that you're a "developer". Note: I only mentioned my experience after you started causing an issue, so I didn't really do what you did.</p></blockquote><p></p>
[QUOTE="Libera Milanesi, post: 759301, member: 74385"] The hilarious part about all of this is that I've actually worked with engineers from AV vendors and I have friends who are currently engineers at Microsoft. You'd think I know a bit about what I'm talking about. Whether you believe me or not is irrelevant, it's the truth. I may or may not have audited parts of the Windows source code as well. We'll leave it a mystery. Spooky! Boo! You didn't need to mention the FileSystemWatcher. It's obvious. I'm aware of the .NET Framework and your description matches it perfectly. The FileSystemWatcher even has an easier naming of the events for you, which is what you referred to. Instead of the I/O Request Packet naming used for registering callbacks in an actual Filesystem Mini-Filter. If you don't want to listen to what I've told you and you want to shine your ego, then you can do that. My post still stands. I saw you struggling and decided to be kind enough to chime in and help everyone. I'm not trying to look like the "best" here. The only person I see doing this is you. This is why you felt the need to point out your programming threads and that you're a "developer". Note: I only mentioned my experience after you started causing an issue, so I didn't really do what you did. [/QUOTE]
Insert quotes…
Verification
Post reply
Top