Reply to thread

Message

<blockquote data-quote="danb" data-source="post: 917274" data-attributes="member: 62850">Yeah, the standalone version of WLC is far less prone to bugs than VS simply because the code does not have nearly the number of moving parts that VS has.&nbsp; There have been a few bugs, but I think it has been pretty much bug free for the last few months.&nbsp; If you guys find anything we need to fix though, please let me know.Now that VS 6 is stable, it is time to add the other other file types to WLC, mainly script extensions that WLC currently does not cover.&nbsp; I have started building a list of file types WLC should cover and will post the list in a day or so, that way you guys can see if I missed something.&nbsp; Once we have a good list to work from, I will implement the changes in VS and WLC... that way when WLC is active, users can be essentially certain that only Safe executable code, scripts, LOLBins, etc. are running at any given time.&nbsp; Thank you!</blockquote>

[QUOTE="danb, post: 917274, member: 62850"] Yeah, the standalone version of WLC is far less prone to bugs than VS simply because the code does not have nearly the number of moving parts that VS has. There have been a few bugs, but I think it has been pretty much bug free for the last few months. If you guys find anything we need to fix though, please let me know. Now that VS 6 is stable, it is time to add the other other file types to WLC, mainly script extensions that WLC currently does not cover. I have started building a list of file types WLC should cover and will post the list in a day or so, that way you guys can see if I missed something. Once we have a good list to work from, I will implement the changes in VS and WLC... that way when WLC is active, users can be essentially certain that only Safe executable code, scripts, LOLBins, etc. are running at any given time. Thank you! [/QUOTE]

Verification