3 ms·

Would it matter? There would be waves of jackasses storing information in them with access granted to anyone, anywhere, because sec is a bother.

squigz 3y ago
Well it would matter in that your comment would actually make sense.
- sonicanatidae 3y ago
  https://www.unrepo.com/sqlite/authentication-and-authorization-in-sqlite-tutorial https://www.unrepo.com/sqlite/authentication-and-authorizati... Note: ANY data storage needs auth. While SQLite's auth is limited, it's still auth, so while you are technically correct, I still expect this to be fucked up by coders, because sec is a bother. smh.
  - eternityforest 3y ago
    SQLite is a file. It doesn't need auth any more than a text file your editor opens. The "auth" is in the OS not letting people access your files. That article seems to be talking about using SQLite to implement authentication for I guess web apps or something, and many/most sqlites are used for stuff that isn't anything like a server. Admittedly coders can still fuck that up by not setting file permissions right(as with any file), so that other users on the system can access it, but these days that seems to be a secondary line of defense, now that systems are mostly single user or container based, people usually don't have fully untrusted stuff running outside a VM.
  - qweqwe14 3y ago
    You clearly don't know what you are talking about. SQLite is a file on disk, the security of who can access it is managed by the OS via filesystem permissions, users and other mechanisms. It's not rocket science, and you would know that if you actually bothered to learn the basics. There is no "authentication" in SQLite, because it's not even applicable to what SQLite aims to be, which is an application file format. Would you also complain that there's no "authentication" on .json files?

3 ms·

Would it matter? There would be waves of jackasses storing information in them with access granted to anyone, anywhere, because sec is a bother.

by sonicanatidae 3y ago

squigz 3y ago
Well it would matter in that your comment would actually make sense.
- sonicanatidae 3y ago
  https://www.unrepo.com/sqlite/authentication-and-authorization-in-sqlite-tutorial https://www.unrepo.com/sqlite/authentication-and-authorizati... Note: ANY data storage needs auth. While SQLite's auth is limited, it's still auth, so while you are technically correct, I still expect this to be fucked up by coders, because sec is a bother. smh.
  - eternityforest 3y ago
    SQLite is a file. It doesn't need auth any more than a text file your editor opens. The "auth" is in the OS not letting people access your files. That article seems to be talking about using SQLite to implement authentication for I guess web apps or something, and many/most sqlites are used for stuff that isn't anything like a server. Admittedly coders can still fuck that up by not setting file permissions right(as with any file), so that other users on the system can access it, but these days that seems to be a secondary line of defense, now that systems are mostly single user or container based, people usually don't have fully untrusted stuff running outside a VM.
  - qweqwe14 3y ago
    You clearly don't know what you are talking about. SQLite is a file on disk, the security of who can access it is managed by the OS via filesystem permissions, users and other mechanisms. It's not rocket science, and you would know that if you actually bothered to learn the basics. There is no "authentication" in SQLite, because it's not even applicable to what SQLite aims to be, which is an application file format. Would you also complain that there's no "authentication" on .json files?