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.
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.
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.
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?