JCAppStore v2.0

With new installers, JCAppStore 2.0 brings better behaviour and intuitivness.

What's new:

• installers via InstallBuilder
• new store signature key

More detailed description will be included later.

How to install

For detailed information, see our wiki. There still might be some issues with installers. In that case, please, let me know.

For the best behaviour, we recommend Java JDK from Oracle. The installer (except for Linux) uses Java Liberica, which is easier to install and more user-friendly but the images are rendered with artifacts. Oracle's JAVA installer is almost impossible to download automatically (login and conditions agreement are required, the latter stored in cookies and impossible to avoid easily).

Known issues (will be fixed ASAP):

mac: the installer is not well tested as we don't have a machine to try it on, it might work but we recommend you build the store by yourself

Download an installer for your platform:

• windows: only 64bit installer
• linux: both 64bit and 32bit installers
• mac: osx installer
• other (requires BASH): use tarball

Each file includes .sig signature file to verify the installer integrity.

In case you want an installer for your platform (ARM processors LINUX, Solaris, FreeBSD...) please, let me know.

JCAppStore v1.3

JCAlgTest integration: testing, sharing results, and automated applet support verification! Due to WebView inclusion, Java 11 JDK is newly required: https://www.oracle.com/cz/java/technologies/javase-jdk11-downloads.html

Changelog:

• java 11 and JavaFX 11 introduction due to better applet info description visuals (small WebView integration for nice HTML display)
• minor buildscript fixes (UNIX scripts, Gradle wrapper to v 6.3, exclude sources from .jar when not read from there)
• GUI store design (and layout manager fix)
• store separation to 'recommended' and 'advanced'

** NOTE **
Due to a stupid typo, the application will fail to run when the store is not downloaded (which is the case of a fresh install). If you want to (for some reason) download this version, first, download store content and place its files into JCAppStore folder in your user home into store folder (if you run the application the JCAppStore folder will be created, just paste the repo contents into a new store folder inside).

---

Signature files not yet included (sorry, forgot the key password 😄 ) - will try to do that later. But still, you can also build the app by yourself.
Mac users are still required to build the ap by themselves (at best, java uses mac-specific look and feel - uncomment these lines in the class extending jframe - search for todo comments). Will try to publish mac-specific distributions in the future :)

Installation guidelines

Windows

Just double-click JCAppStore-1.3-win.exe file and install the store.

You can use GnuPG to verify the .exe.sig detached signature. The signature key is available in this repository (installer-unix/store.asc for example).

Debian/Ubuntu

Install the .deb package with sudo dpkg -i jcappstore_1.3-1_all.deb. Please, don't double-click install, run the command instead. Once installed, run sudo jcapp. It is because you don't have the rights to run the file as it belongs to root. This first run will just do some necessary setup and exits. It will prompt you whether to import our public key and also it changes the rights. Then, run just jcapp command.

For the .deb package creation, a different key (jcappstore_1.3-1_all.deb.asc) was used as it had to be generated on a Unix machine (and I was lazy to re-import the key, see assets in https://github.com/crocs-muni/JCAppStore/releases/tag/v1.0).

Unix generally

1. Download the tar ball for UNIX from the latest release and extract it.
2. Decide on where to put the application data. We recommend to choose folder such as: /usr/share/java
3. Inside your selected folder, create another folder called JCAppStore and move here all files from the package except launcher.sh file.
4. Modify launcher.sh file: set DIR=path_to_the_sources. For example: DIR=/usr/share/java/JCAppStore
5. Put the launcher script anywhere you like and launch the app with it. You can put it inside /usr/bin folder so that it is visible from anywhere and rename it conveniently (jcapp, for example). You may have to set executable rights to the launcher as follows: chmod u+x launcher.sh. It is up to you where the script is located and how the application will be launched.
   All you need to do is execute the shell script.

You can use GnuPG to verify the tar detached signature. The signature key is available in this repository (installer-unix/store.asc for example).

JCAppStore v1.2

JCAlgTest integration: testing, sharing results and automated applet support verification!

Changelog:

• minor error fixes (metadata for packages was ignored due to the previous fix that preferred package instances with modules only for example)
• implementation of JCAlgTest support - auto applet installation, results sharing, algorithm support checking
• JCAlgTest results finding - either from test results or online on JCAlgTest GitHub repository
• build.gradle: automated windows .exe generation

Installation guidelines

Windows

Just double-click JCAppStore-1.2-win.exe file and install the store.

You can use GnuPG to verify the .exe.sig detached signature. The signature key is available in this repository (installer-unix/store.asc for example).

Debian/Ubuntu

Install the .deb package with sudo dpkg -i jcappstore_1.2-1_all.deb. Please, don't double-click install, run the command instead. Once installed, run sudo jcapp. It is because you don't have the rights to run the file as it belongs to root. This first run will just do some necessary setup and exits. It will prompt you whether to import our public key and also it changes the rights. Then, run just jcapp command.

For the .deb package creation, a different key (jcappstore_1.0-1_all.deb.asc) was used as it had to be generated on a Unix machine (and I was lazy to re-import the key, see assets in https://github.com/crocs-muni/JCAppStore/releases/tag/v1.0).

Unix generally

1. Download the tar ball for UNIX from the latest release and extract it.
2. Decide on where to put the application data. We recommend to choose folder such as: /usr/share/java
3. Inside your selected folder, create another folder called JCAppStore and move here all files from the package except launcher.sh file.
4. Modify launcher.sh file: set DIR=path_to_the_sources. For example: DIR=/usr/share/java/JCAppStore
5. Put the launcher script anywhere you like and launch the app with it. You can put it inside /usr/bin folder so that it is visible from anywhere and rename it conveniently (jcapp, for example). You may have to set executable rights to the launcher as follows: chmod u+x launcher.sh. It is up to you where the script is located and how the application will be launched.
   All you need to do is execute the shell script.

You can use GnuPG to verify the tar detached signature. The signature key is available in this repository (installer-unix/store.asc for example).

JCAppStore v1.1

Changelog:

• CSS fix for code class
• remove data field logging from APDU transmissions
• signatures now use both fields from JSON data (before, signature filename and key fingerprint were one value, now file name depends on the author, whereas fingerprint is independent value)
• general error handling on card action - will not block the GUI with endless 'working' message
• other minor graphics/error messages updates

Installation guidelines

Windows

Just double-click JCAppStore-1.0-win.jar file (if it asks for a program to run with, use java, usually installed in C:\Program Files\Java\jre_[version]\bin\java.exe) and install the store.
Or, you can run java -jar JCAppStore-1.0-win.jar from a command line if you like.

You can use GnuPG to verify the .jar detached signature. The signature key is available in this repository (installer-unix/store.asc for example).

Debian/Ubuntu

Install the .deb package with sudo dpkg -i jcappstore_1.0-1_all.deb. Please, don't double-click install, run the command instead. Once installed, run sudo jcapp. It is because you don't have the rights to run the file as it belongs to root. This first run will just do some necessary setup and exits. It will prompt you whether to import our public key and also it changes the rights. Then, run just jcapp command.

For the .deb package creation, a different key (jcappstore_1.0-1_all.deb.asc) was used as it had to be generated on a Unix machine (and I was lazy to re-import the key).

Unix generally

1. Download the tar ball for UNIX from the latest release and extract it.
2. Decide on where to put the application data. We recommend to choose folder such as: /usr/share/java
3. Inside your selected folder, create another folder called JCAppStore and move here all files from the package except launcher.sh file.
4. Modify launcher.sh file: set DIR=path_to_the_sources. For example: DIR=/usr/share/java/JCAppStore
5. Put the launcher script anywhere you like and launch the app with it. You can put it inside /usr/bin folder so that it is visible from anywhere and rename it conveniently (jcapp, for example). You may have to set executable rights to the launcher as follows: chmod u+x launcher.sh. It is up to you where the script is located and how the application will be launched.
   All you need to do is execute the shell script.

You can use GnuPG to verify the tar detached signature. The signature key is available in this repository (installer-unix/store.asc for example).

JCAppStore v1.0

This is the first fully functional release. Though next releases might come early because the JCAppStore content repository is signed with a test key (until we decide on how to manage the store key).

Windows

Just double-click JCAppStore-1.0-win.jar file (if it asks for a program to run with, use java, usually installed in C:\Program Files\Java\jre_[version]\bin\java.exe) and install the store.
Or, you can run java -jar JCAppStore-1.0-win.jar from a command line if you like.

You can use GnuPG to verify the .jar detached signature. The signature key is available in this repository (installer-unix/store.asc for example).

Debian/Ubuntu

Install the .deb package with sudo dpkg -i jcappstore_1.0-1_all.deb. Please, don't double-click install, run the command instead. Once installed, run sudo jcapp. It is because you don't have the rights to run the file as it belongs to root. This first run will just do some necessary setup and exits. It will prompt you whether to import our public key and also it changes the rights. Then, run just jcapp command.

For the .deb package creation, a different key (jcappstore_1.0-1_all.deb.asc) was used as it had to be generated on a Unix machine (and I was lazy to re-import the key).

Unix generally

1. Download the tar ball for unix from the latest release and extract it.
2. Decide on where to put the application data. We recommed to choose folder such as: /usr/share/java
3. Inside your selected folder, create another folder called JCAppStore and move here all files from the package except launcher.sh file.
4. Modify launcher.sh file: set DIR=path_to_the_sources. For example: DIR=/usr/share/java/JCAppStore
5. Put the launcher script anywhere you like and launch the app with it. You can put it inside /usr/bin folder so that it is visible from anywhere and rename it conveniently (jcapp, for example). You may have to set executable rights to the launcher as follows: chmod u+x launcher.sh. It is up to you where the script is located and how the application will be launched.
   All you need to do is execute the shell script.

You can use GnuPG to verify the tar detached signature. The signature key is available in this repository (installer-unix/store.asc for example).

User experience test release

Test release containing windows installer.

Do not use this release - there are performance bugs. This release was solely for testing purposes.

The installer cannot opt for import gpg key (e.g. key is imported allways). The installer cannot install GnuPG dependency, it supposes the gpg is already present and its PATH env set.