Sandboxie Forum - Skype (5052)

tzuk:

Tue Mar 17, 2009 9:37 pm

Thank you for the confirmation JimOfCR.

JimOfCR:

Tue Mar 17, 2009 4:04 pm

Success! I upgraded to 3.35.17 I removed \RPC Control\plugplay from Resource Access->IPC Access->Direct Access from the Sandboxie box SkypeBox. Skype 4.0.0.206 initialized and became ready without errors. Thanks a bunch.

tzuk:

Mon Mar 16, 2009 5:44 pm

Thanks for checking JimOfCR. I did find a small problem related to this. Please try again with version 3.35.17.

JimOfCR:

Sun Mar 15, 2009 4:43 pm

I have upgraded to Sandboxie 3.35.16. I removed \RPC Control\plugplay from Resource Access->IPC Access->Direct Access from the Sandboxie box SkypeBox. The Skype initializing window displayed followed by the Windows AppCrash dialog with Skype.exe named. I decided to try reinitializing Vista. I got the same results but after the AppCrash dialog, I got an Access Violation msg for Skype.exe. I then restored the \RPC Control\plugplay into the configuration for SkypeBox. Skype initializied and operated normally. I will continue to use 3.35.16 with \RPC Control\plugplay until advised otherwise. Thanks for tackling this and good luck on tracking it down. Let me know if I can help through providing more information. In addition to being a developer for over 30 years, I also have years of experience in testing software of many types.

tzuk:

Wed Mar 11, 2009 9:19 pm

Please try version 3.35.15. http://www.sandboxie.com/phpbb/viewtopic.php?t=4985

tzuk:

Tue Mar 10, 2009 6:51 pm

Like I said, I believe I fixed it already, but I'll need your confirmation later on. I haven't released the fix yet because I've also started working on some other big feature and I'm not ready to release it yet. But hopefully, tomorrow or the day after that.

JimOfCR:

Tue Mar 10, 2009 6:34 pm

I'm sorry to have been absent from this thread for awhile. Adding \RPC Control\plugplay does, in fact, allow Skype to run on my machine. tzuk, your mention of Skype trying to access devices is interesting because my webcam stopped working with Skype 4 beta. I kept reporting it to them. With the official release of version 4, my webcam resumed working (and the problem with sandboxing began). Interestingly, my webcam worked fine with earlier versions of Skype running in a Sandboxie sandbox. Thanks very mucyh for thie workaround. I worry about the security of peer-to-peer technology like that of Skype. The workaround may not be ideal (and maybe it is), but at least I have Skype back inside its own private sandbox again.

tzuk:

Wed Mar 04, 2009 5:04 pm

I think I managed to fix this. I will ask you to check and confirm this, when I release the next beta version.

dogdog:

Tue Mar 03, 2009 8:48 am

]]>Quoting tzuk: ]]> ]]>Quoting dogdog: ]]>Will you be able to include long term solution specific to Skype in Sandboxie v 3.35?? ]]> I hope to address this within a week or two. ]]>Quoting dogdog: ]]>What is Skype trying to access that change allows?? ]]> Skype is trying to find or use some hardware devices, most likely a webcam. ]]> Many thanks.

tzuk:

Mon Mar 02, 2009 6:35 pm

]]>Quoting dogdog: ]]>Will you be able to include long term solution specific to Skype in Sandboxie v 3.35?? ]]> I hope to address this within a week or two. ]]>Quoting dogdog: ]]>What is Skype trying to access that change allows?? ]]> Skype is trying to find or use some hardware devices, most likely a webcam.

dogdog:

Mon Mar 02, 2009 5:28 pm

]]>Quoting tzuk: ]]>For an immediate solution, try going to Sandbox Settings > Resource Access > IPC Access > Direct Access, and add: \RPC Control\plugplay This exclusion is related to what I've determined to be the cause of the problem, so I'd really like to hear if this exclusion is making a difference on your systems as well. ]]> With your change to the sanbox settings I can run Skype v 4.4 sandboxed with no problems. Pending a long term (more secure solution) I have reverted to Skype v 3.8 without change to sandbox settings. Will you be able to include long term solution specific to Skype in Sandboxie v 3.35?? For my own interset what does this extra IPC access actually do?? What is Skype trying to access that change allows?? Once again many thanks for your prompt help with this problem.

PiCo:

Mon Mar 02, 2009 12:00 pm

Your solution works fine here tzuk :)

tzuk:

Mon Mar 02, 2009 10:48 am

I said immediate solution and I meant short-term solution. Long term I plan to fix the problem at the source. But I would like to get confirmation from you guys that what I perceive to be the source of the problem in my system is also the source of the problem in your system. And to get that confirmation I need you to apply the setting and let me know if Skype then runs sandboxed correctly. Thanks.

dogdog:

