Howdy,
At the Virtual Dev Summit today, the security subsystem was talked about:
00:24:44 <@dukeleto> I just got PL/Parrot converting the three basic
datatypes back and forth between Parrot and Postgres. The simplest
feature that
PL/Parrot needs is to disable ops relating to
filesystem access
00:24:56 <@allison> that's a specific task
00:25:10 <@allison> and can actually be worked on right away
00:25:18 <@dukeleto> allison: that sounds great. I can help
00:25:39 <@allison> excellent, we can talk about details
I was thinking that if Parrot made file access opcodes dynops,
PL/Parrot can just install it's own replacement dynop over it. Is this
feasible? Better and more extensible API's are obviously possible, but
being able to disable and/or replace certain op codes is a huge
feature that PL/Parrot needs.
PL/Parrot also requires being able to handle the "exception" of a
"disabled" opcode being called. Obviously, a DBA would rather get a
report that someone is writing fishy stored procedures, rather than
postgres dumping a core file.
Duke
--
Jonathan "Duke" Leto
[email protected]
http://leto.net
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
