I'm a Windows user. I'll do my part :-) On Wednesday, February 10, 2021 at 3:44:43 PM UTC-6 [email protected] wrote:
> Hi John and others at racket-dev, > > > > > 2) If you use Windows and you have experience that would suggest that > we’re somehow misunderstanding this situation, we’d love to hear about it. > > although I am not using Windows, we've been developing some software > that needs direct hardware access for quite some time now here at my > company. > > We faced a similar situation in 2019 and apparently there is only one > "ultimate" solution: get an EV signing certificate from a CA trusted by > Microsoft to sign binaries. Truth is that getting it here in Central > (ehm, ehm, Eastern) Europe is almost impossible. > > Getting OV certificate lowers the required number of > downloaded/installed instances before the SmartScreen warning goes away. > Getting EV one makes it go away immediately (usually - exceptions are > sadly not unheard of). > > We followed the documentation for Windows drivers (which have the > strictest rules) at > > https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/get-a-code-signing-certificate > - similar approach might help here as well. > > > Cheers, > Dominik > -- You received this message because you are subscribed to the Google Groups "Racket Developers" 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/racket-dev/c7119265-303f-41c9-9b95-4235b43f4a70n%40googlegroups.com.
