agora inbox for pljava-dev@postgresql.org
help / color / mirror / Atom feed[Pljava-dev] ERROR: must be superuser to examine "dynamic_library_path"
4+ messages / 0 participants
[nested] [flat]
* [Pljava-dev] ERROR: must be superuser to examine "dynamic_library_path"
@ 2004-12-15 23:26
0 siblings, 1 reply; 4+ messages in thread
From: @ 2004-12-15 23:26 UTC (permalink / raw)
Newbie alert. First, thanks Thomas for this great addition to
PostgreSQL - I appreciate your efforts. I've installed PLJava on Linux
PostgreSQL 8.0 in a little test database. As the "postgres" super user,
I am able to deploy, load examples.jar and run javatest stored
functions. I did not need to set the dynamic_library_path in
postgresql.conf, as the so's where installed in /usr/local/pgsql/lib,
where it apparently already looking.
I've granted "All" to "public" on both the sqlj and javatest schemas.
But whenever I try to run any javatest functions as a user other than
postgres, I get the subject message. Is it possible to configure this
so that I don't need to grant superuser privilege to every user that
wants to execute Java stored procedures?
--
Guy Rouillier
^ permalink raw reply [nested|flat] 4+ messages in thread
* [Pljava-dev] ERROR: must be superuser to examine "dynamic_library_path"
@ 2004-12-16 07:35
parent:
0 siblings, 0 replies; 4+ messages in thread
From: @ 2004-12-16 07:35 UTC (permalink / raw)
Guy,
>I've granted "All" to "public" on both the sqlj and javatest schemas.
>But whenever I try to run any javatest functions as a user other than
>postgres, I get the subject message. Is it possible to configure this
>so that I don't need to grant superuser privilege to every user that
>wants to execute Java stored procedures?
>
>
I'm afraid that you've encountered a bug. It will be fairly easy to fix
since the code that attempts the access is obsolete. I should have
removed it long ago. Thanks for pointing this out. I'll supply a patch
for it later this week.
If you have the source for the latest beta and know how to compile, you
can comment out the lines 368 and 370 in src/C/pljava/type/Backend.c.
That should fix the problem.
Regards,
Thomas Hallgren
^ permalink raw reply [nested|flat] 4+ messages in thread
* [Pljava-dev] ERROR: must be superuser to examine "dynamic_library_path"
@ 2004-12-16 23:16
0 siblings, 1 reply; 4+ messages in thread
From: @ 2004-12-16 23:16 UTC (permalink / raw)
Thomas Hallgren wrote:
> Guy,
>
>> I've granted "All" to "public" on both the sqlj and javatest schemas.
>> But whenever I try to run any javatest functions as a user other than
>> postgres, I get the subject message. Is it possible to configure
>> this so that I don't need to grant superuser privilege to every user
>> that wants to execute Java stored procedures?
>>
>>
> I'm afraid that you've encountered a bug. It will be fairly easy to
> fix since the code that attempts the access is obsolete. I should have
> removed it long ago. Thanks for pointing this out. I'll supply a patch
> for it later this week.
>
> If you have the source for the latest beta and know how to compile,
> you can comment out the lines 368 and 370 in
> src/C/pljava/type/Backend.c. That should fix the problem.
I did indeed build this from the source, and am happy to report that
commenting out the two lines referencing dynPath appears to have solved
this problem. Thanks, Thomas.
After learning my way around, I'll probably remove everything and start
over so I can identify the minimum permissions necessary to provide the
PLJava functionality to all database programmers. For example, after
removing superuser permission, I discovered I needed select permission
on sqlj.jar_entry in order to execute javatest.java_addone. Has this
minimum set of permissions already been identified? If not, would it be
helpful for me to write that down as I go along?
--
Guy Rouillier
^ permalink raw reply [nested|flat] 4+ messages in thread
* [Pljava-dev] ERROR: must be superuser to examine "dynamic_library_path"
@ 2004-12-16 23:25
parent:
0 siblings, 0 replies; 4+ messages in thread
From: @ 2004-12-16 23:25 UTC (permalink / raw)
Guy Rouillier wrote:
>I did indeed build this from the source, and am happy to report that
>commenting out the two lines referencing dynPath appears to have solved
>this problem. Thanks, Thomas.
>
>
Good to know that it worked out.
>After learning my way around, I'll probably remove everything and start
>over so I can identify the minimum permissions necessary to provide the
>PLJava functionality to all database programmers. For example, after
>removing superuser permission, I discovered I needed select permission
>on sqlj.jar_entry in order to execute javatest.java_addone. Has this
>minimum set of permissions already been identified? If not, would it be
>helpful for me to write that down as I go along?
>
>
No work has been done in the security domain yet and any help is of
course greatly appreciated.
Thanks,
Thomas Hallgren
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2004-12-16 23:25 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-12-15 23:26 [Pljava-dev] ERROR: must be superuser to examine "dynamic_library_path"
2004-12-16 07:35 ` [Pljava-dev] ERROR: must be superuser to examine "dynamic_library_path"
2004-12-16 23:16 [Pljava-dev] ERROR: must be superuser to examine "dynamic_library_path"
2004-12-16 23:25 ` [Pljava-dev] ERROR: must be superuser to examine "dynamic_library_path"
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox