The nightly builds should be signed, but there's a problem with the signing 
certificate so most of the time, the signing fails.

Signing has the advantage that when installing, you'll get a nicer dialog 
from Windows, i.e. the warning is not as severe as if it wasn't signed.
Also, users can verify that the download hasn't been tampered with.

If you want to sign the binaries and the installler, create a file named 
"signinfo.txt" in the WC root, and put your cert info in that file:
/I "Certificate-Name" /a /t "http://signing.time.server/"; /d "TortoiseSVN" 
/du "http://assembla.com"; /q
Then the build script will find that file and automatically sign all files 
during the build.

In case your signing certificate comes with a chip/usb-stick and requires a 
password for every signing, you can install this little tool:
https://www.mgtek.com/smartcard
and follow the instructions on how to install and configure it.

and then in the default.build.users file add the line
    <property name="signtool" value="scsigntool.exe" />

this will make the build script use the smartcard signing tool which 
automatically enters the password so the build script can run unattended.

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn-dev/f9cdfae9-57ab-4e45-aad2-60598e14a14e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • Signing p... tortoisesvn-dev+APn2wQd1mkOrV2yJHJ8Pt6PHurVkdg_F5JS4zFRfN0DSt5fR
    • Re: ... Stefan via TortoiseSVN-dev

Reply via email to