Yeah, you guys have serious problems. You are asking to get cracked pretty
bad... especially being a university! You guys are prime targets.
If you guys must use public internet lines for data transfer. Setup private
networks over it using IPSEC. Freeswan is an Open Source IPSEC server.
http://www.xs4all.nl/~freeswan/
This way, all traffic is encrypted over the Internet. A LOT safer. Also,
then you don't need to worry about ssl for postgres. All traffic going over
that tunnel will be safe.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Martin A. Marques" <martin@math.unl.edu.ar>
To: <pgsql-php@postgresql.org>
Sent: Thursday, March 22, 2001 9:53 AM
Subject: Re: [PHP] php, postgres, ssl
> El Jue 22 Mar 2001 10:45, escribiste:
> > The argument then would probably be, "why is your web app connecting to
a
> > database across the public Internet"?
> >
> > I'd assume that is not the safest, nor smartest, thing to do. There are
a
> > lot of problems with that setup.
>
> That is soething that we are trying to change, but it is very difficult.
Try
> to convince the politicians on the university that we need a public and
> private net with firewalls is a hard thing.
> Some people (not my boss) think that if you get cracked, you don't have to
> worry, because it's worst.
> With that kind of thinking, I can't do much.
>
> Saludos... :-)
>
> --
> System Administration: It's a dirty job,
> but someone told me I had to do it.
> -----------------------------------------------------------------
> Martín Marqués email: martin@math.unl.edu.ar
> Santa Fe - Argentina http://math.unl.edu.ar/~martin/
> Administrador de sistemas en math.unl.edu.ar
> -----------------------------------------------------------------
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
