Closed GoogleCodeExporter closed 9 years ago
Ok, thanks. I believe I've fixed both of those in r655. The s.Name check went
in as is, but rather than catching a unicode decode error, I've handled the
possible outputs explicitly (since dat could be a list of unicode strings
[REG_MUTLI_SZ] or just a unicode string [REG_SZ, et al]). I've also gone with
.encode("ascii", "backslashreplace") since we seem to have used that in a few
other places.
I don't think it should be up to registry returning function to prematurely
convert to ascii (particularly when we decide to move to python3 which does
most things internally as unicode), although it would be much easier to add it
in there.
Anyway, let me know if that's ok/works/a terrible idea/better than sliced
bread, and then we can figure out what status to give this... 5:)
Original comment by mike.auty@gmail.com
on 3 Feb 2011 at 8:42
Right... I guess that makes sense. About REG_MUTLI_SZ I wonder if we should
print those out item by item, because as is, it prints like:
REG_MULTI_SZ HTTPFilter : [u'HTTPFilter', u'', u''] (Stable)
REG_MULTI_SZ LocalService : [u'Alerter', u'WebClient', u'LmHosts',
u'RemoteRegistry', u'upnphost', u'SSDPSRV', u'', u''] (Stable)
Or is that clear enough...? I'm not sure..
Original comment by jamie.l...@gmail.com
on 3 Feb 2011 at 8:49
ok nevermind... i have the correct update now looks good :-)
Original comment by jamie.l...@gmail.com
on 3 Feb 2011 at 9:01
Yep, sorry, that was my bad. r656 actually fixes it for Volatility_1.4rc1.
However, either way I'm now going to class it as... FIXED! 5:)
Original comment by mike.auty@gmail.com
on 3 Feb 2011 at 9:12
Original issue reported on code.google.com by
jamie.l...@gmail.com
on 3 Feb 2011 at 5:30