Skript 2.8 support #25

Open
opened 2024-01-23 22:39:57 +00:00 by toms · 4 comments

The plugin is currently not working with the latest script version. I hope that support for the latest version can be added so that the add-on can continue to be used.

The plugin is currently not working with the latest script version. I hope that support for the latest version can be added so that the add-on can continue to be used.
Owner

Is there any error that I could go by? I cannot find what exactly changed in Skript 2.8 that makes this not work.

Is there any error that I could go by? I cannot find what exactly changed in Skript 2.8 that makes this not work.

If you use the unsafe function it works, but it is unsafe. I wanted to take this opportunity to thank you again for the plugin. It helps me a lot.

If you use the unsafe function it works, but it is unsafe. I wanted to take this opportunity to thank you again for the plugin. It helps me a lot.
5.5 KiB
Owner

thanks for the provided information, I recommend using unsafe for the time being and ensuring your inputs are well validated, to prevent SQL injection

I will look into fixing it at some point, but for the time being I'm busy with other things, and SQL injection protection code comes from the original developer before I had started updating skript-db myself, which will take some time understanding what he was doing with it

thanks for the provided information, I recommend using unsafe for the time being and ensuring your inputs are well validated, to prevent SQL injection I will look into fixing it at some point, but for the time being I'm busy with other things, and SQL injection protection code comes from the original developer before I had started updating skript-db myself, which will take some time understanding what he was doing with it
Owner

unsafe is currently mandatory for PostgreSQL as it doesn't work the safe way even in older Skript versions, I think the solution could be to make a whole another system for automatic SQL injection protection, that would work throughout all database systems

maybe adding a syntax for prepared statement creation?

unsafe is currently mandatory for PostgreSQL as it doesn't work the safe way even in older Skript versions, I think the solution could be to make a whole another system for automatic SQL injection protection, that would work throughout all database systems maybe adding a syntax for prepared statement creation?
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Limework/skript-db#25
No description provided.