
Recherche avancée
Autres articles (40)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...)
Sur d’autres sites (8239)
-
rtmppkt : Check for packet size mismatches
5 décembre 2016, par Michael Niedermayerrtmppkt : Check for packet size mismatches
When receiving fragmented packets, the first packet declares the size,
and the later ones normally are small follow-on packets that don’t repeat
the size and the other header fields. But technically, the later fragments
also can have a full header, declaring a different size than the previous
packet.If the follow-on packet declares a larger size than the initial one, we
could end up writing outside of the allocation.This fixes out of bounds writes.
Found-by : Paul Cher <paulcher@icloud.com>
Reviewed-by : Paul Cher <paulcher@icloud.com>CC : libav-stable@libav.org
Signed-off-by : Martin Storsjö <martin@martin.st> -
fate/fits : Use transcode for transcode-like test
22 avril 2022, par Andreas Rheinhardtfate/fits : Use transcode for transcode-like test
Each of the intermediately generated lena-*.fits files is only used
for exactly one test ; so it could be deleted right after the test.
Switching to a transcode test (which is also more natural) achieves
this. It also adds checksums of the intermediate files to the ref-file.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
-
avcodec/tiff : Enforce increasing offsets
9 août 2019, par Michael Niedermayeravcodec/tiff : Enforce increasing offsets
This may break some valid tiff files, it appears the specification does not require
the offsets to be increasing. They increase in the 2 test files i have though except
the last offset which is 0 (an end marker) and for which a special case is added to
avoid asking for a sample for that end marker.See : [FFmpeg-devel] [PATCH 2/2] avcodec/tiff : Detect infinite retry loop
for an alternative implementationFixes : Timeout (Infinite -> Finite)
Fixes : 15706/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_TIFF_fuzzer-5114674904825856This variant was requested by paul on IRC
Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
Reviewed-by : Paul B Mahol <onemda@gmail.com>
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>