Skip to content

Mxvmem maintenance #285

Merged
merged 3 commits into from
Dec 7, 2022
Merged

Mxvmem maintenance #285

merged 3 commits into from
Dec 7, 2022

Conversation

thomas
Copy link
Contributor

@thomas thomas commented Dec 6, 2022

No description provided.

From the context the tool fits in forensics.
Also it was accepted to have a python script
therein.
Reading logfiles containing 'strange' bytes, would yield
errors like:

  "UnicodeDecodeError: 'utf-8' codec can't decode byte
   0xb3 in position 3221: invalid start byte"

Either switch to binary input, or escape the characters
in question. Here the latter was choosen.
Copy link
Collaborator

@donald donald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nits:

  • Commits 1 and 2 could be one because its a single logical operation and it doesn't work when only half is done
  • Commit messages could start uppercase

Was about to say, that backslashreplace was not required in ProcBuffer, because the non-ascii and non-utf8 characters came from /proc/PID/fd, which only exists in the forensic logfile, but, yes, there is "Name:" in /proc/PID/status.

buczek@theinternet:~/x$ head -2 /proc/$$/status
Name:	äöü
Umask:	0002

:-)

@thomas
Copy link
Contributor Author

thomas commented Dec 7, 2022

Also I do not know if someone uses ProcBuffer to read other files from proc, which probably should not use 'invalid' chars, but who knows. So with this I should be on the safe side.

@thomas thomas merged commit 08dbbfb into master Dec 7, 2022
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants