When I install my application on Win7, Windows shows installation dialog saying 'Unknown Publisher'. What should I do to get rid of it?
Simply: you need a certificate from the certification authority and sign your binary. The certificate AFAIK is not for free and it is time-limited. For details see this answer.
Related
I am working on an Angular project on a SharePoint 2013 site. When using the console window in IE 11, I see 75 warnings like this:
SEC7132: The certificate protecting this web site uses weak cryptography,
SHA1. The web site should replace this certificate with a SHA2 certificate
before SHA1 is no longer allowed.
Now, please accept the premise that I have no control over my admins and I cannot force them to fix the certificate. I can't make the SOURCE of this warning go away.
I know I can disable showing all warnings. But I can't assume that my code will only generate errors, I will still have some warnings I want to see. How can I suppress a specific warning in the console?
You cannot. It has nothing to do with your code. It is Internet Explorer telling you on each request that the web server certificate using for the SharePoint zone you are hitting (IIS website) is using an obsolete and insecure algorithm. So best thing you can do, is make your admins aware they have some work to do :)
https://technet.microsoft.com/en-us/library/security/4010323.aspx
I just downloaded the latest version of xCode (9.0 beta (9M136h)).
However, when I try to make a request to my server in iOS 11 simulator (Using NSURLConnection sendAsynchronousRequest), an error is received:
NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9807)
NSURLConnection finished with error - code -1202
NSError object contains the message - #"NSLocalizedDescription" : #"The certificate for this server is invalid. You might be connecting to a server that is pretending to be “***” which could put your confidential information at risk."
The plist contains:
<key>NSAppTransportSecurity</key>
<dict>
<key>NSAllowsArbitraryLoads</key>
<true/>
</dict>
so it is not the problem in this case (I guess)
Needless to say that it is working in iOS 10/9/8
Any suggestions?
Thanks in advance!
You need to allow your application to run HTTP (no S) connections. By default, Apple only allows HTTPS:
go to your info.plist
then press the plus icon on any of them
Search for "App Transport Security Settings"
click the little arrow to the left and find "Allow arbitrary loads", by default it is set to "NO" change it to "YES"
For all of you who get this error in iOS 11, please make sure you're working against valid (secured) certificate in your server.
In our case, the certificate wasn't strict enough.
Once our server guy integrated new valid certificate, the problem has gone.
One way to check if the certificate is secured, is to past the problematic link in the browser.
As a result, you might see that the connection is not secured:
Since you've got an invalid certificate error, I'll make the following suggestion based on my personal security practice.
If you're still in your servicing terms with your CA, ask them to issue a new valid certificate for you.
Check your Keychain setting and make sure no CA cert is missing.
Alternatively, you can issue your own self-signed certificate for testing purposes, and add it to your local Keychain as trust anchor. A search for "how to create self-signed x509 certificate" will return something you might find useful.
The apps is working fine in debug and throw error when I try to build it.
I have already regenerate certificate and provisioning profile, but nothing seems works.
I have gone through all answer for code sign error in here but also no solution.
How to fix this?
Go into your project Build Settings and make sure Provision Profile is set to "Automatic" and that Code Signing Identity is configured with the right certificate for debug and release.
Now, if you have the correct provision profile and certificate you should not have any issues...
I maintain a large WPF application which I inherited from another developer. I use ClickOnce to publish it. Suddenly, today I got an error message:
Error 2 Cannot publish because a project failed to build. 1 1
Error 3 An error occurred while signing: Failed to sign bin\Debug\app.publish\setup.exe. SignTool Error: No certificates were found that met all the given criteria.
I do have a file called SomeName.snk, which is referred in project settings, Signing tab. I have no idea what happened today that caused the problem.
I use VS 2012.
Go to main project properties > Signing > If the expiration date is over > click on Create Test Certificate, password is not mandatory, and you're done.
I'd check whether the certificate expired. Most (all?) certs have an expiration date.
I got this problem installing visual c++ on top of a VS2017 .net install. I solved it by unchecking Properties -> Security -> Enable ClickOnce security settings.
It then created an app.manifest file. After that the error went away. Interestingly enough, I checked it again to see what would happen and the problem did not come back.
Did you check for the certificate?
View or manage your certificates
You can use the MMC Snap In or Internet Explorer.
Go to main project properties > Signing > Select from Store...
Click certificate properties
And install certificate
Go to Main project (Startup Project) and right click > properties
Then go to Signing
Then unchecked "Sign the ClickOnce manifests"
It's work for me.
This happens mostly if your certificate for that particular project has expired or has some issues.
Right Click Project -> Properties -> Signing Tab -> More Details button -> Shows your certificate details. Check if your certificate has expired
Ways to Fix
1. Un-check the "Sign the ClickOnce manifests" and try
2. Extend the Certificate by creating a Test Certificate (If your certificate is expired)
Hit "Create Test Certificate..." button
Enter your credentials (Not mandatory)
Save
3. Re-validate your existing certificate (If your certificate is not expired)
Hit "Select from file" button and use your existing key file (eg. .pfx)
OR
Hit "Select from Store" button and select from the available options
Tip: If you still face issues building the project. Just restart your
Visual Studio.
Hope that helps.
I had this same issue and I was able to solve it by removing or changing the timestamp server URL. After removing that, the project was able to build successfully.
I just ran into the problem today. In my particular case, it was caused by this Microsoft Windows Update.
I uninstalled that update and publish began working as it always had. This is only a temporary work around and means you should probably regenerate your keys/certificates.
In my case, the cert was not expired and none of the other solutions worked (restarting VS, using a temp test cert, restarting computer, etc.)
The issue was resolved by deleting my output directory and rebuilding.
Simple Clean sorted it for me.
Build - Clean Solution
In my situation I had many projects in the solution, so I browsed to the non-startup project and:
Go to main project properties > Signing > uncheck the Sign the ClickOnce option
Using Visual Studio 2019
When trying to sign in using the button in the lower left corner of the screen, I am unable to do so because it needs a verification code. However, I am not offered the chance to receive one, it only brings me directly to the "allow this application page." The exact error in the log is
Could not sign in. Make sure that you entered the correct verification code.
Thanks for your help in advance.
I had the same issue, resolved by changing network settings as follows:
In Eclipse:
Preferences > General > Network Connections
Set Active Provider to Manual
Under Proxy entries, edit the HTTPS proxy, adding host and port info
Check "Requires authentication" and add your network ID and password
I had a similar problem on my Mac OS X.
However, after upgrading my JDK from 1.6 to 1.7 my problems disappeared.(Note: JDK not JRE)
The default java on Mac 10.x is Java SE 6 and you can't uninstall it. You can add Java 1.7 or higher and your system should automatically pick up the later version -you can check from the terminal with
$java -version