Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: mpjpeg fails on wansview 1080p (Joseph Heenan)
2. request for comment: naming threads (Joseph Heenan)
3. Re: mpjpeg fails on wansview 1080p (tosiara)
4. Re: mpjpeg fails on wansview 1080p (John Baker)
----------------------------------------------------------------------
Message: 1
Date: Sun, 7 Aug 2016 11:24:34 +0100
From: Joseph Heenan <[email protected]>
Subject: Re: [Motion-user] mpjpeg fails on wansview 1080p
To: Motion discussion list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
2 doesn?t seem a particularly high priority to me given that the camera works
with motion using rtsp (which does support digest auth), but I may have missed
something.
Joseph
> On 7 Aug 2016, at 08:08, tosiara <[email protected]> wrote:
>
> So here we have two issues:
> 1. motion should better handle 401 or any non-200 http status and show user
> friendly error
> 2. digest auth support
>
> The first would probably be an easy code change
> But the second would be a challenge. We can implement digest auth. Or. There
> was a discussion already to replace all the manual http code by some web
> library that provides better support and better maintained. But that requires
> also quite a lot of efforts to change the code
>
> On Sun, Aug 7, 2016 at 9:25 AM, John Baker <[email protected]
> <mailto:[email protected]>> wrote:
> So being more awake this morning, I now spot the problem. The camera
> wishes to use HTTP digest authentication, which I guess motion doesn't
> support (another on the todo list Mr Dave / Joseph ?:).
>
> http://stackoverflow.com/questions/2384230/what-is-digest-authentication
> <http://stackoverflow.com/questions/2384230/what-is-digest-authentication>
>
> Example:
>
> > HEAD /mjpeg/stream.cgi?chn=0 HTTP/1.1
> > Host: 192.168.0.102
> > User-Agent: curl/7.49.1
> > Accept: */*
> >
> < HTTP/1.1 401 Unauthorized
> < WWW-Authenticate: Digest realm="IPCamera Login",
> nonce="f35b3a998c0b964d21d99da3f8880f14", qop="auth"
>
> > HEAD /mjpeg/stream.cgi?chn=0 HTTP/1.1
> > Host: 192.168.0.102
> > Authorization: Digest username="visitor", realm="IPCamera Login",
> > nonce="f35b3a998c0b964d21d99da3f8880f14", uri="/mjpeg/stream.cgi?chn=0",
> > cnonce="MWY1N2M3NmUzMjNlODIxM2ZjMzAxYTcyNTIzMjA0MTY=", nc=00000001,
> > qop=auth, response="3bb6cbc93342432432421104ebeed5c3a"
> > User-Agent: curl/7.49.1
> > Accept: */*
> >
> < HTTP/1.1 200 OK
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> [email protected] <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/motion-user
> <https://lists.sourceforge.net/lists/listinfo/motion-user>
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> <http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Sun, 7 Aug 2016 11:30:43 +0100
From: Joseph Heenan <[email protected]>
Subject: [Motion-user] request for comment: naming threads
To: Motion discussion list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi all,
Not really sure how MrDave plans to manage commits going forward, but here?s an
interesting (to me at least) one that I?d welcome any comments on:
https://github.com/jogu/motion/commit/cdd8b988fb08a486e98da5516d7faaf4a3b9f542
(There?s a few other commits in my repo too,
https://github.com/jogu/motion/commits/master but most of the others are just
simple bug fixes, but if anyone spots anything odd in those do let me know.)
Cheers
Joseph
------------------------------
Message: 3
Date: Sun, 7 Aug 2016 16:55:36 +0300
From: tosiara <[email protected]>
Subject: Re: [Motion-user] mpjpeg fails on wansview 1080p
To: Motion discussion list <[email protected]>
Message-ID:
<CACHTdwQTq_KZdJOcTGsk3OCz30njYcoKSo=xob_cnkjv0kr...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Kenneth,
the was suggestion to use libmicrohttpd which seems a good choice and is
really not too heavy for motion:
https://github.com/Mr-Dave/motion/pull/94#issuecomment-159535262
On Sun, Aug 7, 2016 at 1:24 PM, Joseph Heenan <[email protected]> wrote:
> 2 doesn?t seem a particularly high priority to me given that the camera
> works with motion using rtsp (which does support digest auth), but I may
> have missed something.
>
> Joseph
>
>
> On 7 Aug 2016, at 08:08, tosiara <[email protected]> wrote:
>
> So here we have two issues:
> 1. motion should better handle 401 or any non-200 http status and show
> user friendly error
> 2. digest auth support
>
> The first would probably be an easy code change
> But the second would be a challenge. We can implement digest auth. Or.
> There was a discussion already to replace all the manual http code by some
> web library that provides better support and better maintained. But that
> requires also quite a lot of efforts to change the code
>
> On Sun, Aug 7, 2016 at 9:25 AM, John Baker <[email protected]> wrote:
>
>> So being more awake this morning, I now spot the problem. The camera
>> wishes to use HTTP digest authentication, which I guess motion doesn't
>> support (another on the todo list Mr Dave / Joseph ?:).
>>
>> http://stackoverflow.com/questions/2384230/what-is-digest-authentication
>>
>> Example:
>>
>> > HEAD /mjpeg/stream.cgi?chn=0 HTTP/1.1
>> > Host: 192.168.0.102
>> > User-Agent: curl/7.49.1
>> > Accept: */*
>> >
>> < HTTP/1.1 401 Unauthorized
>> < WWW-Authenticate: Digest realm="IPCamera Login",
>> nonce="f35b3a998c0b964d21d99da3f8880f14", qop="auth"
>>
>> > HEAD /mjpeg/stream.cgi?chn=0 HTTP/1.1
>> > Host: 192.168.0.102
>> > Authorization: Digest username="visitor", realm="IPCamera Login",
>> nonce="f35b3a998c0b964d21d99da3f8880f14", uri="/mjpeg/stream.cgi?chn=0",
>> cnonce="MWY1N2M3NmUzMjNlODIxM2ZjMzAxYTcyNTIzMjA0MTY=", nc=00000001,
>> qop=auth, response="3bb6cbc93342432432421104ebeed5c3a"
>> > User-Agent: curl/7.49.1
>> > Accept: */*
>> >
>> < HTTP/1.1 200 OK
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>
>
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
>
>
> ------------------------------------------------------------
> ------------------
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Sun, 07 Aug 2016 15:10:41 +0100
From: John Baker <[email protected]>
Subject: Re: [Motion-user] mpjpeg fails on wansview 1080p
To: [email protected]
Message-ID:
<1470579041.1169775.688344665.769ea...@webmail.messagingengine.com>
Content-Type: text/plain; charset="utf-8"
> 2 doesn?t seem a particularly high priority to me given that the camera works
> with motion using rtsp
> (which does support digest auth), but I may have missed something.
That's right, it's not a big issue but I think two logging changes are
required:
1. Hack the HTTP code to warn if it receives a request for digest
authentication.
2. Do not start trying to read images if a 401 is received after sending
the Authorization header.
The HTTP code sounds beyond hope so I digest can be sorted when the HTTP
code is ejected in place of a library; I assume any modern good library
would support Digest.
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 123, Issue 19
********************************************
