Comments on: About The BUILTIN, FIPSFLAG and INTERFACE Pragmas in Oracle http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/ News, views, tips and tricks on Oracle and other fun stuff Fri, 21 Nov 2008 04:56:19 +0000 http://wordpress.org/?v=2.6.3 By: Go ahead, turn your FIPS flagging on » Eddie Awad’s Blog http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/#comment-22442 Go ahead, turn your FIPS flagging on » Eddie Awad’s Blog Thu, 29 Jun 2006 15:19:51 +0000 http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/#comment-22442 <p>[...] Since my last post about the undocumented pragmas in Oracle, I have found more information about the FIPSFLAG pragma directive and more specifically about the FIPS part of it. Jens commented about the existence of a session parameter FLAGGER and its possible relationship with FIPSFLAG and FIPS. After a bit of searching, here is what I found: [...]</p> [...] Since my last post about the undocumented pragmas in Oracle, I have found more information about the FIPSFLAG pragma directive and more specifically about the FIPS part of it. Jens commented about the existence of a session parameter FLAGGER and its possible relationship with FIPSFLAG and FIPS. After a bit of searching, here is what I found: [...]

]]> By: Jens http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/#comment-14792 Jens Sat, 03 Jun 2006 16:11:56 +0000 http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/#comment-14792 <p>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.</p> 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.

]]> By: Eddie Awad http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/#comment-14662 Eddie Awad Sat, 03 Jun 2006 04:57:09 +0000 http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/#comment-14662 <p>Pete, thanks for your work on this and the extra clarification.</p> Pete, thanks for your work on this and the extra clarification.

]]> By: Pete Finnigan http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/#comment-14510 Pete Finnigan Fri, 02 Jun 2006 19:56:21 +0000 http://awads.net/wp/2006/05/24/about-the-builtin-fipsflag-and-interface-pragmas-in-oracle/#comment-14510 <p>Hi Eddie,</p> <p>Nice post!!</p> <p>A couple of comments. Normally FIPS stands for Federal Information Processing Standards, I don't know but maybe its related?</p> <p>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..:-)</p> <p>cheers</p> <p>Pete</p> 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

]]>