Partly, I am thinking that when trying to access GNUmed from inside a
hospital, many hospitals are strict about port egress. It is possible
that they may allow only ports 80 and 443.
Would it therefore work to configure a client (that needed to connect
from inside a hospital) to connect to a GNUmed server on port 443?
This scenario would require that the server has port redirection set
up, to forward the incoming request to Postgres port 5432. (?)
For the SSL to be supported, must Apache be used, and must it perhaps
be added to postgres as a user?
By the way, does GNUmed set Postgres to use non-trust authentication
and, for passwords, do GNUmed/postgres authenticate using md5, crypt
or password (hopefully md5) :-)
On 27-Jan-08, at 5:06 PM, James Busser wrote:
If client and server both support it the connection is run
by GNUmed with SSL.
What is required for the "client to support it"? Is there software
or services that must be enabled and running on the client computer
OS, and/or anything that needs to be set up anywhere in configuration?
_______________________________________________
Gnumed-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnumed-devel
