Skip to content

Update the installer git uses to 5.5.8 please #647

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
paladox opened this issue Feb 4, 2016 · 4 comments
Closed

Update the installer git uses to 5.5.8 please #647

paladox opened this issue Feb 4, 2016 · 4 comments

Comments

@paladox
Copy link

paladox commented Feb 4, 2016

Hi please update Inno Setup to 5.5.8

The change log for changes is http://www.jrsoftware.org/files/is5-whatsnew.htm

The main changes I think are good are

•The [Setup] section may now list multiple SignTool directives which will be executed in order of appearance. This can be used to dual sign (SHA1 & SHA256) Setup and Uninstall. This requires a recent signtool.exe version and a SHA256 (SHA-2) certificate. Inno Setup's own installer is now also dual signed. See the help file for a dual sign example. Without dual signing Windows will no longer trust any of your new installers if they are downloaded. See http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx for more information.

Which we are doing.

•The Compiler IDE's New Script Wizard now offers to create a shortcut to the main executable in the common Start Menu Programs folder instead of creating a new Start Menu folder especially for the application. This option is enabled by default and is recommended by Microsoft unless you install a suite of applications rather than a single application.

@paladox paladox changed the title Update the installer git uses to 5.5.8 Update the installer git uses to 5.5.8 please Feb 4, 2016
@dscho
Copy link
Member

dscho commented Feb 4, 2016

We are dual signing without the need for the new feature. And we do not use the IDE.

@paladox
Copy link
Author

paladox commented Feb 5, 2016

Oh ok.

@dscho
Copy link
Member

dscho commented Feb 7, 2016

The main changes I think are good

This completely misses that we are using 5.5.6, still, and it is quite possible that our use of git-edit-bash.dll is broken by this change in 5.5.7 (which you did not mention at all):

;* The Setup and Uninstall programs are now marked as DEP and ASLR compatible. This can be disabled by setting the new DEPCompatible and ASLRCompatible [Setup] section directives to no. Doing this for DEP compatibility might be needed if you're using a buggy third-party DLL from [Code], like isxdl.dll.

That would be a rather dramatic regression, and it would have been good if you would have tested this before opening this ticket (you have been around long enough to know how to make an installer).

@dscho
Copy link
Member

dscho commented Feb 16, 2016

This completely misses that we are using 5.5.6, still, and it is quite possible that our use of git-edit-bash.dll is broken by this change in 5.5.7 (which you did not mention at all)

I did the menial work of testing this and found edit-git-bash.dll to be safe and still working with 5.5.9-dev. For the record: anybody testing such things relieves me greatly.

dscho added a commit to dscho/git that referenced this issue Jun 21, 2024
I noticed the `osx-gcc` job failing in git-for-windows#647 so I found this upstream fix
from @peff. Merging now to unblock PR builds in `microsoft/git`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants