print spooler access
print spooler access
I apologize in advance for this dumb question.
When I print from my browser (or from the sandboxed PDF application) is Sandboxie accessing the "print spooler" or spoolsv.exe
un-sandboxed?
I say it's sandboxed, but a friend says it's not.
???
When I print from my browser (or from the sandboxed PDF application) is Sandboxie accessing the "print spooler" or spoolsv.exe
un-sandboxed?
I say it's sandboxed, but a friend says it's not.
???
Windows 7 Home Premium 64-bit
SandboxIE 5.2.1.2
SandboxIE 5.2.1.2
When will I learn to do more than one rudimentary search??!
Ok, looks like I'm wrong.
Quote from Tzuk...."Printing is part of GDI, the graphics subsystem in Windows, and GDI does not allow more than one print spooler."
and
"It's not a breach because no arbitrary data is sent ouside the sandbox, only well-defined print commands that serve as instructions for how to put letters and drawings into a PDF file."
Soooo, it's nothing to worry about because the info being sent to the print spooler are just instructions on how and what to print, not the actual (potentially dangerous) file...?
Ok, looks like I'm wrong.
Quote from Tzuk...."Printing is part of GDI, the graphics subsystem in Windows, and GDI does not allow more than one print spooler."
and
"It's not a breach because no arbitrary data is sent ouside the sandbox, only well-defined print commands that serve as instructions for how to put letters and drawings into a PDF file."
Soooo, it's nothing to worry about because the info being sent to the print spooler are just instructions on how and what to print, not the actual (potentially dangerous) file...?
Windows 7 Home Premium 64-bit
SandboxIE 5.2.1.2
SandboxIE 5.2.1.2
In very few and specific cases a sandboxed program would need to access a resource that is outside the sandbox to accomplish a needed task. In this case it would be printing a document. Blocking access to the printer spooler doesn't provide ang higher level of security, it impairs functionality instead. There isn't much abuse that could result from connecting to the spooler service unsandboxed, ie all a virus can do is to print itself out.
There are no other exceptions that I know of besides this.
There are no other exceptions that I know of besides this.
Yes, the info being sent to the print spooler are printer spooler commands, not the contents from the PDF or Word or whatever document file or web page.BoredNow wrote:Soooo, it's nothing to worry about because the info being sent to the print spooler are just instructions on how and what to print, not the actual (potentially dangerous) file...?
You could block access to the \RPC Control\spoolss resource (in IPC Access settings) or you could turn off the Print Spooler, but either of these would reduce the usefulness of your Windows computer, to some extent.
tzuk
-
- Posts: 388
- Joined: Sun Oct 12, 2008 9:13 pm
It's the only service which can be utilized directly by a sandboxed program AFAIK. Sandboxie intercepts IPC going to other services in order to contain the malware and halt any potential indirect circumvention ie. in a case involving a potentially malicious file that sends malicious commands for a windows service to carry out on its behalf instead of direclty doing it itself.is this the only service which can be compromised from inside?
In general its good practice to disable any services that you don't need. I don't think that stopping a service would prevent it from being locally exploited however. The benefit is to decrease the amount of open ports on the network. Upnp is one of those services that are higly recommended for disabling.its ok when inside can not stop service outside, but other way round is not acceptable
when service might upnp or any other. eg upnp make doors wide open for malware
connections to routers or modems.
By default they could Sandboxie allows message passthrough to this particular service for convenience of the everyday user. People want to click print and have it done at that instant instead of having to run their browser unsandboxed which could exppose them to risks or having to go through the settings and enbaling an openpath to the spooler service.Are there restrictions on what information can be sent? I've heard of print spooler service exploits before.
In normal circumstances the spooler service validates the parameters of any code relayed to it so it should be a non - issue.
One Program to rule them all, One Program to confine them, One Program to wrest them all and in the sandbox bind them.
Who is online
Users browsing this forum: No registered users and 0 guests