Skip to contentSkip to conversation

Disturbing news..

DISCUSSION Jesse Pollard 1 participant 1 message Mar 29, 2001

lore
Share & tools
lore
#0 lore raw

Walter Hofmann <[email protected]>:

Quoted 1 line · Jesse Pollard

[snip]

Quoted 10 lines
Quoted 6 lines

Now, if ELF were to be modified, I'd just add a segment checksum for each segment, then put the checksum in the ELF header as well as in the/a segment header just to make things harder. At exec time a checksum verify could (expensive) be done on each segment. A reduced level could be done only on the data segment or text segment. This would at least force the virus to completly read the file to regenerate the checksum.

So? The virus will just redo the checksum. Sooner or later their will be a routine to do this in libbfd and this all reduces to a single additional line of code.

true.

Quoted 8 lines
Quoted 5 lines

That change would even allow for signature checks of the checksum if the signature was stored somewhere else (system binaries/setuid binaries...). But only in a high risk environment. This could even be used for a scanner to detect ANY change to binaries (and fast too - signature check of checksums wouldn't require reading the entire file).

One sane way to do this is to store the sig on a ro medium and make the kernel check the sig of every binary before it is run.

Only for trusted binaries. (extreme paranoia now).

Quoted 3 lines

HOWEVER, this means no compilers will work, and you have to delete all script languages like perl or python (or make all of them check the signature).

Compilers should work normally, the link phase is what would generate the checksums, though if each object file contained a checksum for the segment then the interpreters/dynamic loaders would have the choice.

The only applications I see as really needing to check such signatures are those using PAM. These should do it anyway. The dynamic linking programs should do so only if they are configured to do so.

Quoted 5 lines

Useless again, IMO.

Quoted 1 line

In any case, the problem is limited to one user, even if nothing is done.

Your best bet is to educate your users.

User eduation is a reasonable substitute as long as they can be directed to follow the rules.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [email protected]

Any opinions expressed are solely my own.