CLI QuickTextRender output utf-8#1804
CLI QuickTextRender output utf-8#1804cam0200 wants to merge 1 commit intovolatilityfoundation:developfrom
Conversation
|
Looks like similar issue was reported here: #1754 |
|
This appears to be python/windows outputting in codepage 1252 for some reason (I don't know if that's the default for python on windows, or information passed by the terminal, etc): I believe volatility already outputs at utf-8, so I'd prefer to get more clarity as to exactly what's going wrong (is it volatility outputting a bad character, or is it python misrepresenting the output stream to the terminal, etc)... Otherwise my concern is that the A good test would be to pipe the output to a file and verify whether the file is all valid utf-8 or not. If it is, then there's some other issue somewhere is the connection between the terminal and python, if not we can take a look at which character is invalid and see if we can figure out how it's happening... |
|
This is an example of attempting to output to a file, which results in the same issue The point that it breaks at appears to be this output from windows.filescan.FileScan plugin |
This comment was marked as duplicate.
This comment was marked as duplicate.
This solution is already posted by @cam0200 in merge request |
Volatility would running into an error when pipping Unicode output in Powershell (whether writing to file or terminal)
POC command:
python .\vol.py -f C:\<path>\memdump.dmp windows.filescan.FileScan | Select-String -Pattern '\.\w{2}\b'The change that is implemented will force output text to be utf-8 encoded.