Skip to content

Conversation

PeggySchmidtMittenzwei
Copy link
Contributor

Comment on lines 3 to 5
## Problem

You can disable the Security Manager by setting NOSECURITY=YES in the JDBC driver configuration, as shown in the following example:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is not a problem, but a solution to the problem.

…e-impact-of-disabling-it.md

Problem => Question

## Recommendation

To ensure security, always download the Exasol JDBC driver from an official and trusted source. After downloading, verify the checksum to confirm the file’s integrity and that it hasn’t been tampered with.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is less about the Exasol JDBC driver, but about JDBS drivers required by virtual schemas and the IMPORT command.

…JDBC-driver-and-the-impact-of-disabling-it.md

Co-authored-by: Christoph Pirkl <[email protected]>
Copy link
Contributor

@allipatev allipatev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a couple of suggestions.


Setting the NOSECURITY flag to YES disables Java Security Manager, allowing function calls without additional checks.

The Java Security Manager provides detailed control over which functions are permitted to run in your environment. However, configuring these settings can be complex and time-consuming. In the past, we tried to whitelist only the functions that JDBC drivers required. However, because the drivers frequently change and add new functions with each update, maintaining an accurate whitelist soon became impractical—especially since ExaLoader would then require a comprehensive list covering all functions for all drivers.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While that's true in general, for the latest occurrences JDBC connection that IMPORT tried to establish just hung until one disables Security Manager. So we had no exception stating which class / method wasn't allowed so we had no particular item to whitelist.

So it's not only time consuming (many third party drivers) and in vain (because the component is deprecated by Java platform), but also simply not always possible. This aspect might show us in even better light, so maybe you can adapt the article accordingly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants