Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

External access by default #655

Open
Nainterceptor opened this issue Oct 30, 2020 · 2 comments
Open

External access by default #655

Nainterceptor opened this issue Oct 30, 2020 · 2 comments
Assignees

Comments

@Nainterceptor
Copy link

Hello,

We've concerns from our security team :
By default, an arango deployment will have an external access via a loadbalancer, it will leads to a security issue, a database will be available worldwide with empty root password.

Your point of view should be developers-friendly : have a ready to use database for developers, and this database should be tweaked for production.

But, experience shown that people don't tweak configurations even if you say to do it in the bolder font, size 72.
That's why we have a lot of unsecured mongodb databases in free access over the internet. Even if mongodb always recommand to bind to local network... (No network access is better than password)

We recommand to have default value of spec.externalAccess.type to "None".
It's the common configuration about ingress for all well-known chart configurations.
Side effects :

  • Will be breaking change
  • Will prevent load balancer creation billing for managed k8s clusters

Best regards,
Gaël

@kalavt
Copy link

kalavt commented Jan 20, 2024

Any update? it's serious security issue to open access widely to public by default.

@jwierzbo
Copy link
Collaborator

@kalavt Externall access will be disabled in the next minor version (1.3.0).

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

No branches or pull requests

4 participants