

- #WINDOWS KEYSTORE EXPLORER SOFTWARE#
- #WINDOWS KEYSTORE EXPLORER CODE#
- #WINDOWS KEYSTORE EXPLORER DOWNLOAD#
- #WINDOWS KEYSTORE EXPLORER WINDOWS#
So the code for locating the JRE should be in the launcher, not in the installer. And I certainly don't want to reinstall all my Java applications just because I have switched to another JRE. Updating or switching Java runtimes after the installation is obviously not handled. It is not complete yet, but the next KSE release is still pretty far away.Īs I have said earlier, the installer is not the right place to search for JREs.

This is going to be the solution for the launcher issue for the next KSE release. However, a few comments above I have posted a pre-release version of the new KSE launcher. I do appreciate your efforts and did not mean to sound I really appreciate your efforts to improve KSE and at a later point in time I will certainly take a look at your Inno Setup installer. Regardless, thanks for the program - it's excellent and the loader issue is, in the end, a minor irritation at worst.

#WINDOWS KEYSTORE EXPLORER WINDOWS#
It would probably help the situation to include a basic command line in the "Running" section, along with a statement along the lines of "KSE can be run by simply launching the JAR or by using the Windows executable.
#WINDOWS KEYSTORE EXPLORER SOFTWARE#
The former is exact, the latter is a minimum.įor a while I was mistakenly under the impression that the loader was needed instead of being a mere convenience, and that the software require exactly that version. In my defense, I was believing the loader, which states, "This application requires a Java Runtime Environment 1.8.0", not "This application requires Java Runtime Environment 1.8.0 or later".
#WINDOWS KEYSTORE EXPLORER DOWNLOAD#
You just have to check the option to create the registry entry when installing AdoptOpenJDK as described on the download page.įair enough, though I already knew that from running it with JDK 15 using the -jar command line form. Would someone please explain to me what am I doing wrong and what this all mean?Īs always, I thank you all for your attention and time.Java 1.8 is the minimum version. I researched and read the part named "Key Pairs" (the "Generate Key Pair" topic and etc.), but unfortunately I could not solve this confusion. I know in the program itself comes with documentation. What I really want is to be able to create a key pair and from that pair generated I want to create a CSR. (Note that we have two fields, "subject" and "Issuer"…) But the funny thing is that when we create a keystore with a key pair with the keytool, we open the generated file with the KeyStore Explorer and the pair seems to have been signed by the creator himself, as a digital certificate, for instance: With the keytool, I believe we can create a key pair only. What does it mean? Am I creating a Digital Certificate signed by myself? And if I am, is there a way to create only a key pair? I was not supposed to create a pair, and from that create a CSR to send it to a Certificate Authority with CSR containing ( then) the details of the entity requesting the digital certificate (in case, me)? In this new screen, the program request the user to choose a signature algorithm, a validity period, and the name, where data from user entity's key pair must be filled. It is on this screen that comes some doubts. After choosing, key generation is made, and then a new window is displayed to the user with the strange name "Generate Key Pair Certificate": When we create a new key pair, we face a window which asks us to choose the algorithm used for the pair generation. However, the forum does not allow me to create new topics. I know that here may not be the appropriate place to make these types of questions, because the site owner of KeyStore Explorer has a forum.

I have some questions related to the use of this program. In my research, I found the KeyStore Explorer (V. I am developing a web application in Tomcat 7, and I must perform a secure exchange of data between client and server using TLS. I've been working with certificates, symmetric and asymmetric keys, and things related to web application security.
