11 karma · joined December 27, 2022
Base64 is about encoding not hashing... So decoding it is... natural. The point here is that it's integrated inside ChatGPT? It seems to me that it's an "obvious" "feature" kind of.
It's a bit weird but I'm using a langage (for a specific project) where prepared statements aren't available (except if you pay or use a specific DBMS, I can't do both because the client won't pay and I need SQLServer).
My initial idea was to use a DLL from PDO (I'm developping on a Windows env) or whatever known piece of code that is trustable in order to sanitize user inputs (of course we do it client side but user is devil :-)) before sending it to SQLServer.
After all answers and my researches, I think that I'll use a tiers piece of code to escape queries (probably a C# program using SQLCommand).
Thanks all.
If anybody knows exactly how SQLServer is handling SQL Statements, please let us know.
It makes sense.
I didn't catch the "client side" part as you do, thanks for the explanation.
"The string returned by sqlite3_expanded_sql(P) [...] is obtained from sqlite3_malloc() [...]"
From SQLite documentation: https://www.sqlite.org/c3ref/expanded_sql.html
I'm still wondering why it's not available for SQLServer (because there are use cases for this feature).
It is "just" a matter of driver interface (I mean the piece of code that implement ODBC API) that "just" do not give this feature or it's letteraly not possible with SQLServer?
Does anybody knows something about source code release (as stated in the GitHub repo)?
https://github.com/multiplie-fr/minimit
Edit: They are working on a v1.1 and they want to release it soon. Keep following the repo.
Edit: I'm a happy user ;-)
I opened an issue:
https://github.com/NotJoeMartinez/yt-fts/issues/1
Hope it helps.
This behavior is due to the YouTube cookies consent page.
I opened an issue about this specific issue: https://github.com/NotJoeMartinez/yt-fts/issues/1
Glad if you want to help.
Edit: It's in the "Discussions" GitHub tab.
Edit: Got a GH response:
"Our review of the account(s) and/or content named in your report has concluded. We have determined that one or more violations of GitHub’s Terms of Service have occurred and have taken appropriate action in response."