<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic IDS 9 security issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ids-9-security-issue/m-p/3360011#M871383</link>
    <description>Env: HP-UX11, Informix Dynamic Server 9.4&lt;BR /&gt;Issue: We have some users using odbc to access our databases, is there any way on group basis that we can grant limited permissions to this kind of users (set role doesn't work).&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Simon</description>
    <pubDate>Wed, 18 Aug 2004 09:59:12 GMT</pubDate>
    <dc:creator>Simon Liu_2</dc:creator>
    <dc:date>2004-08-18T09:59:12Z</dc:date>
    <item>
      <title>IDS 9 security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ids-9-security-issue/m-p/3360011#M871383</link>
      <description>Env: HP-UX11, Informix Dynamic Server 9.4&lt;BR /&gt;Issue: We have some users using odbc to access our databases, is there any way on group basis that we can grant limited permissions to this kind of users (set role doesn't work).&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Simon</description>
      <pubDate>Wed, 18 Aug 2004 09:59:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ids-9-security-issue/m-p/3360011#M871383</guid>
      <dc:creator>Simon Liu_2</dc:creator>
      <dc:date>2004-08-18T09:59:12Z</dc:date>
    </item>
    <item>
      <title>Re: IDS 9 security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ids-9-security-issue/m-p/3360012#M871384</link>
      <description>Set role does work provided you do it properly.  First you have to revoke permissions.  &lt;BR /&gt;&lt;BR /&gt;Don't allow people to connect as user informix, or the DBA user or anything silly like that.&lt;BR /&gt;&lt;BR /&gt;Create a role called readonly and grant select (only) to that role for each table, then grant the readonly role to the those users who access the database with restricted permissions.&lt;BR /&gt;&lt;BR /&gt;Then create a second role, with update/insert/delete/select etc permissions.  Grant that role to other users who are to be allowed to update the data.&lt;BR /&gt;&lt;BR /&gt;We also have a stored procedure which allows users to change role, according to what they have been granted.  Its sets the readonly role by default.&lt;BR /&gt;&lt;BR /&gt;It works for us, so it can be made to work for you.  Its probably just your historical set-up thats stopping it from locking out the right people.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Aug 2004 11:43:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ids-9-security-issue/m-p/3360012#M871384</guid>
      <dc:creator>Steve Lewis</dc:creator>
      <dc:date>2004-08-18T11:43:11Z</dc:date>
    </item>
  </channel>
</rss>

