What the press connector can and cannot see

This page is for whoever looks after the network at your site. It says what the press connector does on your network and what it does not.

What it connects to

• Only outward. Nothing listens except a status page on the computer itself, on the local address only, and that page checks who is asking. No firewall rule is needed to let anything in.
• Only Studio's own address, over https. It follows no redirect. An update may come only from Studio's own host or releases.postpressprint.com, under one path, and every address is judged before the first byte is fetched.
• A proxy that Windows is set to is not used. A shop behind one needs the entry to allow Studio's address.

What it looks at

• Only your shop's own network. Private addresses and the /24 it is on, six hosts at a time. For each address it reads the printer's name and state, and asks a printer for its attributes. For a RIP's port it makes one read with no credential.
• Read only toward a RIP. It signs in to ONYX, where you have turned it on, and lists printers. It has no code that places, releases, starts or deletes a job.
• The one thing it writes toward a RIP is a print file into the hot folder you named, written under a name your RIP ignores and then renamed into place. It lists, reads and deletes nothing in a hot folder, and makes a folder only when a supervisor asked for one.
• Closed folders. It will not look in a whole drive, the Windows folder, Program Files, the recycle bin, a user's own folder or its application data, and never through a link or junction.

What it tells Studio

Once a minute: the computer's name, the site's name, the version, and the printers, cutters and RIP servers it found with their names, models and states. Nothing of a job's design, its artwork or a customer is in the report.

What it brings down

Only the jobs you put on its own site's presses. The saved job goes to a file in the connector's own folder, its fingerprint is checked, the print file is written, and the connector removes its own copy once the job's outcome is final. A press that two connectors claim is handed to neither.

What it keeps on the computer

Its token, its settings, the updates it has fetched and a log for each month, in a folder named PostPress Connector under the user's local application data. The program we give you holds no token or secret.

Who can switch it off

A supervisor can disconnect it at any time. That stops its reports and fetches, and deletes nothing. If your licence has ended, it keeps its permission and waits.

What it does not do yet

It reports no press's ink, roll or job. A press that no connector sees is added by its address or name. Setting up in a shared folder, a real update restart and a real network share have not yet been tried by hand, and the connector has so far been tried only against a stand-in press.