scala-cli icon indicating copy to clipboard operation
scala-cli copied to clipboard

Support signed Windows msi installer

Open ekrich opened this issue 3 years ago • 4 comments

I am on a typical corporate network and unable to install the MSI even via an elevated permissions shell at the command line.

Windows protected your PC
Microsoft Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk.

App: 
scala-cli-x86_64-pc-win32.msi 
Publisher:  
Unknown publisher 

I believe we need a signed MSI as talked about in the following link:

https://www.scala-sbt.org/sbt-native-packager/formats/windows.html

ekrich avatar Apr 12 '22 23:04 ekrich

This would be very good to have!

bjornregnell avatar Apr 18 '22 15:04 bjornregnell

@ekrich Kind of late answer, but can you try to install scala-cli in version 0.1.10 via MSI installer in typical corporate network ? You can find here MSI installer of Scala CLI 0.1.10.

We processed verification of scala-cli 0.1.10 MSI installer in Windows Defender and I hope, it should work now.

lwronski avatar Aug 25 '22 14:08 lwronski

Sure, I can try when I get back to the office next week and any details on other methods that may have worked.

ekrich avatar Aug 26 '22 14:08 ekrich

@lwronski That version, https://github.com/VirtusLab/scala-cli/releases/tag/v0.1.10, allows the installer to run but then I don't have admin privileges so I can't install, even into my home directory. We could request to get scalacli approved if the installers can be signed on each release - that may be the easiest. Otherwise an installer like "Git for Windows" that allows local (into user) install without enhanced privileges.

We are also still having a coursier redirect basic auth proxy issue which I haven't had a chance to look into yet which makes Metals and other tools not function when on the network.

I was able to get scalacli installed via sdkman but with some difficulty and running some commands locally.

Edit: I can post the sdkman details but I am not sure who prepares those release or where I should do that.

ekrich avatar Aug 30 '22 16:08 ekrich

We sign each subsequent release at this point, so the issue shouldn't be present. The verification process with Microsoft sometimes takes up to even 2 weeks after a relase, so please remember to be patient (although sometimes it gets approved on the same day, that process is outside of our control). Issues with proxies are tracked elsewhere: #1109 Closing this.

Gedochao avatar Dec 20 '23 10:12 Gedochao