I installed the TFS plugin (http://java.visualstudio.com/) for Android Studio but I can not connect to the server. Any extra ideas? Thank you!
evidence image
This error can be interpreted to be the result of self-signed certificate. If the certificate in use is Self-signed or any other certificate that is private to the internal network.
Java doesn’t trust such certificates and for which, we can import the cert into the trust store and make it to work.
The link explains how the certificate import works in a Linux machine
(which is also applicable for Windows).
the “keytool” is under “\bin\keytool.exe”, and
the “cacerts” trust store is under
“\jre\lib\security\cacerts”.
should be the jre/jdk installation used by IntelliJ.
This should have resolved the above TFS connectivity failure.
Reference this article: Error: SSL certificate problem: unable to get local issuer certificate
And this thread: How to properly import a selfsigned certificate into Java keystore that is available to all Java applications by default?
Related
SO!
We're developing a desktop app for Windows and using *.pfx Code Signing certificate from GlobalSign for signing code after compiling.
Now we have also started developing and building this app in Linux for Linux-based systems.
Does Linux have the similar trust systems for apps as Authenticode for Windows? Are there any CA such as GlobalSign?
From my search i only found that Linux devs either use self-signed certs (assuming themselves as CA), or trying push their apps to large soft repos such as HomeBrew., that signed them automatically.
From there: Code Signing for Linux.
And from there: Authenticode or other code signing for Mac and Linux.
That's Linux authenticate code by validation binaries once while installing the package. The package (e.g. RPM) contains a cryptographic signature that must match the contents of the files or the installer will refuse to install. But what is exactly this crypto signature and how to take this sign?
Thanks in advance!
It gives This site can’t be reached fabric-service-url.com unexpectedly closed the connection. error.
I am using Mac computer.
Accessing the url from Chrome.
The certificate comes from the *.pfx translated *.pem.
In my case I solved this by deleting the previously installed Service Fabric certificate from the certificate store on my laptop, rebooting, installing the certificate again (on Windows 10: double click the .pfx file, next, next, finish) and rebooting again.
When I create and run a WebApi .NET Core project, I get an untrusted certificate error in Chrome.
I read https://www.hanselman.com/blog/DevelopingLocallyWithASPNETCoreUnderHTTPSSSLAndSelfSignedCerts.aspx and tried dotnet dev-certs https --trust but this option is missing on Linux:
On Linux there isn't a standard way across distros to trust the certificate, so you'll need to perform the distro specific guidance for trusting the development certificate.
How can I make Chrome on Linux trust the cert?
I used this article to solve your problem. I hope you will resolve your problem.
I am using Couchbase client inside my asp.net web mvc project (i downloaded the dll files from here)
I have a Couchbase Server installed on Windows Server 2012 x64.
When developing the project, everything works as expected. When i publish the website on the server, i get this error:
Could not load file or assembly 'Enyim.Caching' or one of its dependencies.
Strong name signature could not be verified.
The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
I am stuck! i have also tried this answer, but with no effect.
What can i do?
There was a problem with the 1.2.2 build (signing related). There's a fix posted to http://packages.couchbase.com/clients/net/1.2/Couchbase-Net-Client-1.2.3.zip (NuGet is also updated). I'll investigate as to why the site doesn't have the new links. Apologies for the confusion.
I have a signed midlet (VeriSign Class 3), which runs perfectly in several Nokia devices.
When I try to run it on the JME SDK 3.0 emulator it produces a java.lang.SecurityException: Application not authorized to access the restricted API.
It has all the permission it needs, otherwise wouldn't work on the devices.
It worked perfectly without the signing, but it's a pain in the neck to click an unclick everytime I compile, depending if I'm running the midlet on the device or on the emulator.
And well, I had to install the VeriSign CA Class 3 certificate on the emulator, in order to recognize the signature. I don't know if the problem is about this certificate, but without it the emulator wouldn't even start the application cause the CA was unknown.
Has anybody some experience with signatures and this JME SDK emulator?
Solved by using a newer version of the emulator (Java Wirelesss Tollkit 2.5.2)