Comments on: Avoid spyware by running applications with SetSAFER http://amasan.co.uk/blog/2007/10/avoid-spyware-by-running-applications-with-setsafer/ Commentary on Digital Media and Usability Sat, 20 Dec 2008 10:54:24 +0000 http://wordpress.org/?v=abc hourly 1 By: Sander http://amasan.co.uk/blog/2007/10/avoid-spyware-by-running-applications-with-setsafer/comment-page-1/#comment-169 Sander Sat, 20 Dec 2008 10:54:24 +0000 http://blog.amasan.co.uk/2007/10/30/avoid-spyware-by-running-applications-with-setsafer/#comment-169 I see a new setsafer release on http://blogs.msdn.com/michael_howard/archive/2006/05/07/592136.aspx mak sure you use that one. If you don't use Vista you'll need to download / install .NET framework 2.0 too, as it sounds like it's not installed. I see a new setsafer release on http://blogs.msdn.com/michael_howard/archive/2006/05/07/592136.aspx mak sure you use that one. If you don’t use Vista you’ll need to download / install .NET framework 2.0 too, as it sounds like it’s not installed.

]]> By: KieronH http://amasan.co.uk/blog/2007/10/avoid-spyware-by-running-applications-with-setsafer/comment-page-1/#comment-168 KieronH Fri, 19 Dec 2008 17:59:30 +0000 http://blog.amasan.co.uk/2007/10/30/avoid-spyware-by-running-applications-with-setsafer/#comment-168 Hi Sander, This looks like just the ticket for me to allow our company's users to browse the web more safely. Unfortunately, each time I run setsafer.exe I get a .NET Runtime 2.0 Error conataining the following description: Faulting application setsafer.exe, version 0.9.0.0, stamp 445ec5f8, faulting module kernel32.dll, version 5.1.2600.3119, stamp 46239bd5, debug? 0, fault address 0x00012a5b. Any ideas? Cheers, Hi Sander, This looks like just the ticket for me to allow our company’s users to browse the web more safely. Unfortunately, each time I run setsafer.exe I get a .NET Runtime 2.0 Error conataining the following description:
Faulting application setsafer.exe, version 0.9.0.0, stamp 445ec5f8, faulting module kernel32.dll, version 5.1.2600.3119, stamp 46239bd5, debug? 0, fault address 0×00012a5b.

Any ideas?

Cheers,

]]> By: Sander http://amasan.co.uk/blog/2007/10/avoid-spyware-by-running-applications-with-setsafer/comment-page-1/#comment-144 Sander Mon, 08 Sep 2008 09:53:09 +0000 http://blog.amasan.co.uk/2007/10/30/avoid-spyware-by-running-applications-with-setsafer/#comment-144 Hi loktar thanks for interesting information. psexec looks like a nice addition as well to achieve a similar effect. I think it should have the same drawbacks as setsafer though wrt google desktop etc, as it uses windows policy settings. Maybe now google has fixed these issues, I'm still using the approach in this post and have had no more spyware issues, but have not tried the google products again. Hi loktar thanks for interesting information. psexec looks like a nice addition as well to achieve a similar effect. I think it should have the same drawbacks as setsafer though wrt google desktop etc, as it uses windows policy settings.

Maybe now google has fixed these issues, I’m still using the approach in this post and have had no more spyware issues, but have not tried the google products again.

]]> By: loktar http://amasan.co.uk/blog/2007/10/avoid-spyware-by-running-applications-with-setsafer/comment-page-1/#comment-143 loktar Sun, 07 Sep 2008 19:36:12 +0000 http://blog.amasan.co.uk/2007/10/30/avoid-spyware-by-running-applications-with-setsafer/#comment-143 Hi, if you use the computer yourself, then you might want to consider psexec tool (add -l -d as switches) from sysinternals to restrict apps via shortcuts. If you somehow share the computer with other people, then setSAFER makes more sense. I know about dropmyrights, but I tried it, and it did not work when trying to limit explorer.exe, it gave out an error. While psexec works fine. I like to limit explorer.exe to open files in general. Hi, if you use the computer yourself, then you might want to consider psexec tool (add -l -d as switches) from sysinternals to restrict apps via shortcuts. If you somehow share the computer with other people, then setSAFER makes more sense.

I know about dropmyrights, but I tried it, and it did not work when trying to limit explorer.exe, it gave out an error. While psexec works fine. I like to limit explorer.exe to open files in general.

]]> By: bsforfar http://amasan.co.uk/blog/2007/10/avoid-spyware-by-running-applications-with-setsafer/comment-page-1/#comment-64 bsforfar Fri, 28 Mar 2008 21:17:16 +0000 http://blog.amasan.co.uk/2007/10/30/avoid-spyware-by-running-applications-with-setsafer/#comment-64 interesting, bet it would be good, so if idetrorce don't agree why??????? interesting, bet it would be good, so if idetrorce don’t agree why???????

]]> By: Sander http://amasan.co.uk/blog/2007/10/avoid-spyware-by-running-applications-with-setsafer/comment-page-1/#comment-62 Sander Thu, 07 Feb 2008 12:00:33 +0000 http://blog.amasan.co.uk/2007/10/30/avoid-spyware-by-running-applications-with-setsafer/#comment-62 Ok why? :) Ok why? :)

]]> By: Idetrorce http://amasan.co.uk/blog/2007/10/avoid-spyware-by-running-applications-with-setsafer/comment-page-1/#comment-50 Idetrorce Sun, 16 Dec 2007 00:46:56 +0000 http://blog.amasan.co.uk/2007/10/30/avoid-spyware-by-running-applications-with-setsafer/#comment-50 very interesting, but I don't agree with you Idetrorce very interesting, but I don’t agree with you
Idetrorce

]]>