From: Juergen E. <fli...@te...> - 2008-08-03 15:18:43
|
Hi Kenneth and All, I'm successfully using Motion v3.2.8 in combination with an Axis ip-camera. Now I tried to add an additional Axis camera which can only be accessed via https and username/password authentication. Although I've entered the URL and the authentication credentials properly the camera cannot be accessed. Now I wonder if Motion supports this access method at all. I've searched the website for further information but without success. Kind regards, Juergen -- Mail: fli...@te... |
From: Angel C. <ac...@te...> - 2008-08-03 15:55:29
|
El dom, 03-08-2008 a las 17:18 +0200, Juergen Edner escribió: Hi Juergen, > Hi Kenneth and All, > I'm successfully using Motion v3.2.8 in combination with > an Axis ip-camera. > Now I tried to add an additional Axis camera which can only > be accessed via https and username/password authentication. motion doesn't support secure socket layer using HTTP. > Although I've entered the URL and the authentication > credentials properly the camera cannot be accessed. > > Now I wonder if Motion supports this access method at all. > I've searched the website for further information but > without success. You can file a new feature in Twiki though :) > Kind regards, > Juergen Cheers, -- Angel Carpintero ack ( at ) telefonica ( dot ) net Key fingerprint = 3FD3 9C90 149E 7824 CECD 6BCF AC2C CA61 6EF1 B90D "No basta saber, hay que aplicar lo que se sabe; no basta querer hacerlas cosas, hay que hacerlas". "Knowing is not enough; we must apply. Willing is not enough; we must do" Johann Wolfgang von Goethe |
From: Jeff G. <jg...@kr...> - 2008-08-03 17:08:16
|
Would stunnel be a solution? I know at work we've used stunnel in the past as a "quick and dirty" method of providing an encrypted connection. Jeff G. Aurélien wrote: > On Sun, Aug 3, 2008 at 5:55 PM, Angel Carpintero <ac...@te... > <mailto:ac...@te...>> wrote: > > El dom, 03-08-2008 a las 17:18 +0200, Juergen Edner escribió: > > Hi Juergen, > > > Hi Kenneth and All, > > I'm successfully using Motion v3.2.8 in combination with > > an Axis ip-camera. > > Now I tried to add an additional Axis camera which can only > > be accessed via https and username/password authentication. > > motion doesn't support secure socket layer using HTTP. > > > Although I've entered the URL and the authentication > > credentials properly the camera cannot be accessed. > > > > Now I wonder if Motion supports this access method at all. > > I've searched the website for further information but > > without success. > > You can file a new feature in Twiki though :) > > > > In the meantime, perhaps the following (untested) solution may work > on Linux: > > # nc -l -s 127.0.0.1 <http://127.0.0.1> -p <local_port> -c 'openssl > s_client -connect <axis_ip>:<axis_port> -quiet 2>/dev/null' > > This should open on <local_port> a tunnel to the camera using SSL > located at <axis_ip>:<axis_port> upon connection. > > Your camera should then be accessible at http://localhost:<local_port>/ . > > This is not ideal, but it may help you if SSL is absolutely required. > > Good luck :) > > Regards, > -- > Aurélien Guillaume > - 90% of statistics are made up. The remaining 20% are put together by > people who are bad at math. > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ------------------------------------------------------------------------ > > _______________________________________________ > Motion-user mailing list > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome > |
From: A. <aur...@ny...> - 2008-08-03 22:24:42
|
On Sun, Aug 3, 2008 at 7:08 PM, Jeff Groves <jg...@kr...> wrote: > Would stunnel be a solution? > > I know at work we've used stunnel in the past as a "quick and dirty" method > of providing an encrypted connection. > I forgot stunnel :) But yes, it's the same basic functionnality as the one i provided, but more polished :) Sorry ^^ > > Aurélien wrote: > > On Sun, Aug 3, 2008 at 5:55 PM, Angel Carpintero <ac...@te...> > wrote: > >> El dom, 03-08-2008 a las 17:18 +0200, Juergen Edner escribió: >> >> Hi Juergen, >> >> > Hi Kenneth and All, >> > I'm successfully using Motion v3.2.8 in combination with >> > an Axis ip-camera. >> > Now I tried to add an additional Axis camera which can only >> > be accessed via https and username/password authentication. >> >> motion doesn't support secure socket layer using HTTP. >> >> > Although I've entered the URL and the authentication >> > credentials properly the camera cannot be accessed. >> > >> > Now I wonder if Motion supports this access method at all. >> > I've searched the website for further information but >> > without success. >> >> You can file a new feature in Twiki though :) >> > > > In the meantime, perhaps the following (untested) solution may work > on Linux: > > # nc -l -s 127.0.0.1 -p <local_port> -c 'openssl s_client -connect > <axis_ip>:<axis_port> -quiet 2>/dev/null' > > This should open on <local_port> a tunnel to the camera using SSL > located at <axis_ip>:<axis_port> upon connection. > > Your camera should then be accessible at http://localhost:<local_port>/ . > > This is not ideal, but it may help you if SSL is absolutely required. > > Good luck :) > > Regards, > > -- Aurélien Guillaume - 90% of statistics are made up. The remaining 20% are put together by people who are bad at math. |
From: Juergen E. <fli...@te...> - 2008-08-11 16:06:34
|
Hello Aurelien and Jeff, > Would stunnel be a solution? > > I know at work we've used stunnel in the past as > a "quick and dirty" method of providing an encrypted > connection. thank you for your hints. I've successfully set-up a stunnel connection to the ip-camera over which the normal http-authentication can be used. Regards, Juergen -- Mail: fli...@te... |
From: A. <foo...@gm...> - 2008-08-03 16:38:28
|
On Sun, Aug 3, 2008 at 5:55 PM, Angel Carpintero <ac...@te...> wrote: > El dom, 03-08-2008 a las 17:18 +0200, Juergen Edner escribió: > > Hi Juergen, > > > Hi Kenneth and All, > > I'm successfully using Motion v3.2.8 in combination with > > an Axis ip-camera. > > Now I tried to add an additional Axis camera which can only > > be accessed via https and username/password authentication. > > motion doesn't support secure socket layer using HTTP. > > > Although I've entered the URL and the authentication > > credentials properly the camera cannot be accessed. > > > > Now I wonder if Motion supports this access method at all. > > I've searched the website for further information but > > without success. > > You can file a new feature in Twiki though :) > In the meantime, perhaps the following (untested) solution may work on Linux: # nc -l -s 127.0.0.1 -p <local_port> -c 'openssl s_client -connect <axis_ip>:<axis_port> -quiet 2>/dev/null' This should open on <local_port> a tunnel to the camera using SSL located at <axis_ip>:<axis_port> upon connection. Your camera should then be accessible at http://localhost:<local_port>/ . This is not ideal, but it may help you if SSL is absolutely required. Good luck :) Regards, -- Aurélien Guillaume - 90% of statistics are made up. The remaining 20% are put together by people who are bad at math. |