Do you really have to be so vague? Why not just tell exactly what you mean? I mean the feature has not even been implemented yet, so for what exactly are you afraid?Ok, I'll give you a hint, it involves coding malware

Then why do you keep asking me Rasheed?Rasheed187 wrote:LOL, do you really think that more knowledgeable people can´t figure it out themselves, without any clues from you?
Oh thank you, I am flattered!What are you, some top notch hacker?
Yes, but I think you got the wrong idea. Right now, SBIE is already blocking lots of stuff to keep the system safe, right? I´m just asking for a feature that would notify me about the suspicious (malicious) behavior that is blocked or virtualized, that´s all.Having said that, the reason I don't add malware analyzing features is that it isn't just a small feature.
Perhaps, because I´m not that knowledgeable? No but seriously, I don´t see how this feature could be used by the bad guys, because that´s what you´re saying, no?Then why do you keep asking me Rasheed?
So now you want to hack SBIE?then it would be patched (if this had been incorporated in the first place).
Well, it was just a question, so don´t be.Oh thank you, I am flattered!
Really? I thought that EQSecure was like SSM, but with basic sandboxing which is more like Geswalls version of sandboxing, then sandboxies version of sandboxing?Rasheed187 wrote:Btw, EQSecure is already working on a sandbox based on virtualization, but it still needs lots of work, and I don´t really like it at the moment.
Well, right now Tzuk is considering the flashing icon request that flashes the tray icon when any new program starts in a sandbox. That seems better to me, in that then it would be up to you to determine if it was suspicious. Rather than have sandboxie somehow keep up to date on everything that was deemed suspicious. 'Suspicious' is just too vague. IMO.Yes, but I think you got the wrong idea. Right now, SBIE is already blocking lots of stuff to keep the system safe, right? I´m just asking for a feature that would notify me about the suspicious (malicious) behavior that is blocked or virtualized, that´s all.
Yes it was and is exactly like SSM, but now they have also added a sandbox to it, so perhaps I can ask them to implement my idea, it would make more sense to implement it in a mix between HIPS/Sandbox, than into a pure sandbox like SBIE. But like I said before, it´s not quite finished yet, and overall I don´t really like the app at the moment, but it does have potential.Really? I thought that EQSecure was like SSM, but with basic sandboxing which is more like Geswalls version of sandboxing, then sandboxies version of sandboxing?
I honestly don´t see the point behind this. You mean like in a drive by attack? I think it´s a better idea to simply deny apps from starting automaticly without user interaction. I think this is an area where sandboxes should become better, it should block child processes automaticly. But for now a nice workaround is to make a HIPS (like SSM) take care of this, and this means that almost every "drive by" attack would fail to do any damage, even in the sandbox.Well, right now Tzuk is considering the flashing icon request that flashes the tray icon when any new program starts in a sandbox.
Let me guess, you have never used a HIPS, or you didn´t like them, correct? If you know how to use a HIPS, there is nothing vague about it.'Suspicious' is just too vague. IMO.
Hey, You're the one that took it up a level on what a HIPS would cover. It is vague on what it is that Sandboxie would do over and above a HIPS.On the other hand, there is also a problem, namely, in order for my plan to work, SBIE must monitor exactly the same, or even more than the HIPS who takes care of actions outside sandbox.
This is also vague in that are you asking for Sandboxie to actually stop all child processes or to sandbox those child processes? Why would you want to stop them, or are you not aware that Sandboxie already does sandbox them? Every sandboxed drive-by attack already fails to do any damage, so you’re stating that as a concern indicates that you are not aware of that.I honestly don’t see the point behind this. You mean like in a drive by attack? I think it’s a better idea to simply deny apps from starting automatically without user interaction. I think this is an area where sandboxes should become better, it should block child processes automatically. But for now a nice workaround is to make a HIPS (like SSM) take care of this, and this means that almost every "drive by" attack would fail to do any damage, even in the sandbox.
Users browsing this forum: No registered users and 1 guest