Mon Mar 02, 2009 9:14 am

]]>Quoting tzuk: ]]>For an immediate solution, try going to Sandbox Settings > Resource Access > IPC Access > Direct Access, and add: \RPC Control\plugplay This exclusion is related to what I've determined to be the cause of the problem, so I'd really like to hear if this exclusion is making a difference on your systems as well. ]]> 1) I have not noticed anything else being affected when I use the sandbox. 2) There must be a change between Skype v 3.8 and v 4.0 that requires this additional access. 3) What does this extra IPC access actually do?? 4) For security reasons could this access be restricted to just the necessary Skype components rather than being general (I assume that this solution gives access [RPC Control\plugplay] to other programs as well as just Skype)?? Many thanks

tzuk:

Sun Mar 01, 2009 9:04 pm

For an immediate solution, try going to Sandbox Settings > Resource Access > IPC Access > Direct Access, and add: \RPC Control\plugplay This exclusion is related to what I've determined to be the cause of the problem, so I'd really like to hear if this exclusion is making a difference on your systems as well.

dogdog:

Sun Mar 01, 2009 8:14 am

]]>Quoting tzuk: ]]>Sorry guys, I did not realize that I should sign in. When I said it was working for me I meant that the sign-in window came up with no error. Now having read JimOfCR's comment, I tried again, but this time I did sign in, and I did get the error this time. I don't have an answer immediately, but at least I know where to look now. ]]> For what it is worth. When I tried I got the Sign In Window but the "egg timer" was running; the error as described above then appeared. I had not had a chance to try to sign in. It sounds like JimOfCR had the same results. tzuk seems to have got to a stable sign in window and the error only appeared after he tried to sign in. So perhaps a slight difference?? Sounds more hopeful - tzuk seems to on the track of some difficulty with Skype. Many thanks.

tzuk:

Sat Feb 28, 2009 11:20 pm

Sorry guys, I did not realize that I should sign in. When I said it was working for me I meant that the sign-in window came up with no error. Now having read JimOfCR's comment, I tried again, but this time I did sign in, and I did get the error this time. I don't have an answer immediately, but at least I know where to look now.

dogdog:

Sat Feb 28, 2009 6:28 pm

OK - problem is as yours. What in particular I do not understand is why tzuk is not getting the same problem when he tries to do the same?? What is happening differently in tzuk's setup??

JimOfCR: Giving Up

Sat Feb 28, 2009 5:01 pm

I have just fully uninstalled Sandboxie 3.34 and reinstalled it. Without changing the default configuration, I started Skype 4.0.0.206 in the only sandbox: DefaultBox. It crashed. In the Sandboxie window, I see: Start.exe A few seconds later Start.exe disappears and I see: Skype.exe, , SandboxieRpcSs.exe, SandboxieDcomLaunch.exe Next, the Skype 'signing in' window appears on the desktop. A few seconds later, skypePM.exe appears in the Sandboxie window followed a second later by Werfault.exe. The 'App has stopped working' dialogbox appears on the desktop. Details say that an AppCrash has occurred and Skype.exe is named. At this point, I give up. I can think of nothing further to do. My version of Vista is Home Premium with SP1 and all updates installed up to and including those of this morning. I will just have to run Skype without a sandbox.

JimOfCR:

Sat Feb 28, 2009 3:20 pm

I'm not sure why you think no one else is having your problem, dogdog. It sounds the same as the one I reported above. I am not running the free version of Sandboxie. I do not have the Google toolbar installed on Skype. I do not want to return to an earlier version of Skype because call quality is so much better with the new version ... no echo, no delay. I will continue to run Skype un-sandboxed until I can figure out what is going on. Note that I mention in my first post that I used a new, completely unrestricted sandbox and still could not run Skype sandboxed. If I figure this out, I will post back what I did.

PiCo:

Fri Feb 27, 2009 1:36 pm

I can confirm the OP. Vista 32bit Bussiness SP1 - Sandboxie 3.34 Funny thing is when I have DropMyRights enabled, it reaches a certain point of loading and then Microsoft says Skype stoped working. When I don't use DropMyRights as soon as I run Skype Sandboxed there's an Access violation error. Hope it will help in any way :)

dogdog:

Fri Feb 27, 2009 12:28 pm

Tried uninstalling & reinstalling Sandboxie - problem still there. Tried removing option where DEP is turned on for all programs - problem still there. Uninstalled Skype v 4.0.0.206 and installed Skype v 3.8.0.154. Can now run Skype sandboxed without any problems. Connundrums: 1) Why does Skype v 3.8 work but v 4.0 does not?? 2) Why is my problem not being reproduced by others?? I use Vista Ultimate + Zone Alarm Security Suite. Any thoughts gratefully received.

dogdog:

Fri Feb 27, 2009 9:32 am

]]>Quoting tzuk: ]]>There is no reason why it should be a free/paid thing. Free/paid only makes a difference as to whether Sandboxie will run the program at all, not how well Sandboxie will run a program once it's started running sandboxed. As for your problems, I'm not sure what else to advise. One thing that does come to my mind, is that in my experiment I did not install the Google toolbar with Skype. But I'm not sure if that should have any impact. ]]> Also did not install Google Toolbar so that is not the difference. I will keep trying things and report back.

tzuk:

Thu Feb 26, 2009 10:25 pm

