|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
RE: ODBC in DMZ
sean.kelly
lanston.com
Thu, 15 Jul 1999 11:33:34 -0400
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Stefan Norberg: "Re: ODBC in DMZ"
- Previous message: Neil Lehrer: "RADware fireproof"
- Next in thread: Stefan Norberg: "Re: ODBC in DMZ"
> From: C. K. Lung [mailto:clung
hotmail.com]
>
>
> A user needs to use ODBC access a program in DMZ. Do I need
> to open ports
> or/and socket to allow the access? What kind of security
> risk it would
> post? Any comments/suggestions are greatly appreciated.
I'm fairly sure it depends on the means of access. If it's a MSSQL server
providing tcp/ip access, it will default to port 1433 on the server. You
can specify that you want to make a tcp/ip connection in the odbc config.
If it's some other situation... I'm not sure offhand but I'll bet there are
a ton of articles in the microsoft knowledge base. The security risk would
depend on what you had to open up, but assuming it is access to a port on an
sql server then you are potentially making access to that server available
to the world (though they'd still have to figure out a username/password to
do anything).
Sean
- Next message: Stefan Norberg: "Re: ODBC in DMZ"
- Previous message: Neil Lehrer: "RADware fireproof"
- Next in thread: Stefan Norberg: "Re: ODBC in DMZ"
This archive was generated by hypermail 2.0b3 on Sat Jul 17 1999 - 07:19:03 CDT