@Diegote - google translate gives me this: `The signed file in clear is not valid, "NOSPLIT" obtained (does the network require authentication?)`
which tells me you probably need to update the keys you have from spotify, because what you have isn't what they're signing with. Try just re-running the first command from the linux installation notes
also please start a new thread for a new issue, instead of adding on to an existing one next time.
A not so simple solution would be to dynamically open libssl1.0.2 or libssl1.0.0 depending on what is available. This could happen.
Another solution would be to drop the feature that libssl is used for (communicating with embedded playbuttons on the web) and then stop depending on the library. Will probably also not happen.
Both of these happened, sort of. We stopped using the TLS parts of libssl.so for communicating with the embedded playbuttons on the web a few versions ago. However, we were still using libcrypto.so from the same debian package from other things. However, suddenly dynamically open different version of the library became a simple solution which was implemented.
Spotify 1.0.69 in the testing repository now (soon stable) can dynamically load different version of libcrypto.so (from the libssl* packages).