Access directly your SQL databases via HTTP. In full security
1–10 of 18 posts
Re: Access directly your SQL databases via HTTP. In full security
#2What problem is this trying to solve?
Re: Access directly your SQL databases via HTTP. In full security
#3What problem is this trying to solve?
Exfiltration of back-end data from a shelled webserver?
Re: Access directly your SQL databases via HTTP. In full security
#4Look similar to postgrest, but younger project under (L)GPL license.
Re: Access directly your SQL databases via HTTP. In full security
#5What problem is this trying to solve?
Exfiltration of back-end data from a shelled webserver?
Seems like if you already have a shell it'd be easiest to just dump data directly over a pipe.
I guess SQL over HTTP could be used to directly operate on databases from resource constrained devices that don't support the full socket library for whatever database you're using?
Re: Access directly your SQL databases via HTTP. In full security
#6Earlier quoted context omitted.
Exfiltration of back-end data from a shelled webserver?
Seems like if you already have a shell it'd be easiest to just dump data directly over a pipe. I guess SQL over HTTP could be used to directly operate on databases from resource constrained devices that don't support the full socket library for whatever database you're using?
>I guess SQL over HTTP could be used to directly operate on databases from resource constrained devices that don't support the full socket library for whatever database you're using?
Indeed. I think botnets could be an example of such "devices."
Re: Access directly your SQL databases via HTTP. In full security
#7What problem is this trying to solve?
I've written a dozen internal dashboards where something like this would have been useful. Rather than writing server side code to craft queries and return results, you can add arbitrary queries easily to the front end. Just use a read-only DB account and you are golden.
Is it the right way to do it? No.
Is it something you can stand up in a few hours so you can work on the things that keep your startup afloat instead? Absolutely.
Re: Access directly your SQL databases via HTTP. In full security
#8Why not just set up a SPARQL endpoint, which seems to be the recommended standard for accessing data over Web platforms?
Re: Access directly your SQL databases via HTTP. In full security
#9rest and odata?
Re: Access directly your SQL databases via HTTP. In full security
#10What problem is this trying to solve?
I've written a dozen internal dashboards where something like this would have been useful. Rather than writing server side code to craft queries and return results, you can add arbitrary queries easily to the front end. Just use a read-only DB account and you are golden. Is it the right way to do it? No. Is it something you can stand up in a few hours so you can work on the things that keep your startup afloat instea…
This sort of tool would be nice for PoC - but if you're using it for production anything and have any customer information (or really, any information of value) saved in that database... it would be terrible - even off an R/O connection.