SEO

Yes, your INFORMIXSQLHOST environment setting tells you where the file
is...

And you can have different ones on same machine... Just make sure the
informix env is set properly before engine start....

Kinda like "oraenv" since you seem to know that...
If your informix env is not set right on engine start... You could have
a big "party"... .. (resume updated?)

echo $INFORMIXSQLHOSTS
/informix/PRD/etc/sqlhosts_hotsite_prd.tli




-----Original Message-----
From: owner-informix-list@iiug.org [mailtowner-informix-list@iiug.org]
On Behalf Of Wolf
Sent: Tuesday, November 09, 2004 9:36 AM
To: informix-list@iiug.org
Subject: Re: No ODBC access to Informix...

Hi there,

I just was informed that providing an empty 'sqlhosts' file would
prevent anybody from accessing the box.

Now -
in sqlhosts a "nettype" and some "options" are entered. Are there any
chances to narrow down the scope of "neglection" using these parameters?
Like - nettype not including "ODBC-net access", or options stating only
read-oinly access....

Next -
the 'sqlhosts' file - is it one per box, or one per "instance" - i.e.
would it be possible to install two dbm-instances on one machine with
two different sqlhosts files?

(I know RTFM - but - I don't have them, and I basically do not have
time to become a Informix admin.....)

Regards
Wolf

wolf.duttlinger-manger@gmx.de (Wolf) wrote in message
news:<6e942e26.0411090203.1f43e57d@posting.google. com>...
> Yeeeeha!!!!
>
> Peng, peng!!!
>
> <G>
>
> I totally agree to this Art - only - the ERP is there and it works the

> way it works... i.e. the users log on to the DB using their! uid - and

> therefore have to have the rights they have.....
>
> So - also to the others that posted - I do not see a solution -
> "hiding" a database is no solution - we have to mitigate the risk of a

> user changing the data outside the ERP.....
>
> Again - please does anybody have an idea how to block ODBC access to a

> Solaris based Informix *** at all *** - i.e. I do not want to allow
> _ANY_ ODBC calls to be coming in to this box - somehow configuring a
> "listener" - if there is such thing in Informix......
>
> Regards
> Wolf
>
> "Art S. Kagel" <kagel@bloomberg.net> wrote in message
news:<pan.2004.11.08.15.48.49.861051.1355@bloomber g.net>...
> > On Mon, 08 Nov 2004 14:00:45 -0500, Bill Dare wrote:
> >
> > WAIT just one minute there cowboy! Why not just disable the user's
> > update/insert/delete permissions on the database itself! The
> > 'business' app can log into the database on the users' behalf using
> > a different ID which is priveleged to modify the data. If doing
> > that with a single login for all, then create another small
> > read-only database that maps real user-id and password to a unique
> > alter-ego user-id which will be used to connect to the DB server.
> >
> > Art S. Kagel
> >
> > >> I do not know Informix - but from my understanding there must be
> > >> a way to totally disable ODBC access towards this database. I
> > >> know a little about
> > >> DB2 and Oracle and from there I have the following picture:

-----------------------------------------
================================================== ========== The
information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the
intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
reproduction, dissemination or distribution of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and deleting it
from your computer. Thank you. Tellabs
================================================== ==========


sending to informix-list