Re: prominent message on website about "use only on trusted input"?

On 2017-07-29 11:09, Thomas Orgis wrote:
> 
> It seems to run just fine, built using GCC 6.3.0 here. And apart from
> that … there is not _that_ much GUI involved, as it seems. So porting
> to newer Gtk or anything else probably, would be an afternoon walk for
> a seasoned GUI programmer, wouldn't it?

For someone knowledgeable about GTK, it would probably not be long to 
adapt.


> Also, the analyser is hooked into the encoder, right? I am starting to
> look into the code … could it be that it's using the generic way to get
> at PCM input, decoding MP3 along the way, and then hooks mpglib
> directly into what lame itself produces? So having the initial decoding
> to PCM happen in libmpg123 and only the analyzing stage with mpglib and
> its extra hooks would also avoid any danger from malicious input files.
> Lame is not producing malicious MP3 data, is it?

Analyser is both hooked into encoder and decoder. MP3X is able to show 
MDCT components on an already encoded file, along with some frame 
information (bit reservoir, block type,...).
You can see that in the screenshots there:
http://lame.sourceforge.net/screenshots.php

The FhG and MPECKER example are running the analyser over an already 
encoded file, without any re-encoding.


--
Gabriel Bouvigne

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev