Hi Ross,

I have raised this with Point Grey and am awaiting a response, but was looking for a way to proceed in the meantime. I don't have access to their code, but I do have access to the live555 library source and I'd like to make some progress elsewhere.

Also, whilst I'm not arguing about the validity or otherwise of the cameras response (I'm no RTP expert), isn't it reasonable to interpret this as a security hole in the live555 library? This failure mechanism shows that it is easy for someone to remotely inject a frame of data into any client that uses this library and the client has no way of knowing that it is not from the source it expects.

Best Regards,

Jonathan

On 27/10/16 21:04, Ross Finlayson wrote:
No - this is much more complicated than you think.  Media ‘source’ objects are 
currently bound tightly to individual network sockets.  This won’t be changing 
until the code undergoes a major overhaul to ‘virtualize’ network interfaces - 
something that will be done as part of the “IPv6 Support” funded project:
        http://live555.com/funded-projects/live555_ipv6.html
Feel free to contribute to (i.e., help fund) this project if you wish.


Once again: The solution to your problem is to ***fix your buggy network 
cameras***.  Remember that these cameras are things that YOU HAVE PAID MONEY 
FOR.  And they have a KNOWN BUG.  Therefore, you should be putting pressure on 
the camera manufacturer (Point Grey) to fix them.  (In contrast, the “LIVE555 
Streaming Media” software is something that you have paid nothing for.  You 
should have no expectation that it should undergo changes simply to try to 
compensate for someone else’s bug)

I would be happy to work with the camera manufacturer (Point Grey) to help them 
fix this bug, should they be interested.


Ross Finlayson
Live Networks, Inc.
http://www.live555.com/


_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

Reply via email to