You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should implement a few different decoding algorithms for making rogue frame data (such as song purchase information commonly hidden in PRIV frames) more easily readable no matter what type of algorithm was initially used to obscure the data.
I have seen instances where rogue frame data has been stored in a variety of formats such as XML or a serialized binary string, so brute force decoding (attempting several methods to decode the data and outputting the results on the screen) might reveal the data in a human-readable context. Users should have a simple way to request/view a brute force decoding of any frame's data.
The text was updated successfully, but these errors were encountered:
We should implement a few different decoding algorithms for making rogue frame data (such as song purchase information commonly hidden in PRIV frames) more easily readable no matter what type of algorithm was initially used to obscure the data.
I have seen instances where rogue frame data has been stored in a variety of formats such as XML or a serialized binary string, so brute force decoding (attempting several methods to decode the data and outputting the results on the screen) might reveal the data in a human-readable context. Users should have a simple way to request/view a brute force decoding of any frame's data.
The text was updated successfully, but these errors were encountered: