> > In RTSPClientConnection::handleRequestBytes, if a pointer wraparound
> > as checked at line 793 happens, parseSucceeded is set to false but
> > contentLength is still used to perform memmove at line 890.
> >
> > This might lead to invalid memory access.
>
> Yes, this is a problem. I have jus
> I have double checked, both issues still seem to affect 2019.05.03.
Thanks for the report.
> In RTSPClientConnection::handleRequestBytes, if a pointer wraparound
> as checked at line 793 happens, parseSucceeded is set to false but
> contentLength is still used to perform memmove at line 890.
>
> Sorry, but we do not use GitHub, and no copies of our code that other people
> have stored on GitHub (or any other third-party code repository) are
> supported by us. (These copies are often out-of-date, and/or contain unknown
> modifications. And quite often, these third-party copies of our
> On May 11, 2019, at 6:10 AM, Ross Finlayson wrote:
>
>
>
>> On May 6, 2019, at 8:03 PM, halim wrote:
>>
>> Hi.
>>
>> I am trying to implement H263VideoFileSink.
>
> Why not use our existing “H263plusVideoRTPSink” class?
My apologies. I misread your question. I see now that you are as
> Is it possible to create something like a RTSP client proxy that will proxy
> RTP packets and RTCP packets?
>
> To elaborate, my goal is not to do anything with RTP packets for now (later I
> will do something with the packets (like frame dropping)), but just to pass
> them trough the websock
> On May 6, 2019, at 8:03 PM, halim wrote:
>
> Hi.
>
> I am trying to implement H263VideoFileSink.
Why not use our existing “H263plusVideoRTPSink” class?
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live
Sorry, but we do not use GitHub, and no copies of our code that other people
have stored on GitHub (or any other third-party code repository) are supported
by us. (These copies are often out-of-date, and/or contain unknown
modifications. And quite often, these third-party copies of our code co
You’re going to have to be a lot more specific about why the “-m” option is not
working for you.
(And Remember, You Have Complete Source Code.)
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.l
This is very strange. The problem seems to be the "EBADF (Bad file
descriptor)”, which tells us that our event loop is trying to do a “select()”
on a socket that has already been closed. Our code has had bugs like this in
the past, but I had thought that we had caught them all by now.
I suspe
Hello my name is Nikola and started to work with the live555 library,
and I have a question.
Is it possible to create something like a RTSP client proxy that will proxy
RTP packets and RTCP packets?
To elaborate, my goal is not to do anything with RTP packets for now (later
I will do something wi
Hi.
I am trying to implement H263VideoFileSink. But I can't really figure
what is really needed at H263VideoFileSink::afterGettingFrame.
I try to refer from H264or5VideoFileSink::afterGettingFrame.
However, it is different from H263 as H263 doesn't have SPropRecord or SPS.
There is H263plusVid
Dear live555 developers,
It appears that two security issues, CVE-2019-7732 and CVE-2019-7733, have
been reported to the GitHub clone of live555[0][1]. I don't think they
were reported here.
Are you planning to address these issues in future releases?
Thanks for your work.
cheers,
Hugo
[0] htt
At this time, what I'm trying to do is create a snapshot of an openRTSP stream
(just capture a SINGLE frame(NOT CONTINOUSLY) for post processing for facial
recognition.
I've tried this option:
Outputting each frame into a separate file
If the "-m" option is given, each incoming 'frame' will be wr
--- Begin Message ---
Hello,
we are using openRTSP tool to record IP cameras stream into file.
Recently we have discovered, that sometimes ( maeby because of some
network issues ? ) some of the processes stucks at 100% cpu and stops
recording.
We are running multiple instances of openRTSP. I
14 matches
Mail list logo
