Re: [Live-devel] Bug report: crash when RTSP register/deregister

Thanks for the report. I have just released a new version (2021.05.22) of the code that includes your patch. Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com

Re: [Live-devel] Bug report: crash when RTSP register/deregister

- development & use Subject: Re: [Live-devel] Bug report: crash when RTSP register/deregister > On May 17, 2021, at 3:04 AM, mario.takeu...@sony.com wrote: > > Hello, > > We found a crash problem in liblivemedia (2018.02.18-1) packaged for Ubuntu > Bionic. > It's

Re: [Live-devel] Bug report: crash when RTSP register/deregister

> On May 17, 2021, at 3:04 AM, mario.takeu...@sony.com wrote: > > Hello, > > We found a crash problem in liblivemedia (2018.02.18-1) packaged for Ubuntu > Bionic. > It's a bit old version, but I think it has not been fixed in the latest > version. Sorry, but we support only the latest versio

Re: [Live-devel] Bug report

So is it ok if I request one, or is this something someone else from the dev team does? On wo, 27 feb 2019 16:45:26 +0100 Ross Finlayson wrote > On Feb 28, 2019, at 1:38 AM, Mans van Someren > wrote: > > So why did other vulnerabilitie

Re: [Live-devel] Bug report

> On Feb 28, 2019, at 1:38 AM, Mans van Someren wrote: > > So why did other vulnerabilities get a CVE? Other people arranged to create those. But this is not something that I do. Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ liv

Re: [Live-devel] Bug report

So why did other vulnerabilities get a CVE? On wo, 27 feb 2019 15:28:11 +0100 finlay...@live555.com wrote > On Feb 28, 2019, at 12:11 AM, Mans van Someren wrote: > Will you also request a CVE for this vulnerability? No. Ross Finlayson Live Networks, Inc. http://www.live555.com/

Re: [Live-devel] Bug report

> On Feb 28, 2019, at 12:11 AM, Mans van Someren wrote: > Will you also request a CVE for this vulnerability? No. Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list live-devel@lists.live555.com http://lists.live5

Re: [Live-devel] Bug report

Hello Ross, Im very pleased to hear that you fixed the vulnerability so fast after my report to the mailing list. Will you also request a CVE for this vulnerability? Kind regards, Mans van Someren On wo, 27 feb 2019 10:00:26 +0100 Ross Finlayson wrote Thanks for the n

Re: [Live-devel] Bug report

Thanks for the note. First, please note that we do not support any version of the LIVE555 code that’s hosted on a third-party site (e.g., ‘GitHub’). Nor should any bug reports be filed at such sites (because we won’t get to read them). Instead, bug reports should be filed only using this mail

Re: [Live-devel] Bug report of Live555ProxyServer

Sorry, but unless you can be a *lot* more specific about what problem you are seeing - and can reproduce it with just two streams, not 14 - then I doubt I’m going to be able to help you (and certainly, not ‘for free’ on this mailing list). Ross Finlayson Live Networks, Inc. http://www.live555.c

Re: [Live-devel] Bug report of Live555ProxyServer

come a great product. I’d like to thank you for your great work. Thanks lots again and best regards Dashan From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: Friday, February 27, 2015 2:13 PM To: LIVE555 Streaming Media - development & use Subje

Re: [Live-devel] Bug report of Live555ProxyServer

Dashan, First, your log file reveals that you have made at least some changes to the supplied code. We can support only the original, unmodified code. Second, your first test shouldn’t be with such a large number of proxied streams. Can you reproduce your problem with just two streams? Third,

Re: [Live-devel] bug report

You are right. Thank you. > >Hi, >> >>I think there is an error in function >>MPEG2TransportStreamIndexFile::readIndexRecord(). >>The line: >> >>++fCurrentIndexRecordNum; >> >>should be: >> >>fCurrentIndexRecordNum = indexRecordNum; >> >>is it? > > No, the current code is correct. "readIndexRe

Re: [Live-devel] bug report

Hi, I think there is an error in function MPEG2TransportStreamIndexFile::readIndexRecord(). The line: ++fCurrentIndexRecordNum; should be: fCurrentIndexRecordNum = indexRecordNum; is it? No, the current code is correct. "readIndexRecord(indexRecordNum)" starts by seeking to "indexRecord