
Recherche avancée
Médias (1)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
Autres articles (51)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...) -
Librairies et binaires spécifiques au traitement vidéo et sonore
31 janvier 2010, parLes logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
Binaires complémentaires et facultatifs flvtool2 : (...)
Sur d’autres sites (11067)
-
Update jQuery/Bootstrap/QUnit dependencies.
23 janvier 2018, par blueimpUpdate jQuery/Bootstrap/QUnit dependencies. Replace protocol-relative URLs (obsolete due to HSTS).
-
rtmpdump check status by command line
2 mai 2014, par DavidI tried doing rtmpdump -r "rtmp-raw=rtmpe ://watch.playfooty.tv/live playpath=nba1569 swfUrl=http://www.playfooty.tv/play/player/player.swf live=1 pageUrl=http://www.playfooty.tv/"
But the output it´s like offline alwaysRTMPDump v2.2e
(c) 2010 Andrej Stepanchuk, Howard Chu, The Flvstreamer Team; license: GPL
DEBUG: Parsing...
WARNING: Unknown protocol!
DEBUG: Parsed host : watch.playfooty.tv
DEBUG: Parsed app : live playpath=nba1569 swfUrl=http:/
DEBUG: Protocol : RTMP
DEBUG: Hostname : watch.playfooty.tv
DEBUG: Port : 1935
DEBUG: Playpath : www.playfooty.tv/play/player/player.swf live=1 pageUrl=http://www.playfooty.tv/
DEBUG: tcUrl : rtmp://watch.playfooty.tv:1935/live playpath=nba1569 swfUrl=http:/
DEBUG: app : live playpath=nba1569 swfUrl=http:/
DEBUG: live : no
DEBUG: timeout : 30 secI tried a lot of links of a list and seems offline with this command, but When I play it in a software it worked.
Does anyone have an idea how to test if this kind of links are alive or die ?
Thanks !
-
RTSP : shodan can do what I can't do with ffmpeg [closed]
6 août 2024, par Charlie BronsonGood morning, I hope someone can help me, I can't get to the bottom of this situationGood morning, I hope someone can help me, I can't get to the bottom of this situation


Premise 1 : Shodan does not brute force or log in with default credentials


Shodan manages to access and capture the RTSP stream and take a snapshot of an AXIS Q6045-E Mk II camera.


Premise 2 : I didn't perform the installation and I don't know (and I don't want to know) the access credentials for the camera, I'm just checking its security


At the request of the camera owner, I attempted to take a snapshot using ffmpeg :


ffmpeg -hide_banner -loglevel verbose -y -rtsp_transport tcp -i "rtsp://xxx.xxx.xxx.xxx:554" -an -vframes 1 -q:v 2 image.jpg



and obtain this output :


[tcp @ 0x61b69c5f4400] Starting connection attempt to xxx.xxx.xxx.xxx port 554
[tcp @ 0x61b69c5f4400] Successfully connected to xxx.xxx.xxx.xxx port 554
[in#0 @ 0x61b69c5f16c0] Error opening input: Invalid data found when processing input
Error opening input file rtsp://xxx.xxx.xxx.xxx:554.
Error opening input files: Invalid data found when processing input



On wireshark I can see how the camera requires authentication and ffmpeg responds with a FIN ACK once it receives OK after the DESCRIBE requestOn wireshark I can see how the camera requires authentication and ffmpeg responds with a FIN ACK once it receives OK after the DESCRIBE request :


My OPTION request


Real Time Streaming Protocol
 Request: OPTIONS rtsp://xxx.xxx.xxx.xxx:554 RTSP/1.0\r\n
 Method: OPTIONS
 URL: rtsp://xxx.xxx.xxx.xxx:554
 CSeq: 1\r\n
 User-Agent: Lavf61.1.100\r\n
 \r\n



Camera response :


Real Time Streaming Protocol
 Response: RTSP/1.0 200 OK\r\n
 Status: 200
 Server: H264DVR 1.0\r\n
 Cseq: 1\r\n
 Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, GET_PARAMETER, SET_PARAMETER, PLAY, PAUSE\r\n
 \r\n



My DESCRIBE request :


Real Time Streaming Protocol
 Request: DESCRIBE rtsp://xxx.xxx.xxx.xxx:554 RTSP/1.0\r\n
 Method: DESCRIBE
 URL: rtsp://xxx.xxx.xxx.xxx:554
 Accept: application/sdp\r\n
 CSeq: 2\r\n
 User-Agent: Lavf61.1.100\r\n
 \r\n



Camera response requesting digest authentication :


Real Time Streaming Protocol
 Response: RTSP/1.0 200 OK\r\n
 Status: 200
 Server: H264DVR 1.0\r\n
 Cseq: 2\r\n
 WWW-Authenticate: Digest realm="135axxxxxxxxxxx", nonce="96n0d4Lv626w8vfu8L090B6\r\n
 \r\n



My response at this point is a TCP FIN ACK.


Premise 3 : I am not an RTSP or ffmpeg expert


at this point I told the owner that as he could see, credentials were required for access, and he rightly says that this is not the case as shodan still manages to access.


If I assume premise 1 to be true, then I'm doing something wrong in the ffmpeg request, so how can I modify the ffmpeg request to obtain a snapshot compatible with the shodan one and avoid detecting false negatives ?