In recent years it has become impossible to have a downloadable windows app without using an SSL cert to sign your install executable so that Windows SmartScreen doesn't put up warnings (and even delete the file) when clients download it.
There are two types of SSL certs that you can use:
A regular Cert which can be for either a company or an individual.
An EV Cert, which costs 3x as much and can only be issued to a company.
The problem with the regular cert is that is doesn't immediately get you past SmartScreen. You have to "build your reputation" first... which I believe means you have to have enough people download your product (possibly downloading it specifically with Microsoft Edge browser) that they start to believe you are not a virus maker or some such thing.
The problem is, I cannot find any guidance anywhere on how long it takes to build a "reputation". 10 downloads? Easy 50 downloads? Sure. 10000 downloads? That would require spending a lot of money on an advertising campaign that would not convert.
Does anyone have any experience that could help narrow this range down?
Related
Recently I have had a rather disturbing issue. Seemingly at random I get err_cert_authority_invalid errors from various websites which goes away after about 15 minutes. This is particularly bad for me because one of them is discordapp.com and the discord application suffers the same problem shutting down my ability to use discord at all. The nvidia driver site also had the same problem. I tried this on Chrome, Firefox, and Edge and got the same issue with all three browsers. As far as I know the only cause for this error is when a certificate is signed by an untrusted authority.
Upon examining the certificate data, this is what I discovered:
During the issue
Issuer: Cisco
Issued to: discord.com
Expiry: duration of the cert is only about five days but the current date is always within that five day range
After the issue passes
Issuer: COMODO
Issued to: ssl764977.cloudflaressl.com
Expiry: From May 2020 to End of November 2020
As far as I can tell, they aren't self-signed because issuer and issued-to are different. The expiration date has not passed. The only conclusion is that the issuer isn't trusted. Sadly I don't remember the before/after for the nvidia site (when it happens again, I'll get screenshots).
I was concerned that I may have a virus so I made sure that wasn't the case by doing a full reformat of my computer (it was due for one anyway). The issue still arises. Furthermore, I tried using my laptop and it doesn't experience this issue, although I only tried my laptop for a short time so maybe this intermittent problem just didn't trigger. The only thing I can think of that can be causing this is a Windows security update, but then you would think my google fu would find evidence of others experiencing the same problem right now, which it doesn't. Although there are countless similar issues from various times over decades. How can I discover the source of this problem in an effort to fix it? The problem is occurring a couple of times each day now.
For reference:
Windows 10 x64 build 1909 (No updates required)
Chrome 86.0.4240.111
Firefox 82.0
Microsoft Edge 44.18362.449.0
I have included screenshots of the traceroutes and certs here
Edit 1: Changed causes for error to only the one the comments suggested was the problem.
Edit 2: Included link with screenshots
I think I found the cuplrit. It is my workplace VPN, I forgot to disable it because it just sits hidden in my system tray and it was wreaking havoc with my DNS lookups.
Hello stackoverflow community. I am asking for help with downloading dvd covers from a dvd shop website (dvdempire.com). I am using wget for Windows.
So the syntax would be wget -r -A .jpg https://www.dvdempire.com/all-movies.html
But the problem is that it doesnt want to connect with SSL. The handshake fails.
Maybe the website has disabled mass downloading of DVD covers because of bandwidth or copyright reasons ?
The covers can be manually downloaded by clicking each link, but it would be much faster to do it with a batch program.
There are some 115000 covers in total.
The Terms of Use page for the site includes the following:
"Read these terms carefully before you ("You") accept these Terms by: (a) placing an order through DVDEmpire or (b) otherwise using the Websites."
"You agree, further, not to use or attempt to use any engine, software, tool, agent or other device or mechanism (including without limitation browsers, spiders, robots, avatars or intelligent agents) to navigate or search the Websites other than the search engine and search agents available from DVDEmpire on the Websites and other than generally available third party web browsers (e.g., Netscape Navigator, Microsoft Explorer)."
I suggest that you contact the site maintainers directly about what you want to do.
We deployed a one-click App (C#/.Net) to the local network around a year ago and using a Commodo Code Signing Certificate had zero problems.
The certificate expired a couple of weeks ago so we renewed it, deleted the old cert from Visual Studio (2017 Pro), imported the new certificate and compiled for a new update, published in exactly the same way we've been doing for the last year.
However, when users update this app (and all others we've written) it's tripping the Windows 10 "SmartScreen prevented an unrecognized app from starting" dialog so users are calling support.
When we click on 'more info' it's correctly showing the publisher's name from the certificate.
I called Commodo who were completely unhelpful and said it's a "Microsoft problem" and there is nothing they or we can do about it, which makes a very expensive certificate worthless.
I also looked online and saw other people were also running into this problem but can't find any solutions.
1) Is there anything I could have done wrong in vS2017 when replacing the certificate?
2) Is there anything I can do to 'fix it' to prevent every single employee's PC displaying this dialog every time we do an update for our signed app?
The app is deployed to an SBS 2011 server on the local network and is installed from \\192.168.0.250\Install\Setup.exe (this is what the network admin wanted).
I was recently given a VB.NET project for fixing some bugs and creating an installer for it. I was told to use Install Shield LE.
All went well with creating the install script but Windows 8 is giving me a smart screen warning when downloading the application from a web site and trying to install it.
I am aware of Windows 8 policy where popular applications get more "trust points" and become popular but the application is targeted for a fairly small audience of people therefore we can not rely on this option. Even more, people without proper knowledge would be repelled by the warning message and that could cause MS to never raise the trust for the application.
My question is, do I have to sign both - the application and the installer with a certificate? If so how do I sign the installer, as there is a signing tab for the project but I can't find one for the installer.
Bonus points if anyone can tell me if acquiring a proper certificate will remove the warning message telling this isn't a commonly downloaded file and might be dangerous from chrome/IE when downloading the application. There are many threads about this, I know, but most of them suggest adding the site to webmaster tools but that hasn't helped and we're still receiving the message
Thanks.
If I have read your post correctly then you are talking about an application as opposed to a website, and for that you would need a code signing certificate. Certificates that sign websites are different so first and foremost decide what it is that you are producing and want to sign.
Having decided that then you need to decide who you will use to supply your certificate. Typical sources would be VeriSign, Thwaite or Globalsign to name but three. All charge different prices but essentially do the same thing.
Once you have the certificate then the installer that you use to build your application signs the code files you select and the actual installer (msi or exe) itself.
That should eliminate the message that you now see warning people about potentially dangerous files that they are about to download.
I cannot stress enough however that you need to be clear about which type of certificate you need BEFORE you go ahead and buy one. I think from your description you are talking about a code signing certificate but do check first.
Following CAB forum regulation you will need to have an Extended Validation code signing in order to bypass the smart screen filter.
Extended Validation code signing will establish immediate trust with the machine, as you go through a more stringent validation process to obtain it! (or at least that's the rationale behind it!)
I think you can get an extended validation code signing either from SYmantec or GLobalsign.
I want to develop an app using Adobe AIR. But I have to sign it using a code signing certificate. I don't wan to buy a code signing certificate. Would it be OK if I distribute my app with a self-signed certificate?
The only difference between using a real certificate and a self-signed certificate is what the user sees in the initial installation dialog. With a real certificated they'll see a yellow "!" and the app will shown to be of "KNOWN" origin, and your company name will be shown. With a self-signed cert, there will be a red "?", and it will say the app's publisher is "UNKNOWN". You can see samples of the two dialogs at the very bottom of this page.
So realistically, it comes down to whether you're okay with people seeing a scary warning at install time. If you're only offering up the apps as a "use at your own risk" thing, or the app will be used mainly by a small group of people who already know who you are (an internal company app, e.g.) that may not be an issue, but if you hope for random internet people to come use your app and trust it, a cert may be a good idea.
That depends on your definition of "OK", but most likely no.
A self-signed certificate will not have been issued by a trusted CA, and your certificate will be considered untrusted by the client. I don't think (but have not tested) that the user is actively prevented from installing an app with an untrusted certificate, but they would at least get a warning, and that doesn't give your user a good first impression of your app.
If it's just for yourself or for a small group of people who know and trust you, then a self-signed certificate is most likely not a problem, but if you're distributing it to the world, you will almost certainly prefer a proper certificate.
I have recently looked into developing an Air App for the company to distribute to customers. On OSX Mavericks - on my mac and my designer's mac a red warning signs pops up stating that we are an unknown publisher - This was using the self signed certificate. The whole process was clunky with the installation, I had to verify that we were legitimate, as this warning sign inferred we were a looking to distribute something underhand.
From a marketing perspective this looked terrible.
In addition to this I managed to find someone to test the whole process of downloading the air app with a self signed cert on windows with an 'average' amount IT skills and this is what they said:
"Nah I didn't download it... it looked like it wanted to put a virus on my computer." And that is where download ended.
Currently we are looking to get some seal of trust on the application for distribution purposes.
Verisign, Thawte look interesting, although costly.
http://www.symantec.com/code-signing/adobe-air
https://www.thawte.com/code-signing/
Or read this page for more information
http://help.adobe.com/en_US/air/build/WS5b3ccc516d4fbf351e63e3d118666ade46-7ff0.html