<head><title>ColdC: Security</title></head> <body> <h1 align=center><a href="/ColdC/">ColdC</a>: Security</h1> <hr> <p>As the ColdC driver does not know what sort of environment you will be executing, by default all functions are callable by any object in the database. In order to preserve integrity it is strongly suggested that you build a heirarchy of trusted objects. Bind administrative-level functions to these objects using the function <code><a href="/ColdC/Functions/bind_function.html">bind_function()</a></code> and restrict access to them. <p>It is suggested that the following functions always be bound and secured: <ul> <li>atomic() <li>create() <li>backup() <li>shutdown() <li>set_heartbeat() <li>cancel() <li>bind_port() <li>unbind_port() <li>open_connection() <li>fopen() <li>fstat() <li>fchmod() <li>fmkdir() <li>frmdir() <li>files() <li>fremove() <li>frename() <li>fclose() <li>fseek() <li>feof() <li>fwrite() <li>fread() <li>execute() <li>fflush() <li>bind_function() <li>unbind_function() </ul> <p>It is also suggested that any additional function which modifies an object or which alters/retrieves data on an object be bound. <p>You can further secure your database by solidifying key methods in your internal security scheme (if one exists) and locking them (by setting the <code>'lock</code> method flag, see section <a href="methods.html">Defining Methods</a>). <p> <hr size=4><p align=center><i>Last Modified on Feb 25 1996</i> <br><i>Copyright © 1995, 1996, Brandon Gillespie</i> </body>