Menu ▾ ▴

#14 Binary packages are not signed and therefore blocked in some cases

1.0
closed
nobody
None
2021-11-02
2021-10-31
Michael Franz
No

Please consider signing binary packages. Windows always warns that the app is not signed and option "Run anyway" is not always available (if corp IT is paranoid).

Thanks in advance!

Discussion

  • Ashok P. Nadkarni

    Ashok P. Nadkarni - 2021-10-31

    Ouch. Looks like I forgot to sign them before uploading. Just uploaded the signed versions.

    Thanks for letting me know.

     

  • Ashok P. Nadkarni

    Ashok P. Nadkarni - 2021-10-31
    • status: open --> closed
     

  • Ashok P. Nadkarni

    Ashok P. Nadkarni - 2021-10-31

    It may take a little time to get distributed to all the mirrors.

     

  • Michael Franz

    Michael Franz - 2021-11-01

    Thanks Ashok,

    I was able to test the updated package with the customer this morning in it installed without issue.

    However I noticed something else... For some reason .tcl extension was not associated with wish.exe and we had to do it manually. The same works well on my PC. FYI.

     

  • Ashok P. Nadkarni

    Ashok P. Nadkarni - 2021-11-02

    It associates .tclapp with tclsh and .tkapp with wish. Is that what you were referring to?

    It does not associate .tcl for a couple of reasons - most .tcl files are applications, only library or package scripts, and second, it would have conflicted with ActiveTcl associations. Also, you need to make sure the checkboxes for that association are selected during install (it is the default but to make sure).

    To associate .tcl, you can use the Windows FTYPE and ASSOC commands.

    /Ashok

     

  • Michael Franz

    Michael Franz - 2021-11-02

    .tkapp is good enough, thanks!

    Also I understand the reasoning.

    Thanks for the clarification and for the support of Tcl/Tk!

     

Log in to post a comment.