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.

Sign up for GitHub

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

Jump to bottom

/configure public accessible #47

Closed
MoritzFago opened this issue Jun 7, 2018 · 1 comment
Closed

/configure public accessible #47

MoritzFago opened this issue Jun 7, 2018 · 1 comment
Labels
A: Security

Comments

@MoritzFago
Copy link

/configure is currently publicly accessible. This could be a security issue.
@elegaanz elegaanz added C: Bug Something isn't working P: High and removed C: Bug Something isn't working labels Jun 7, 2018
@elegaanz
Copy link
Member

elegaanz commented Jun 7, 2018

We should probably rethink the instance setup anyway. What I'm thinking about is to have a plume command which asks you questions to setup the instance (like instance name, domain, but also DB URL) and create the admin account, setups the instance, and then launches it (and just launches if it have been configured). It would mean installing Plume would just be cargo install plume (and most of the time setting up a service and a reverse-proxy).

@elegaanz elegaanz mentioned this issue Jun 19, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A: Security
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MoritzFago @elegaanz