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

Use static nums for role elevation check #1137

Merged
merged 1 commit into from
May 17, 2017

Conversation

Martii
Copy link
Member

@Martii Martii commented May 17, 2017

  • I never have liked this test and mathematical calc... it's just asking for a security breach if there is an error somewhere else
  • Set to static numbers... we have static numbers all over the place so continue to use these

Applies to #1109 and #1107

* I never have liked this test and mathematial calc... it's just asking for a security breach if there is an error somewhere else
* Set to static numbers... we have static numbers all over the place so continue to use these

Applies to OpenUserJS#1109 and OpenUserJS#1107
@Martii Martii added CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. security Usually relates to something critical. labels May 17, 2017
@Martii Martii merged commit 1562c6f into OpenUserJS:master May 17, 2017
@Martii Martii deleted the Issue-1109roleToStatic branch May 17, 2017 02:33
Martii added a commit to Martii/OpenUserJS.org that referenced this pull request Aug 19, 2019
* Create system reserved role type
* Bump DB/project version as this is not backwards compatible and a breaking change
* Amend TOS for an explicit instead of implied reserved right for renaming access. This is useful to notify the author including possible account name change requests.
* When OUJS needs to reserve a future (or current) specific name to continue the Sites integrity, especially from "bad actors", this is useful to have for a reservation with rename. Perhaps useful later on as well for some additional feature. These instance should be rare but declare none-the-less.

Post OpenUserJS#1137 OpenUserJS#735 *(inverse)*
@Martii Martii mentioned this pull request Aug 19, 2019
Martii added a commit that referenced this pull request Aug 19, 2019
* Create system reserved role type
* Bump DB/project version as this is not backwards compatible and a breaking change
* Amend TOS for an explicit instead of implied reserved right for renaming access. This is useful to notify the author including possible account name change requests.
* When OUJS needs to reserve a future (or current) specific name to continue the Sites integrity, especially from "bad actors", this is useful to have for a reservation with rename. Perhaps useful later on as well for some additional feature. These instance should be rare but declare none-the-less.

Post #1137 #735 *(inverse)*

Auto-merge
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. security Usually relates to something critical.
Development

Successfully merging this pull request may close these issues.

1 participant