[Cialug] hiding a publicly accessible database server

[Nathan C. Smith]

Have you looked at the open hashing technology?

Not sure if you would use that instead of Postres or use a variation on the system fro your application.

-Nate

> -----Original Message-----
> From: cialug-bounces at cialug.org
> [mailto:cialug-bounces at cialug.org] On Behalf Of Matthew Nuzum
> Sent: Thursday, September 11, 2008 1:57 PM
> To: Central Iowa Linux Users Group
> Subject: [Cialug] hiding a publicly accessible database server
>
> Hi, I'm conceiving an application that would like to use a
> centralized postgres database. For my idea to work best it
> would be nice if the application could make a connection to
> the postgres server on demand without the user having to do
> anything. Yet I really don't want to put the database wide
> open to the web. So its a conundrum.
>
> I have an idea I know would work but is has a challenge: Use
> an SSH tunnel. But for this to work, the user would have to
> create an SSH key without a password and keep in on their
> computer. If someone else found this key then they'd have
> shell access to the machine used to tunnel the postgres
> connections. (the reason for no ssh password is so that the
> application could initiate the ssh connection automatically)
>
> Does anyone have a suggestion?
>
> --
> Matthew Nuzum
> newz2000 on freenode
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>