-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Smartscreen warning #9
Comments
I believe for now the best course of action should be "don't worry about it" ? |
probably; its just people don't read properly and start telling others "windows is saying this is a virus" :/ |
Would be great if the installer triggered 0 warnings. |
I'll have to do it sooner or later, probably when I hit v1.0. |
damn, yeah they are expensive.. |
So I need help using github if anyone knows how to help will be appreciated |
Looks like I won't be able to do it for v1.0, hardware is required now for signing which will take time for me. @LivedWhistle52 To avoid going off-topic, you can have talk about things in lively reddit discussion thread instead https://www.reddit.com/r/LivelyWallpaper/ |
how do I know this is safe |
What code signing does is it verifies the installer has not been modified - if you download from the official website you are fine. Lively is just a fun learning project for me to try new things, I don't plan to make any profit from this project ..if it sounds too good to be true that's why. |
well thats the only confirmation I needed 😄 thanks 🚀 |
Any reason it can't be deployed through the windows app store? I have a wpf app that is deployed that way and Microsoft takes care of the signing. |
Oh I thought third party key was still needed! |
The Git Extensions project was gifted an Open Source certificate from signpath.io. You may be able to reach out to them. |
Thanks for letting me know, I'll send them a mail. |
every time i launch it i get a BSOD |
If your getting a bsod from running a web browser/ videoplayer it is more likely your system has some underlying issue that need fixing. Also try to keep this discussion on track, create a new issue with more details so that I can have a look at it. |
nope its just this |
Over 400k download and first time I'm hearing of this, take it as you will. Not sure if spam or not, you are clearly not interested in helping to trace the cause of the issue and just want to make claims without much information in an unrelated thread. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Check Certum, they have pretty cheap code signing certificates for open source, they even have signing in cloud (however it is more expensive, but you don't need any HW) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This is a discussion for about smartscreen warning only, for other problems create a new Issue: |
Windows store version released: #213 |
Windows: this application looking sus and its time to play |
Discussion is going off-topic, locking for now. |
Update |
Looks like will need to buy code signing cert either ways:
|
Basically the lively installer is blocked by windows smartscreen filter, can be bypassed by clicking More Info -> Run anyway.
https://support.microsoft.com/en-in/help/17443/microsoft-edge-smartscreen-faq
It will go away after some amounts of download, but the problem is as I update my application with new version, the new installer will also get flagged unless I sign & let windows know its the same application.
Microsoft recommended EV Certificate is expensive, there are some free alternatives for foss projects.. after looking at it the documentation requirement is huge though, lots of work, not sure if I want to spend time on it...will have to look into it later.
Some old discussion on it: MonoGame/MonoGame#3189
The text was updated successfully, but these errors were encountered: