-
Website
http://awads.net/wp/ -
Original page
http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
jgarry
3 comments · 1 points
-
Andy C
22 comments · 47 points
-
dahowlett
1 comment · 2 points
-
Don Seiler
9 comments · 1 points
-
davidhaimes
4 comments · 3 points
-
-
Popular Threads
Hi Eddie,
Nice post!!
A couple of comments. Normally FIPS stands for Federal Information Processing Standards, I don't know but maybe its related?
Also on the Pragma interface C, if you read further in my first big Oracle paper (Expoliting and protecting Oracle) you will see that i tried to use the syntax myself but if fails with an ORA-6509 - ICD vector Processing error. I assumed at the time that Oracle implements a function call table. Like a table of structs that includes details for each function implemented as a pragma interface C call. This table or linked list would include function pointers for each C function, hence you cannot simply call your own C directly from PL/SQL unless you can update this table to add the address of the function you add. This is a great interface for calling C directly without the extproc overheads if only we coluld find a way to make it work..:-)
cheers
Pete
Pete, thanks for your work on this and the extra clarification.
I would also guess that the pragma FIPSFLAG is related with the FIPS compliance.
There is a session parameter FLAGGER which causes an error message to be generated when a SQL statement issued is an extension of ANSI SQL92.
This would somehow explain why SQLERRM is declared with this pragma.