Timeline for Smart-Screen filter still complains, despite I signed the executable, why?
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 15, 2021 at 16:22 | history | edited | Maxim Masiutin | CC BY-SA 4.0 |
added 1 character in body
|
Feb 15, 2021 at 16:02 | history | edited | Maxim Masiutin | CC BY-SA 4.0 |
added info on personal experience
|
Sep 30, 2020 at 9:18 | comment | added | IceCold | It seems there is another way to get certified without buying an expensive EV by (quite) "distributing your apps through the Windows Store". See: docs.microsoft.com/en-us/archive/blogs/ie/… I hope getting into the WinStore is not more expensive than the EV :) | |
Sep 12, 2020 at 21:34 | comment | added | MarcusUA | @Basj yes, that's the thing | |
Sep 9, 2020 at 10:33 | comment | added | Maxim Masiutin | @MarcusUA when I wrote this answer (in 2018), all EV certificates require a hardware key, but I did not research this topic since then. At least I did not hear the contrary since that. | |
Sep 8, 2020 at 9:02 | comment | added | Basj | @MarcusUA Do all EV certificates require a hardware key? | |
Feb 20, 2020 at 13:02 | comment | added | Gertsen | @MarcusUA Exactly - Not being able to sign in DevOps or similar non-local deployment pipeline is extremely annoying. I suspect it might be possible if the certificate is stored in Azure Key Vault, but you can't reuse your local certificate for that, it requires a separate certificate for this, effectively doubling the price of an already very expensive certificate. | |
May 29, 2019 at 15:47 | comment | added | MarcusUA | They don't mention that EV certificate uses a hardware key, and cannot be used on with cloud build infrastructure :( | |
Jul 1, 2018 at 23:46 | history | edited | Maxim Masiutin | CC BY-SA 4.0 |
added 52 characters in body
|
Jun 30, 2018 at 10:12 | review | First posts | |||
Jun 30, 2018 at 11:11 | |||||
Jun 30, 2018 at 10:08 | history | answered | Maxim Masiutin | CC BY-SA 4.0 |