5 ms·
really nice that you've used wasm and no server. This seems really secure to test. I was thinking at first: Hey, this might be kinda dangerous, imagine iterati
by nicolasmelo12 5y ago
really nice that you've used wasm and no server. This seems really secure to test.
I was thinking at first: Hey, this might be kinda dangerous, imagine iterating in a tool and sending my database to a server and any attacker retrieves the database.
But since it runs everything inside of the browser with wasm i found it WAY more secure. Nice that you've done it, will probably use it a lot.
- Siira 5y agoIt can't change under you on a whim though, can't it? Unless you host it yourself.
- jazzyjackson 5y agoSure but you can always keep the network tab in the devtools open and be confident nothing is getting exfiltrated
- krageon 5y agoOnce you see a connection doing so, it is too late :)
- nalgeon 5y agoThanks! I've always liked the idea of SQL in the browser, since the Web SQL times. That part is provided by the excellent sql.js project btw: https://github.com/sql-js/sql.js/ https://github.com/sql-js/sql.js/
- gizlu 5y agoIt would of course also increase server's potential attack layer. sqlite had some bugs, potentially exploitable, if you are able to invoke arbitrary statements https://www.sqlite.org/cves.html https://www.sqlite.org/cves.html https://www.sqlite.org/security.html https://www.sqlite.org/security.html