On Fri, Aug 17, 2018 at 09:49:01AM -0700, ToddAndMargo wrote:
On 08/17/2018 09:17 AM, Matthew Miller wrote:
>On Fri, Aug 17, 2018 at 08:34:12AM -0400, Tom Horsley wrote:
>>Todd Chester wrote:
>>>And now that you all write me back, they mysteriously started
>>>working again. AAAAAAHHHHHH!!!!!
>>This is the sort of thing that always makes me want to
>>run memtest for a few hours to see if memory corruption
>>is happening (in, for instance, the in memory copies of
>>pages from shared libs the tools might have been using).
>
>Or look for signs of malware / intruders.
>
Is there a scanner you recommend?
memtest, as someone already mentioned (you might even have a memory
testing tool in BIOS).
Read about kali-linux the other day (haven't found anything about
memtest being part of its tools tho') - never tried it. Seems to be a
complete Linux system specifically built for "penetration testing and
security auditing" [1], has a forensic mode boot option [2] and seems
to be installable on USB thumbs [3].
They write that the system won't neither touch nor mount an internal
disk [2]. Runs with root privileges [4].
Again: I never tried it ...
HTH
Wolfgang
[1]
https://docs.kali.org/introduction/what-is-kali-linux
[2]
https://docs.kali.org/general-use/kali-linux-forensics-mode
[3]
https://docs.kali.org/downloading/kali-linux-live-usb-install
[4]
https://docs.kali.org/policy/kali-linux-root-user-policy