Is it possible to get emerge to do a SHA256 hash on each binary, just before it installs them, and then store the in a user defined location. One could then use this hash table to check later if the binary has been modified in any way. e.g. virus. Using emerge to do this, would also have the benefit of the hash table being updated with each install.
Portage stored MD5 hashes, I don't see any benefit from using SHA256 for this, TBH...
Where are the md5 hashes? It is my understanding that md5 hashes are insecure. SHA256 is considerably better.
Needs a new vdb format => not anytime soon.
(In reply to comment #2) > Where are the md5 hashes? See CONTENTS files in /var/db/pkg/<category>/<ebuild>. You can use 'equery check <pkgspec> from gentoolkit to verify the MD5 checksums for ebuilds.
i thought portage already supported SHA1 in CONTENTS ? or am i just imagining ?
(In reply to comment #5) > i thought portage already supported SHA1 in CONTENTS ? or am i just imagining > ? The second. The CONTENTS format is nothing you can change that easily.
