docs(tr): translate GUIDs and authorization note for API1:2023 - #166
Open
jankesec wants to merge 1 commit into
Open
docs(tr): translate GUIDs and authorization note for API1:2023#166jankesec wants to merge 1 commit into
jankesec wants to merge 1 commit into
Conversation
Translate the GUIDs/UUIDs authorization note in the Turkish edition of API1:2023 (Broken Object Level Authorization), clarifying object enumeration and authorization verification principles. Closes OWASP#164
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR translates the placeholder GUIDs/UUIDs authorization note into Turkish in
editions/2023/tr/0xa1-broken-object-level-authorization.md(API1:2023 Broken Object Level Authorization).Key security terms such as
object enumeration,excessive data exposure, andendpointare preserved in context alongside accurate Turkish terminology to maintain technical clarity.Closes #164