Volatility Error - The requested file doesn't exist - volatility

I am running the program Volatility on a Kali Linux machine. However, whenever I try the command
vol -f <memdump name> <plugin name>
I get the error
ERROR: volatility.plugins.fileparam: The requested file doesn't exist
I tried downloading the source code and running Volatility as a python script, and I've tried changing and for the command above, but the error persists.
Any idea how to fix it?

Replacing the memdump name with the absolute path of the memdump name seems to do the trick. This is clearly a bug with the program.
Bug Report!

This is Bug. O.K. No solution at all, that's also O.K.
Replacing file name with full path, doesn't appear to work.

Related

WSL Not able to find file or directory due to space

The error I was originally getting was that wsl was not able to find JAVA_HOME. After I ran the command
export JAVA_HOME="/mnt/c/Program Files/JAVA/jdk-15.0.2"
And now the error it gives me is:
ERROR: JAVA_HOME is set to an invalid directory: /mnt/c/Program Files/Java/jdk-15.0.2
Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.
When I run
${JAVA_HOME}
to check the variable I get the response
bash: /mnt/c/Program: No such file or directory
Which I believe is due to the space in the file name. Online it said that the space shouldn't be an issue as it is enclosed in quotes so I don't know what to do here.
Any help would be appreciated!
It looks like you are trying to use the Windows version of Java from within WSL. That should be possible, but you are currently exporting a Linux-style path, which the Windows version won't handle (as you can see).
If you have both the Windows and Linux version of Java installed, then see this answer for some related information. The question there is about npm, but the core issue is the same -- The Windows version is getting picked up in the path before the Linux version.
If you just have the Windows version, then at least modify the JAVA_HOME to be 'C:\Program Files\JAVA\jdk-15.0.2' (watch out for potential quoting issues with backslashes in the Linux-shell string, though). I'm not sure that's going to take care of all of your issues -- I've never tried running the Windows Java version through WSL myself. But it's at least the first step you're going to need to take to get past the current error.
The second error when you just execute ${JAVA_HOME} is to be expected, as you are trying to execute this directory (with a space) as a command. The shell is interpreting the portion before the space as a command, and the portion after the space as the argument. If you were to set it to a directory without a space, you'd still get an error message when trying to execute it (as you are now), just that it would be something like bash: /mnt/c: Is a directory.
If you just want to check it, use echo ${JAVA_HOME}.

Error in LeNet on MNIST example

I followed the guidance under the Training LeNet on MNIST with Caffe but I've got a error when creating lmdb..
$ ./examples/mnist/create_mnist.sh
Creating lmdb...
F:/program files/caffe/build/examples/mnist/convert_mnist_data.exe:
error while loading shared libraries: boost_python-vc140-mt-1_61.dll: cannot open shared object file: No such file or directory
I'm using GIT Bash for run the shell script,
so what is wrong?
It appears that the linker/loader does not have access to that Python BOOST library. Did you run the scripts needed to set your environment variables? I suspect that there's a missing path in your LD_LIBRARY_PATH.
As a stop-gap, you can locate the missing file with
find / -name boost_python-vc140-mt-1_61.dll
... and then manually add that path to LD_LIBRARY_PATH. The problem is that you'll hit thesefiles/caffe/build/examples/mnist/convert_mnist_data.exe one at a time until you get them all.
You can also try
ldd files/caffe/build/examples/mnist/convert_mnist_data.exe
... and see what you might be missing.

Installing hadoop issue

I am following Joseph Adler instructions on how to install ( page 555 here - http:// it-e
books. info/book/1014/ ) Hadoop on my lubuntu.
I wrote in terminal:
wget http://archive.cloudera.com/cdh/3/hadoop-0.20.2-cdh3u4.tar.gz
tar xvfz hadoop-0.20.2-cdh3u4.tar.gz
and everything went fine, .tar.gz file was downloaded and then it was untarred.
But when I wrote
hadoop version
in the terminal, there appeared a message saying that there is no command hadoop.
Does anybody has an idea on what should I do to use (already) installed but (still) somehow invisible Hadoop?
Thanks for help!
In Linux invoking a command without prefixing its path requires the location where the command resides should be present the environment variable PATH.
Here, For executing the command you got to specify either absolute or relative path of the command. Following can be used, replace with the extracted location.
<EXTRACT_LOC_PATH>/hadoop-0.20.2-cdh3u4/bin/hadoop version
If your present working directory is /hadoop-0.20.2-cdh3u4/bin/ then ./hadoop version would be sufficient.
Whenever you are getting COMMAND NOT FOUND ERROR the problem will be there in .bashrc file only. You might not have properly set the JAVA_HOME, HADOOP_HOME and PATH Variable. So check it out whether you have given proper path for all these 3 variables or not.

Getting "The syntax of the command is incorrect." when running new Amazon CLI

Running Python27 on windows. Trying to run the new AWS command line interface (found here: http://aws.amazon.com/cli/) , and getting the error "The syntax of the command is incorrect." when running anything.
Even "aws help" gives this error. I know everything is installed because a regular garbage command (asdf) gives a different error.
I get the same error in powershell as in cmd.
Googling around, the error is typically encountered when renaming/moving a file that has a space in it without using quote marks. I had hoped moving my python install to c:\python27\ would fix the issue, but it has not.
Moving python to a non-space having path was the correct choice.
The aws command is a little aggressive in finding all your python installs. It searches your PATH directories for python.exe (or .bat or .cmd). I had changed this manually when I moved my python directory.
It also searches your file associations (which I had not changed) and was still finding c:\program files\python27\ and was choking on the space.
This question helped me fix the file associations, and I'm good to go now.
How do you change file association for .py Python files in XP?
If you find the aws command slightly slow, you probably speed it up by skipping all this searching nonsense and just hard coding your python.exe path into the aws.cmd file.

an error in plone theming

I installed Plone 4.1.3 and I am trying to make a theme. I saw this link talk about this issue:
http://www.treebrolly.com/blog/turbo-plone-theming-with-xdv-diazo
and I followed the commands. When I run this command
$ ./bin/instance fg
it says
Error: error opening file /home/hosam/plone413/zinstance/parts/instance/etc/zope.conf: [Errno 2] No such file or directory: '/home/hosam/plone413/zinstance/parts/instance/etc/zope.conf'
For help, use ./bin/instance -h
hosam#hosam-desktop:~/plone413/zinstance$
I noticed that when I run this command
$ ./bin/buildout -c demo.cfg
this directory and its contents are deleted /home/hosam/plone413/zinstance/parts/instance/
and so this error appears to me, Any can help??
When you run :
$ ./bin/buildout -c demo.cfg
the parts folder is supposed to be deleted and rebuilt (that's fine).
The error you are facing says that this command doesn't end correctly. Try to add the -v parameter
$ ./bin/buildout -v -c demo.cfg
so you will have a more verbose output and you can provide here a complete error traceback
Set up your demo.cfg in a different buildout directory. Looking at the blog entry you mentioned, it's meant to standalone, not share the same buildout directory with a zope/plone instance.
You might want to consider using plone.app.theming instead of XDV. The big difference is that plone.app.theming runs inside Plone and doesn't require any separate build. That really simplifies things if you don't need to mix in content from non-Plone sources.

Resources