There is no reason why it should be a free/paid thing. Free/paid only makes a difference as to whether Sandboxie will run the program at all, not how well Sandboxie will run a program once it's started running sandboxed. As for your problems, I'm not sure what else to advise. One thing that does come to my mind, is that in my experiment I did not install the Google toolbar with Skype. But I'm not sure if that should have any impact.

dogdog:

Thu Feb 26, 2009 4:27 pm

]]>Quoting tzuk: ]]>I tried with version 3.34, still no problems. Try using a clean sandbox with no restrictions at all -- maybe the latest Skype expects to be able to access your Documents folder for some reason, and is not prepared to handle the case where this folder is not accessible. Update: Actually I just tried it myself. After blocking C:\Users\myUser, I could no longer run Skype sandboxed. So, it seems the problem is with Skype and not with Sandboxie. You can no longer keep Skype from looking into your personal folders. ]]> I tried a creating a brand new sandbox - no changes from default/no restrictions. Same problem as before. As for JimOfCR. Any thoughts?? Could it be due to using free version of Sandboxie??

JimOfCR:

Thu Feb 26, 2009 4:18 pm

I cannot get Skype 4.0.0.206 to run sandboxed. Until this morning, I was using the latest beta version of the new Skype 4 sandboxed. This morning I updated to 4.0.0.206 and cannot run it. I have tried everything listed in this thread, but only managed to change the error message. The first msg said Access Violation. Now, I am simply informed the app has stopped working. Skype 4.0.0.206 does work outside of a sandbox ok. (Vista SP1 6.0.6001.2.1.0.768.3, Sandboxie 3.34.) I have not tried upgrading to Sandboxie 3.35.13. I can find no reference to this build outside of this forum. Anyway, tzuk was able to run Skype using 3.34. I disabled forced programs in Sandboxie in order to start Skype in the new, unrestricted sanbox I created for it. I usually run it in its dedicated sandbox. I am at a loss. Suggestions?

tzuk:

Thu Feb 26, 2009 1:23 pm

I tried with version 3.34, still no problems. Try using a clean sandbox with no restrictions at all -- maybe the latest Skype expects to be able to access your Documents folder for some reason, and is not prepared to handle the case where this folder is not accessible. Update: Actually I just tried it myself. After blocking C:\Users\myUser, I could no longer run Skype sandboxed. So, it seems the problem is with Skype and not with Sandboxie. You can no longer keep Skype from looking into your personal folders.

soccerfan:

Thu Feb 26, 2009 1:21 pm

]]>Quoting dogdog: ]]>I have tried running other installed programs in a sandboxed mode - no problems - so presumably my Sandboxie installation is OK. Are there any diagnostics I can follow to see why Skype is failing to run sandboxed?? ]]> Presumably you are using sbie3.34 .Since tzuk was able to run it in 3.35.13, my suggestion would be to try version 3.35.13 and take it from there.

dogdog:

Thu Feb 26, 2009 7:43 am

I have tried running other installed programs in a sandboxed mode - no problems - so presumably my Sandboxie installation is OK. Are there any diagnostics I can follow to see why Skype is failing to run sandboxed??

dogdog:

Wed Feb 25, 2009 11:07 pm

]]>Quoting tzuk: ]]>I just downloaded the SkypeSetupFull.exe for version 4.0.0.206 and installed it in Windows Vista, and it runs ok sandboxed. I used version 3.35.13 but I'm not sure if that should make any difference compared to version 3.34. Can you try uninstall Skype completely and then reinstalling it? ]]> Just did as requested - ininstalled Skype, downloaded Skype v 4.0 and reinstalled Skype outside the sandbox. Results are the same as before - no problem running Skype unsandboxed but same error when I try to run Skype sandboxed??? I am using clean sandbox with no standard settings other than denying access to personal folders. Could you try with v Sandboxie 3.34 and see if you can replicate my problem. Many thanks.

tzuk:

Wed Feb 25, 2009 10:12 pm

I just downloaded the SkypeSetupFull.exe for version 4.0.0.206 and installed it in Windows Vista, and it runs ok sandboxed. I used version 3.35.13 but I'm not sure if that should make any difference compared to version 3.34. Can you try uninstall Skype completely and then reinstalling it?

dogdog:

Wed Feb 25, 2009 5:06 pm

I also created a new sandbox to try Skype with no restrictions on box other than blocked access to personal folders.

dogdog:

Wed Feb 25, 2009 3:54 pm

]]>Quoting soccerfan: ]]>Have you tried deleting the contents of the sandbox and then starting over? ]]> Yes. And rebooting PC!!

soccerfan:

Wed Feb 25, 2009 3:40 pm

Have you tried deleting the contents of the sandbox and then starting over?

dogdog: Skype

Wed Feb 25, 2009 2:02 pm

I am using Vista premium & Sandboxie v 3.34 I have Skype installed on PC proper (ie not installed within a sandbox) but then run Skype sandboxed. I was using Skype v 3.8.0.188 and had no problems. Skype just updated to v 4.0.0.206 (update done on PC proper ie installation not sandboxed). Now when I try to run Skype sandboxed I get a Microsoft Windows message that "Skype has stopped working" "A problem has caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" but nothing further happens. Any others with same problem?? Any thoughts??