[Fatal Error] :1:1: Content is not allowed in prolog. about armitage HOT 9 CLOSED

Ok, this is a fun one. What is your unicode locale on your computer? Open a 
terminal and type:

echo $LANG

and paste the output here. I suspect that because your locale is something 
different, the chars I'm sending over the socket are being encoded in a weird 
way causing the software to freak out. 

If you want to test this hypothesis, do:

export LC_CTYPE=en_US.UTF-8
export LANG=en_US.UTF-8
java -Dfile.encoding=UTF-8 -jar armitage.jar

Let me know if it works with UTF-8. If it does, I'll either come up with a work 
around or document this situation in the FAQ. If it doesn't, back to square one.

My LC_CTYPE was set, but not the LANG.

Bad news, doesn't work with UTF-8 or en_US.UTF-8 for LANG and LC_CTYPE


chri@ceto:~/Tools/armitage/armitage-read-only
$ export LC_CTYPE=en_US.UTF-8
chri@ceto:~/Tools/armitage/armitage-read-only
$ export LANG=en_US.UTF-8
chri@ceto:~/Tools/armitage/armitage-read-only
$ java -Dfile.encoding=UTF-8 -classpath bin:lib/\*:. armitage.ArmitageMain $*
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.

Could you point out where in the code you think it's failing? Maybe I can help 
look at that code and help a little with the debugging...

I'm a little bit confused you talk about a socket, because the error is caused 
by a  SAXParseException. Which is from my limited experience triggered by a 
malformed XML or DTD. Where is the socket playing a part in this? 

Armitage communicates with MSFRPCD over XMLRPC. I'm using scriptjunkie's code 
in src/msf/RpcConnection.java   This hides all of the non-stop XML excitement.

If you shoot an email to [email protected], I'll add some debug 
code to RpcConnection.java and send you an updated .jar to try. This will help 
us narrow down the problem more efficiently.

I did shoot an email on the 7th of December, but got no reply back...
Don't hesitate to send me that jar with debugcode.

Cheers

Yeap, thanks for getting that to me. I still owe you a debug jar, I've just 
been really busy lately. 

Ok, I've created a jar file with some debug code. It's at: 
http://armitage.googlecode.com/svn/trunk/release/armitage-unix/armitage.jar

Execute Armitage with java -jar armitage.jar -d. Do your normal stuff, it'll 
create a debug.log file in the current directory. Go ahead and email that to 
me. 

The debug.log file will contain some info about your system 
(System.getProperties().toString() in Java) and a log of the entire 
conversation between Armitage and MSFRPCD.

I am a little bit ashamed/annoyed,
the error was caused by a mistyped parameter in the msfrpcd command.
Sorry for the false-alarm

However, there are other issues now depending on the revision...
I'll first try to debug them a little more and will then create a new Issue. 

What parameter did you mistype? I'll keep this info on hand in case it comes up 
again. If someone else reports it, I'll toss it into the FAQ. No need to be 
annoyed or ashamed.

Well, I plan to submit a patch (this week-end) to make the login screen GUI 
more clear. To distinguish between the MSF parameters and mysql params more 
clearly.