Nightly builds with support for Win11

[Daniel Sahlberg]

Hi,

I've been trying to build my own setup to test on Win11, however I'm have not been able to make the code signing work yet.

In the meantime I looked at the nightly builds but it seems they are not built with support for the Windows 11 context menu either.

Is there any chance to configure the nightly builds with support for the Windows 11 context menus? Or is it still too much work in progress to be meaningful to test?

Kind regards

Daniel Sahlberg

[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"

if you then still have questions, please ask!

as for the nightly builds getting that, I don't think this will happen - the WANdisco guys can't get the digital signing to work, and I've asked many, many times....

Stefan

[Daniel Sahlberg]

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.

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).

 

as for the nightly builds getting that, I don't think this will happen - the WANdisco guys can't get the digital signing to work, and I've asked many, many times....

Oh, that's too bad.

Thanks for your help so far!

Kind regards

Daniel

[Stefan]

On Sunday, October 10, 2021 at 11:13:55 PM UTC+2 daniel.l...@gmail.com 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).

Stefan

[Daniel Sahlberg]

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

 

[Stefan]

here's how to create a self-signed certificate that's compatible with Windows identity needed for packages:

https://docs.microsoft.com/en-us/windows/win32/appxpkg/how-to-create-a-package-signing-certificate

[Daniel Sahlberg]

onsdag 13 oktober 2021 kl. 20:33:00 UTC+2 skrev Stefan:

here's how to create a self-signed certificate that's compatible with Windows identity needed for packages:

https://docs.microsoft.com/en-us/windows/win32/appxpkg/how-to-create-a-package-signing-certificate

Thank you Stefan, that was the final piece of the puzzle. I now have a working context menu in Win11.

Would you consider to add this link to build.txt?

Kind regards,

Daniel

[Robert Woods]

Is there a way to release to all Windows 11 users?  I really would like to have context menus back in one click without reverting back to previous context menus.