I am attempting to run a Red5 server to do something pretty simple. I want to stream from my local computer and have others view with an flash-based RTMP client across the web. I would like to password protect the server (so only I can stream to it), but I would like anyone to be able to connect to it. Given the apparent robustness of Red5 this seems like it would be fairly easy to set up.
I have used the oflaDemo to successfully stream and view my content, but I am ready to start my own VERY simple "application" in Red5 to achieve this. I am somewhat overwhelmed and don't know where to start because the documentation seems to have been written by someone apparently very much smarter than I am.
First of all, is using Red5 overkill? Is there a more simple approach that I can use to stream my content out to my web server? I am not trying to transcode or use objects or anything very complicated at all. Just use Red5 to get my content out there (Adobe Flash Media Server is VERY straightforward, but looking for an open-source alternative).
Second of all, if Red5 is the way I need to go, where can I go to learn to create a very simple "application" to stream out to the web?
My server is a dedicated box running Debian GNU Linux 7.0. Thanks!
Related
I am new to exploit development, and I am wondering how I could go about fuzzing a local application (e.g. Windows Media Player) using software if I did not have access to the source code. I have basic-intermediate knowledge of buffer overflow vulnerabilities, how they work, how to find them and how to write exploits for them. I just need the 2nd step - finding them in the first place...
Thanks!
Fuzzing is a useful tool but not necessarily easy. I'd suggest starting with listening to some talks online on fuzzing or doing some reading. The big picture is that you want to find a way to generate random/mutated input and then script your application to run with this random input. So for Windows Media Player, you might start by:
Figuring out how to run WMP in an automated/scripted way.
Looking for tools to generate fuzzed file input.
I have to make the online game as my project at the university.
The game must have
The server and the client of any turn-based game. Implementing the basic principles and rules of the game.
The server keeps a list of connected clients, runs the game, deals
processing and transfer of information. The application server with text-based interface
user concurrent operation. Client GUI
I would like to use Unity3D engine, but do not know if this is feasible.
How to make a console server for unity?
Feasible? yes
Easy, well, it depends of your aproach, but it is completly possible, there exist some people than do it with Node.js
But, if your thing is turn based, then maybie you can do an invention with a webserver (like uniserver for example, or Xamp, or some other Apache / mysql implementation) and, inside unity, use the WWWForm class.
https://docs.unity3d.com/ScriptReference/WWWForm.html
Is a little cheaty, but it's maybie the easiest way for testing purposes (in no way you must use it for production of a serious game if you have any decent, fast (for production) and secure aproach to the subject, which this is not.
Cheers
I am a newbie to jitsi.
I have the following problem that I need to solve:
I want to stream the video via my web cam pointed over my home car parking.
The video stream would be received at my office laptop.
As such I want to keep an eye on my parked car at home via my web cam.
Following are my questions now:
I am able to run the Libjitsi sender and receiver (sample) code for my web cam, on a local network setup.
How can I use ice4j to enable streaming across networks as the Jitsi product is able to do.
Moreover I am also interested in knowing how Jitsi video calling works and what components/protocols are involved, so that I can leverage that for my own solution
I have hosted an openfire xmpp server of mine to facilitate communication for session management for Libjitsi.
Please reply suitable links, reference etc.
java-bells is a "library" designed to wrap ice4j, libjitsi and smack and even contains a sample for making a connection. Since ice4j and libjitsi are, for all intents and purposes undocumented black-boxes, I created java-bells as a thin wrapper around those libraries to make them a bit easier to use. You could also think of it as a demonstration of how to use those libraries. In other words, you might choose to use java-bells directly as a library or just look at java-bells to see how it works and write your own code. Since trying to figure that out by using the jitsi source alone is an exercise in futility, and I don't know of any other approach, I think this is what you should do.
As for docs about the protocols themselves, I only know of the RFCs and the wikipedia pages.
I'm trying to set up some integration between Chrome, and various command-line tools and build systems that I have. Almost everything that I want to do within Chrome is supported by the extensions API, so I figured I'd make an extension, set up communication between it and my external tools, and go from there.
Unfortunately, I can't find any sane way to get messages in and out of Chrome. The only thing I could find that would plausibly work at all, would be introduce a local web server as a message broker, having the extension connect to it with WebSockets, and then having the command-line utilities do the same. But that's way too much complexity - it'd basically mean writing a whole IPC framework.
Is there any reasonable way to do this?
There is currently no way to let extensions communicate outside Chrome without XHR/WebSockets/SocketAPI or any traditional methods like Image URLs, JavaScript URLs etc.
If you want make an overkill, you could try creating a NPAPI Plugin that writes protocol messages to disk/file (like how Apache WebServer does), and create another standalone Python script/or any other scripting language that tails that. So your API would basically read that file that the NPAPI Extension Plugin creates.
I want to try developing an XMPP server component using XEP-0114: Jabber Component Protocol.
Which server do you recommend and why? I'm talking about ease of development, community support, documentation, examples, etc.
That's a hard question to answer, because I doubt there are many developers involved in developing across multiple XMPP projects and languages.
I can throw out a few personal perceptions but... I could be off-base!
What you're really looking for is which libraries would be recommended for component development. All the servers support the component protocol, so all you really need is a socket connection to the server and some helper routines to make the repetitive stuff like message parsing easier.
Where the server might matter is if you need tighter integration.
For example if you want your component to scale the same way as Ejabberd then you'll probably want to use exmpp.
If you need to deploy your component alongside Openfire into Java only enterprises, then you'll probably want to use smack.
If you are familiar with Python and want to prototype quickly use Wokkel.
I don't think documentation is going to be great for any of the libraries (haven't looked at them all though!) but that shouldn't be a huge burden. All you really need a good book on how the XMPP protocol works and then some sample code from the library and it's fairly easy to move on from there.
For an easy-to-use testing server I like openfire. Good instructions, easy to hook in components, and a good web interface for administration. Debugging is more of a "tail -f" on the logfiles, slightly java-ish.
I've used XCP professionally, but that's really for commercial use. It works well but if that's not your target deployment it's not worth the effort. I'm not sure if you can buy it separately any more.
I tried using ejabberd and I gave up quickly. I found the documentation for setup and administration awful. The config files are not self describing and there's no good walk through on the ejabberd site. It may be able to even fry my eggs in the morning for breakfast, but I couldn't get past install with the time I'd allotted to it.
For Openfire, there is something called Whack, which is a Java library for creating server components (XEP-0114).
Since the communication is over sockets, I presume the same code should work for any well designed XMPP server (such as ejabberd). However, I have only tested it with Openfire and it works quite well.