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

Add whitelist for server settings editing #876

Closed
klemmchr opened this issue Jan 19, 2018 · 10 comments · Fixed by #892
Closed

Add whitelist for server settings editing #876

klemmchr opened this issue Jan 19, 2018 · 10 comments · Fixed by #892
Assignees
Labels
Milestone

Comments

@klemmchr
Copy link
Contributor

Arma 3 Version: 1.80 (stable)
CBA Version: 3.5.0 (stable)

Mods:

- CBA_A3
- ACE3

Description:

  • Adding a whitelist of player uids for server settings editing could be helpful to protect the editing of server settings in large communities. In our community every member has got the server password to load missions on the fly however server settings should not be editable by them. I would like to request a security feature where the server owner can specify certain uid's allowed to change server settings.
@Cuel
Copy link
Contributor

Cuel commented Jan 21, 2018

Can't you set voting treshold really low instead, to allow players to vote themselves admin?

@jonpas
Copy link
Member

jonpas commented Jan 21, 2018

Can't you set voting treshold really low instead, to allow players to vote themselves admin?

Is what we do with our not-official-missions server.

@klemmchr
Copy link
Contributor Author

We're currently doing this but it's not working when HCs are connected to the server. Also we want to distribute the password to our closest members but some tend to play around with the settings even though they should not.
I could submit a PR if you're up to it.

@commy2
Copy link
Contributor

commy2 commented Feb 8, 2018

I could see this working. Where should that setting be? Itself being a global cba setting? Description.ext entry? Config entry?

@commy2 commy2 added the Feature label Feb 8, 2018
@commy2 commy2 added this to the 3.7 milestone Feb 8, 2018
@klemmchr
Copy link
Contributor Author

klemmchr commented Feb 8, 2018

Global CBA setting could be the easiest way. There should be a fallback option in case the server owner is locking out himself, maybe a config entry could fit this scenario the best.

@commy2
Copy link
Contributor

commy2 commented Feb 8, 2018

Logged admin would have access regardless, so no way to lock out yourself. The setting would only be for additional "admins".

@klemmchr
Copy link
Contributor Author

klemmchr commented Feb 8, 2018

What do you mean with additional admins?

@commy2
Copy link
Contributor

commy2 commented Feb 8, 2018

Users that can edit the Server tab settings. Which is atm only possible as logged in admin.

@klemmchr
Copy link
Contributor Author

klemmchr commented Feb 8, 2018

Well, this doesn't fit the intentional idea of a whitelist for logged in admins.

@commy2
Copy link
Contributor

commy2 commented Feb 8, 2018

I see. I got it wrong and confused this with a different proposal that was brought up in Slack.

@commy2 commy2 self-assigned this Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants