UUtly Remote Download

Code signing

Every Windows file we publish, including the portable version, the installer and the programs inside it, is signed with an Authenticode signature. Each signature also has a timestamp from DigiCert, which keeps it valid after the certificate that made it expires.

Why Windows says “unknown publisher”

For now, our files are signed with a certificate we created ourselves, named Utly Development Studio (development signing). The signature is real, and it shows that the file hasn’t been changed since we signed it. But Windows doesn’t know our certificate yet, so SmartScreen calls us an “unknown publisher”.

To check who signed a file and when, right-click it, choose Properties and open the Digital Signatures tab.

If you want Windows to trust our files before our public certificate arrives, you can import our development certificate into your computer’s Trusted Root and Trusted Publisher certificate stores. Please only do this if you’re comfortable with it, because it tells Windows to trust everything we sign with that certificate.

Our public certificate

We’re getting a certificate from a public certificate authority, which checks who we are before issuing it. Once we start signing with it, Windows will show our name as the publisher. SmartScreen builds trust in a new certificate over the first few weeks of downloads, so you might still see the warning for a little while after the switch.

How updates are protected

Updates are checked with a second signature that has nothing to do with Windows. We sign every version we publish, and the document that describes it, with a private key that we keep ourselves. The program contains the matching public key. It won’t read an update document unless the signature checks out, and it won’t run anything it downloaded unless that file’s signature checks out too, whatever the web server says. The only thing that isn’t signed is how many computers are offered an update at once, and the most anyone could do with that is hold an update back.

This means that if our web server or a certificate authority were hacked, the attacker could stop updates from arriving, but couldn’t give you a version we didn’t sign. Before the public launch, the private key will move to a hardware device that we only connect when publishing a release.