DataMuseum.dk

top - metrics - download

    Length: 1445 (0x5a5)
    Types: TextFile
    Names: »object-code-protections.tex«

└─⟦4f9d7c866⟧ Bits:30007245 EUUGD6: Sikkerheds distributionen
    └─⟦36857feb3⟧ »./papers/Security_Primer/primer.tar.Z« 
        └─⟦5c5f5f2d8⟧ 
            └─⟦this⟧ »object-code-protections.tex« 

TextFile

\section{Object Code Protection}

To keep object code safe from human attackers and virus, a variety of
techniques may be employed.  

\begin{description}
\item[Checksums.]  Saving the checksums of each of the system files in
a protected area an periodically comparing the stored checksum with
those computed from the file's current contents is a common and
moderately effective way to detect the alteration of system files.

\item[Source Comparisons.]  Rather than just using a checksum the
complete files may be compared against a known set of sources.  This
requires a greater storage commitment.

\item[File Properties.]  Rather the computing a checksum, some
facility store certain attributes of files.  Among these are the length
and location on the physical disk.  While these characteristics are
easy to preserve, the naive attacker may not know that they are important.

\item[Read-Only Devices.]  Where practical, the system sources should
be stored on a device that does not permit writing.   On many system
disk partitions may be mounted as ``Read-Only.''

\item[Dates.]  On many systems the last modification date of each file
is stored and recent modifications of system files are reported to the
system administrator.

\item[Refresh.]  Some system automatically re-install system software
onto there machines on a regular basis.  Users of TRACK often do this
daily to assure that systems have not be corrupted.

\end{description}