Details
-
New Feature
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
2.36.0
-
customfield_11100 31859
-
CP: sprint 89, CP: sprint 90
-
2
-
Core: Platform
Description
Okapi 2.36.0 is not able to talk to a PostgreSQL server that enforces SSL communication. Although a dedicated VLAN can be used for communication of this type, a single error or bug in the network setup can severely impact query privacy in this scenario, including exposure of database (login) information to a sniffing attacker. Defense in depth -> use everything that secures confidentiality and security of communication and hampers a potential adversary, so even crushing 0day exploits are highly unlikely to compromise the setup.
All vert.x PostgreSQL clients have SSL/TLS disabled by default:
https://vertx.io/docs/vertx-mysql-postgresql-client/java/#_configuration
https://vertx.io/docs/vertx-pg-client/java/#_using_ssl_tls
It checks the server certificate (sslmode=verify-full) to prevent man-in-the-middle attacks (FOLIO-2412): https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION
Enable TLSv1.3 only. If there is a need to support older protocol versions (that are not state of the art and violate GDPR) we can add them later.
TestRail: Results
Attachments
Issue Links
- is blocked by
-
OKAPI-854 Json-configured database user postgres_user not honored
-
- Closed
-
- is cloned by
-
RMB-546 Support TLS/SSL connections to Postgres
-
- Closed
-
- is duplicated by
-
FOLIO-2406 SSL/TLS, SCRAM-SHA-256, migration to PostgreSQL 10 (or higher)
-
- Closed
-
- relates to
-
FOLIO-1134 Secure public AWS instances
-
- Open
-
-
OKAPI-788 Upgrade to Vert.x 4.0 milestone 4
-
- Closed
-
-
OKAPI-792 PostgreSQL SSL CA Certificate configuration option
-
- Closed
-
-
FOLIO-2412 Clients should verify PostgreSQL SSL/TLS server certificate
-
- Blocked
-
-
OKAPI-861 Unit test PostgresHandleTest fails if Docker is unavailable
-
- Closed
-
-
OKAPI-888 Test warning: Corrupted STDOUT by directly writing to native stream in forked JVM 1.
-
- Closed
-