Currently integration tests only use unencrypted connections. We need to make sure that BFSC also works with bfss:/ URLs and TLS encrypted connections to the database.

That's why we need to add integration tests that use TLS. See also #31

Preconditions

Docker-db by default does not enable TLS for Bucketfs, see this default /exa/etc/EXAConf (for both Exasol 7.1 and 8):

[BucketFS : bfsdefault]
    Owner = 500 : 500
    # HTTP port number (0 = disabled)
    HttpPort = 2580
    # HTTPS port number (0 = disabled)
    HttpsPort = 0

That's why we need to update https://github.com/exasol/exasol-testcontainers/ to allow enabling TLS, see exasol/exasol-testcontainers#234

After exasol/bucketfs-java#57 is implemented class ListingProvider can be removed

Dependencies

• exasol/bucketfs-java#57

When pointing the client to a non-existent endpoint, the resulting error message needs a lot of interpretation:

#> java -jar bfsc-2.1.0.jar ls -pw bfs://localhost:2580/blah/
Password for reading from BucketFS: 
E-BFSJ-5: I/O error trying to list 'http://localhost:2580/blah'. Cause: null

Update broken links checker

The link to the Dependencies in the README is broken.
This is the link target: https://github.com/exasol/bucketfs-client/blob/main/dependencies.md

Uploading a file from the current working dir with the following command fails:

$ bfsc cp --profile default retail-mini-mapping.json bfs:/default/
Cannot invoke "java.nio.file.Path.relativize(java.nio.file.Path)" because "this.sourceRoot" is null

Workaround

Specify a relative path ./ to the file:

bfsc cp --profile default ./retail-mini-mapping.json bfs:/default/

I can't find any mentions of the prerequisites for running the bfsc. With which java versions is it compatible? Does it need other prerequisites? How do I install it?

I was not able to run the application from the terminal on macOS Monterey,
maybe this option also needs to be explained better.

Signing for macOS binaries will not be possible in near future.

Until then the macOS binaries should be removed

• from releases
• and documentation

Acceptance Criteria

• Users can copy a local file to a bucket
• Users can copy a file from a bucket to the local file system

If I run the following command

java -cp bfsc-0.1.0.jar com.exasol.bucketfs.client.BucketFsClient cp -p bfsc-0.1.0.jar bfs://localhost:6666/default/test1/

it produces the following error

E-BFSJ-1: Unable do upload http://localhost:6666/test/bfsc-0.1.0.jar. HTTP status 400.

If I instead run the following command where I doubled the bucket

java -cp bfsc-0.1.0.jar com.exasol.bucketfs.client.BucketFsClient cp -p bfsc-0.1.0.jar bfs://localhost:6666/default/default/test1/

It is afterwards available at http://localhost:6666/default/test1/bfsc-0.1.0.jar

When downloading the Windows binary Chrome and Edge display a warning that it is a potential risk.

I suggest that we inform about this issue in the documentation and explain that the file is safe. Firefox does not bother though.

When executing the jar with -jar option it fails because of a missing main manifest attribute.

% java -jar target/bfsc-0.2.0.jar 
no main manifest attribute, in target/bfsc-0.2.0.jar

Add underlying cause to the official error messages when available

tn@hw4122:~$ ./bfsc-linux_x86 --help
./bfsc-linux_x86: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by ./bfsc-linux_x86) 

Currently we cannot provide native binaries for other platforms.
The reported issue will be added as known issue to the documentation.

1. Markup for the hyperlink near "SuSE: OpenJDK build of the Leap project" is seemingly broken.
2. The tool seems to have quite a wide set of requirements. In my Ubuntu 22.04 running in a VirtualBox VM (host system is Windows 11) it's failing with

alex@alex-VirtualBox:~$ /home/alex/Downloads/bfsc-linux_x86 ls bfss://localhost:2581/default
The current machine does not support all of the following CPU features that are required by the image: [CX8, CMOV, FXSR, MMX, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, POPCNT, LZCNT, AVX, AVX2, BMI1, BMI2, FMA].
Please rebuild the executable with an appropriate setting of the -march option.alex@alex-VirtualBox:~$

3. A trailing newline after the error message above would be useful.
4. It is not crystal clear from the User Guide if the native executable supports "Linux" or "Ubuntu Linux".
5. Again to wide system requirements, on Rocky Linux release 8.9 (Green Obsidian) the tool fails with

$ ~/Downloads/bfsc-linux_x86 bfsc ls bfss://localhost:2581/default
<path>/bfsc-linux_x86: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by <path>/bfsc-linux_x86)
<path>/bfsc-linux_x86: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by <path>/bfsc-linux_x86)

For release 1.1.2 this is Ubuntu 22.04 with glibc 2.32.

Maybe one can refresh this part (the latest version is 2.0.0)?

7. "Retrieving the Password" section.
   /exa/etc/EXAConf is not a publicly available interface. Luckily, one can use ConfD job bucketfs_info.

BFSC is currently delivered as an executable JAR that requires installing a JVM for running. We should build and deliver a native executable for macOS, Linux and Windows so that users don't need to install a JVM for running BFSC.

Acceptance Criteria

1. An executable for macOS, Linux and Windows is uploaded to the release page (in addition to the jar)
2. Integration tests verify that the executable works on all three platforms
3. User guide describes how to use the executable

See exasol/parquet-edml-generator#20 for an example

• Enable BFSC to display its version with command line option --version or `-V´
• Add native images to documentation: user guide, readme (optional)

See exasol/bucketfs-python#33

• org.apache.commons:commons-compress:jar:1.22 in test
  • CVE-2023-42503, severity CWE-20: Improper Input Validation (5.5)

Connection to Exasol v8 fails, even when specifying bfss://....
Also when entering a TLS port in config.ini BFSC still connects unencrypted (http), not TLS (https).