If you don't need on-line access to a database on the "secure" side:
If the "secure" internal network and the DMZ are in the same facility,
the easiest solution is to set up two systems - one for content
development (all "internal" users can freely transfer finished content to
this system) and one for distribution.
Put the development system on the secure side, and the distribution
system on the DMZ. Use a JAZ drive or re-writeable CD-ROM to move content
between the two systems by hand.
If you need on-line access, use a proxy, and be sure to filter meta
characters!
-r.w.
On Tue, 23 Dec 1997, Oliver Kubis wrote:
> Olga,
>
> could you please explain whether you need on online-update (like for
> example an online-selection from a database located in the secure network)
> or a solution for simple one-time file transfers?
>
> Besides strict filtering rules, I'd suggest to use strong encryption and
> authentication methods (certificates) between the two machines.
>
> Regards,
> Oliver
>
> At 04:28 PM 12/23/97 +0300, Demina Olga wrote:
> >Hello all.
> >We are going to put our "public access" WWW Server in DMZ.
> >On the other hand, we have to public online information from the secure LAN
> >serment
> >on "public access" WWW Server.
> >So the problem is:
> >Public WWWServer have to get online information from secure network.
> >How to organize connection between DMZ and our secure network?
> >Any suggestions are appreciated.
> >
> >Thank you for your time.
> >Regards,
> >Olga
> >-----------------------------------------------------------------
> >Demina Olga
> >email olga @
spbex .
ru
> >
> >
> Oliver Kubis
> EDS Electronic Data Systems Industrien (Deutschland) GmbH
> Phone +49(0)6142-80-2942 Fax +49(0)6142-80-1755 Email oliverk @
ols-eds .
de
>
References:
|
|
