I'm capturing nimbuzz traffic on ipad galaxy and pc and it seems sometimes the traffic in the xmpp is some binary? is it encrypted? does anyone know how to read it ? it is not in plain text.. example to a packet text : is it compressed perhaps? does anyone know how to decompress it?
\262\311,\004\371E\311\320\300\330$>\263 #?/53%^I\241\244\262 \325V\t\250\2424\247D\211D\327\331\331de\246\330\025\344\224\002\2238(\225\033: \205\213>\304\022SKc#`v\002)\264\321\a\351\002R\231\205v\000\000\000\000\377\377
It might be both compressed and encrypted. Please start by reading RFC 6120, then perhaps XEP-0138.
Related
(^.^)"Hi again sorry for my English is not good if someone like correct my redaction I would appreciate this"
Hi, is anybody now if I can capture IVs with my iphone from the wi-fi networks , any source code, Api, tutorial, etc.. who can make this who can put the iphone wifi promiscuous mode monitor to capture packets.
I've looking for but can not find nothing.
Thanks.
Take a look at Stumbler.
Note that it uses private APIs so most of this code is not suitable for
App Store aplications. But as a learning resource it's priceless.
I'm new to these things, and have no idea how to achieve this thing.
I want to send some data from iphone to MAC/PC and also want to receive data sent from MAC to iphone.
Please help me out or give me some clue, where I can start from.
Most apps solve this issue by including a small http server in the app and providing a web interface to upload/download data to the app.
I am trying to make a program that receives UDP data on a port that the user can choose. For this i am using asyncUdpSocket.
I could not find it but i believe there is a way to send data from your mac to the simulator. Can anybody tell me how to do this?
Thanks!
It seems that you can just call the simulator on the ip adress of the mac you are running on.
Sorry for bothering everybody.
I'm planning on building an application where audio media is going to be streamed to the mobile phone for the user to listen.
The targets are smartphones: iPhone/Blackberry/Android/(J2ME ?).
I see that streaming on iPhone has to be done with HTTP Live streaming, but I don't see it supported by other platforms.
Should I broadcast the streams via rstp ? http ? Is there any way to use a unified solution for all the different mobile platform ? If anyone already had to go through this, help would be greatly appreciated.
One answer to the question "what technology to use ?", for iPhone specifically is WiFi. I know that's not the type of question you are asking, but its a point worth making! Many apps that support streaming over 3G have been rejected by Apple due to bandwidth usage. You may need to be prepared to sense network connection type and limit streaming to when you have a WiFi connection only.
Blackberry works with http and RSTP on OS 4.3 or later. I'm not familiar with other platforms but I would think http would be the most compatible.
Here is a PDF that lists the supported types by the major models.
http://docs.blackberry.com/en/smartphone_users/deliverables/15801/711-01774-123_Supported_Media_Types_on_BlackBerry_Smartphones.pdf
You will probably want to do RTSP, but it doesn't really matter. HTTP Live Streaming is just a protocol on the client side I am pretty sure. All these acronyms just describe ways of transmitting data. If a browser can access the data for a given protocol....chances are a phone can too. It sounds like you are asking more of a server side question.....but that question is the least of your worries You are going to have to think more along the lines of "How am I going to scale this" rather than "What protocol should I use to transmit data". Also, the unified solution for all clients, would be to have a server that they all hit for data. You still need to develop separate clients for each OS.
Both Android and BlackBerry supports RTSP.
Note that some BlackBerry devices only support 15fps video, so you may need separated streams to give the best experience to your users.
iPhone, starting from iPhone OS 3.0, needs HTTP Live Streaming.
The only software solution I know to support all above is Wowza, but you still need an encoder. (I think Wowza supports RTP as input, but need double checking.)
iPhone can play non-streamed audio (progressive download). Considered all platforms you would normally you just needs streams that are suitable transcoded. See f.e. https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/StreamingMediaGuide/Introduction/Introduction.html The title says its about 'HTTP Live Streaming' but a lot applies for just downloading and playing streams.
I have made Iphone applicatio. In my application whatever data i have recorded; all that data i want to export to the Computer using the application.
Is there any way available to sent data to computer using wifi using developed application? Can we use Bluetooth or Http connection to send application from device to the PC?
if we can than how can we manage the bluetooth and how to use it without Jailbreaking?
if any body has any solution,please give any code or any link or any other solution which would appreciated.
Thanks,
Mishal
Your best bet is to send the data using HTTP or FTP to a server, which could be your PC. Would that work for you?
Here's one way to do it.
Here's another.
And one for FTP.
I dont think you have an option to gain control of a computer and toss a file in there from within an iPhone app. You cannot do it over the usb cord, you cannot mount the drive unless you roll your own fs mounter (pretty difficult), and you cannot push a file over html or something and have it magically appear. The user would have to interact at some point.
Many times, this is done over html. In my apps, I use CocoaHTTPServer to get local info into and off of the phone. You run the server and out-of-the-box, it indexes all the files in the documents directory for you to download from any browser on the same wifi network. Give it a shot as it is a easy to implement solution for getting large files off the phone without having to resort to something clunky like email