Information about the source code

[rakhirhif8963]

One of the mechanisms for increasing the level of security is to hide the source text of procedures and functions stored in the database from being read and modified by users operating it, including those with administrative privileges.

Why is it necessary to hide the text of procedures? Almost every commercial application contains information that you would like to protect from viewing and especially from changing the logic of its processing without the consent of the software author. The code of stored procedures may contain certain know-how of the product itself or methods of its licensing protection, mechanisms for restricting access to data using a role model are implemented, etc. Certain capabilities of this kind can be provided by the basic version of PostgreSQL, but they are very limited and need to be expanded. For example, restricting data visibility can be implemented using row level security technologies and through your own logic for accessing data at the level of the code of procedures and functions.

In PostgreSQL, of a procedure can be obtained using colombia whatsapp data tools from system views of the database. Here, one of the options for restricting access to the text of a procedure can be fine-tuning access rights to system views (view). But in PostgreSQL, this cannot be done for superusers, since a user with this role has access to all databases and all objects of all databases.

The wrap program, created by the developers of the Gazinformservice company, converts the ASCII text of the source code into an unreadable form that can be transferred to users, to geographically remote branches, etc. for subsequent storage of the corresponding procedures and functions in other database instances. The code is characterized by the same portability as the pgsql source code and can be imported and exported. The Jatoba DBMS supports dependencies for programs with hidden code in the same way as for programs with regular code. In other words, hidden programs in the database are functionally no different from regular pgsql programs; the only difference is that their text in its original form cannot be read through the pg_proc representation.