Closed PsychoShock closed 2 months ago
I don't think that resource specific exploitation/mitigations should be included in the fivem docs.
Some of this would probably be better off living in a modding tutorial and be linked to from this doc.
@PsychoShock thoughts?
I don't think that resource specific exploitation/mitigations should be included in the fivem docs.
Some of this would probably be better off living in a modding tutorial and be linked to from this doc.
@PsychoShock thoughts?
I had the same thought—although the resource is extremely popular, this document is more about demonstrating how to prevent general situations rather than focusing on this specific resource. While I agree that a modding tutorial linked to the main docs could work, it would lead users to multiple documents (unless you have a better option). Perhaps I could remove the specific examples and keep the guidance more general?
Do you have anything in mind?
While I agree that a modding tutorial linked to the main docs could work, it would lead users to multiple documents (unless you have a better option). Perhaps I could remove the specific examples and keep the guidance more general?
I think this is a good idea, just remove the resource specific example
While I agree that a modding tutorial linked to the main docs could work, it would lead users to multiple documents (unless you have a better option). Perhaps I could remove the specific examples and keep the guidance more general?
I think this is a good idea, just remove the resource specific example
These examples are retained because they are helpful for understanding, but I also added a note that they do not represent any specific resources.
The issue here is that SQL related attacks are not related to FiveM at all.
So we just remove all the SQL section? I just added since it's something "good" for people to know. Up to you--feel free to remove what ever part you wish and merge the rest if it simplier. I'll stay available if any change.
This will be a good "start" for people building security in their server.