Discussion in 'sandboxing & virtualization' started by ad18, Dec 16, 2013.
Thanks, Bo. Appreciate your help, brother.
Beta version 4.17.4 is out. The changes in printing that were implemented in version 4.17.3 have been improved (New setting added to Sandbox settings).
Do you guys have issues printing things that's in a sandbox? my printer won't print things inside sbie
No problem here, Overkill. If after upgrading to beta 4.17.4, you are getting a Sandboxie message 1319 and you cant print, to print, you need to tick the new setting in Sandbox settings>Restrictions (look at the picture above).
4.17.4 (64-bit) installed and running fine on two W7x64 machines.
Upgraded from 4.17.2 to 4.17.4 and now I need to check the 'Allow the Windows Print Spooler to print to file' option in order to print in W7. That's from either Chrome of PDF file.
Curt has said,
so I'm not too enthused about this change... if I'm understanding it correctly.
Hi Page, this is how I understand the change. If you tick the new printing option (Allow the Windows Print Spooler to print to file), things related to security in the sandbox are as they were before beta version 4.17.3. What Invincea is doing in beta 4.17.3 and 4.17.4 is closing a potential hole that has been there for as long as Sandboxie has been around.
So, if you need to tick the new setting in order to print, you are not putting yourself at higher risk than you were before installing 4.17.3. In my personal case use, I don't print in W7. I never printed or have set up my W7 laptop to print. So, I don't know if I would need to tick the setting to print in that computer if I wanted to print something.
In XP, the PC that I use for all my printing, I don't have to tick the new setting to print anything. But I have the feeling that perhaps that is because the security improvement has not been added yet for that system. Anyway, If I had to tick the new setting for printing, what I would do is setup a new sandbox and use that sandbox only whenever I need to print something.
So you think it is by design that I began having printer issues upon upgrading from 4.17.2 to 4.17.4?
Yes, by design. With the new setting ticked.....things related to security are as they were before 4.17.3. And without ticking the new setting, security is tighter now that it was before 4.17.3.
After updating Sandboxie to version 4.17.4 on my Windows 8.1 laptop (wireless), I cannot print from any of my sandboxed browsers - Firefox, IE, Chrome.
If I'm using the same browsers without Sandboxie - no issues with printing.
Yes, I have check-marked "Allow the Windows print spooler to print to file".
P.S. I have no printing issues on my wired Windows 7 Desktop while using any browsers with Sandboxie 4.17.4.
Zmechy, I think you should post about your issue at the beta thread at the Sandboxie forum. You would be the first user to report that cant print even after ticking the Allow the Windows print spooler setting.
Thank you for your answer.
Sneak Preview Sandboxie/Windows 10
happy people who bought a lifetime license <thumbup>
love this news
Yeah, I bought two of them
The best smallest amount of money ever spent by me.
Without exaggeration I can't believe I've got so much in return for a ridiculous amount of money, extremely inexpensive these lifetime licenses.
Similar thoughts from me. I view purchasing the lifetime license as the wisest decision I taken about buying something over the internet.
I feel the same exact way.
Sandboxie is definitely one of those wise purchases
New beta version (4.17.5) got released today with improvements in printing.
Norton just quarantined 4.17.5 as WS.Reputation.1
most unusual for SBIE -- even beta's
eh like I said to him the second one isn't a real improvement, more of a regression IMO.
I kind of didn't mind the setting being available in the UI but I agree with Curt, it was risky. The way it is now, if you get the 1319 message, you can allow the print spooler for that session only. It cant get much more convenient and safer than that. Perfect balance.
Whenever I run a SBIE installer at Virus total, Jiangmin always detect the installer as Trojan/Generic.tjzm. No other anti malware program detects anything, ever. I just ran 4.17,5 there and Symantec don't detect nothing. Perhaps you ought to submit the detection as a False positive.
I rarely print anything so I haven't tested it but the way it was explained in that thread I saw a worse outcome. The way you said it it makes more sense. Silly me, I try to see things like my poor ol grandmother might and UI choices are more important. Guess I should I have tested before I spoke :-/
Bo, tell me if you agree with this... having 4.17.4 on my computers now with the print spooler option checked in Restrictions, I will be better off installing 4.17.5 and unchecking the print spooler option, and going forward, only allowing it on a per session basis when I get the 1319 message. That sound about right?
Separate names with a comma.