Unix security: Difference between revisions

Content deleted Content added
GID of files can be set arbitrarily
MD5 has been broken and SHA256 is a stronger alternative (unbroken as of now - Jan 2022).
Tags: nowiki added Visual edit
Line 60:
 
===Patching===
Operating systems, like all software, may contain bugs in need of fixing or may be enhanced with the addition of new features. Patching the operating system in a secure manner requires that the software come from a trustworthy source and not have been altered since it was packaged. Common methods for verifying that operating system patches have not been altered include the use of the [[digital signature]] of a [[cryptographic hash]], such as ana [[MD5SHA-2|SHA-256]] based checksum, or the use of read-only media.
 
From a security standpoint, the specific packaging method, such as the [[Dpkg|dpkg package manager]] or the [[RPM Package Manager]] format originally from [[Debian]] and [[Red Hat Linux]], respectively is not as important as the use of features which ensure the integrity of the patch itself.
 
====Source distributions====
Line 68:
 
====RPM packages====
[[Linux]] distributions which use the [[RPM Package Manager]] format for providing base functionality and software updates make use of [[MD5|cryptographic hash]]<nowiki/>es and [[GNU Privacy Guard|GPG]] to ensure content integrity. The hash values are packaged with the RPM file and verified when the package is installed.
 
====Debian packages====