Re: Ways to fake table in own scema.

My apologies, I wrote this in a hurry. For those that were confused by what I wrote, the security issues I refer to are probably better referred to as lack of knowledge issues. I've seen new DBA's implement public synonyms and then grant to PUBLIC whatever access is required. THEN you have a security issue, particularly if scott/tiger still exists in the database. It basically means you have no way of stopping people from damaging the data.

Public synonyms by themselves are not a security issue, just the way some people implement them.

Hope this clarifies my initial too quickly sent response!

Pete

Pete Sharman wrote:

> Nope, but if you want to you could make them public synonyms so you don't
> need to do this for multiple users. There are security issues here
> though.
>
> HTH.
>
> Pete
>
> "G. Mjoen" wrote:
>
> > I have a user (USER1) with a lot of tabes. I created a new user
> > (USER2) with no tables in his/hers schema. USER2 is granted select on
> > all of USER1's tables.
> >
> > The problem is:
> >
> > USER2 needs to write 'select * from USER1.TABLE1' instead of 'select *
> > from TABLE1'.
> >
> > I am able to fix this by creating a synonym for each table. Is there
> > som other way of doing this?
> >
> > --
> > Gaute

Received on Mon Aug 30 1999 - 11:11:30 CDT