tisdag 12 oktober 2021 kl. 18:34:11 UTC+2 skrev Stefan: > On Sunday, October 10, 2021 at 11:13:55 PM UTC+2 [email protected] > wrote: > >> torsdag 7 oktober 2021 kl. 21:32:41 UTC+2 skrev Stefan: >> >>> As you've already noticed, you need to digitally sign the binaries if >>> you want to get the support for the Win11 context menu. >>> I've added a few lines to the build.txt file: >>> https://svn.osdn.net/svnroot/tortoisesvn/trunk/build.txt >>> >>> basically, you need to create two files (signinfo.txt and >>> signpublisher.txt) in the wc root, and then start the build. >>> just have a look at the build.txt file, section "digitally signing the >>> binaries and installers" >>> >> >> Thanks, yes, I saw those. My problem was in creating a suitable >> (selfsigned) certificate. I think I managed, but I'll have to doublecheck >> the different steps. Would it make sense to document these steps in >> build.txt? I can write them up after double checking. >> > > yes, of course you can add to build.txt! > > >> >> if you then still have questions, please ask! >>> >> >> Yes, but maybe this should be a new thread. Even though I have everything >> signed (almost - TortoiseSVN32.dll and TortoiseStub32.dll are not signed) >> and no error messages during the build, the context menu is still only >> available under Shift-F10. Is this a known problem with a selfsigned cert >> or can I check somewhere if it was installed properly? (I've rebooted my >> computer after installation). >> > > well, unfortunately, there's no way (I know of) to really figure out why > the menu won't show up. It took me more than a week to get this working... > Since most of what I learned is now in the build script, a few pointers: > * the text in signpublisher.txt must match the certificate DN *exactly* > (but it must be xml quoted, e.g. a " must be changed to ") > * signing must be done with the /fd SHA256 switch, otherwise you'll get a > non-descriptive error when building the msix > as for self-signed certificates, I'm not sure these would even work. But > you will have to install the certificate into the Windows root chain if you > want any chance to get that to work. Just signing without having the cert > also installed will definitely not work. And the certificate needs to be > created with SHA256 encryption - anything else won't work (but you won't > get any errors, it just silently won't work). >
Thanks. I believe I've done all this, still doesn't work. I think I'm able to get an official certificate from digicert through apache.org so I'll investigate that route first and come back if I have further questions. Kind regards, Daniel -- 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/2507773a-314a-497c-9961-d51913758880n%40googlegroups.com.
