You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This request is not based on a problem, but on what I feel is a shortcoming of the system. Encrypted connections would make it safer to store confidential data in SiriDB and also prevent plain-text passwords from flowing across the wire.
Describe the solution you'd like
I would like to see siridb connections support TLS v1.2, ideally at least single directional, but support for mutual TLS would be nice as well. It would be nice if the HTTP API also supported TLS/SSL connections.
Describe alternatives you've considered
Currently we have to rely on a docker-provided encrypted backhaul network to provide security over the wire, this is unnecessarily complex and adds a lot of overhead.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
I don't think, this would be useful, since it would also add a lot of bloat: increasing code basis and possible security problems. better use a TLS proxy for this or other proven and solid encryption layer (perhaps wireguard) to establish secure connection and protect your credentials.
Is your feature request related to a problem? Please describe.
This request is not based on a problem, but on what I feel is a shortcoming of the system. Encrypted connections would make it safer to store confidential data in SiriDB and also prevent plain-text passwords from flowing across the wire.
Describe the solution you'd like
I would like to see siridb connections support TLS v1.2, ideally at least single directional, but support for mutual TLS would be nice as well. It would be nice if the HTTP API also supported TLS/SSL connections.
Describe alternatives you've considered
Currently we have to rely on a docker-provided encrypted backhaul network to provide security over the wire, this is unnecessarily complex and adds a lot of overhead.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: