this post was submitted on 25 Sep 2024
149 points (92.1% liked)
Open Source
31692 readers
307 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm curious, why does this require OpenSSL in order to compile? I'm not aware of any audio formats that use encryption, but I could be wrong.
My first thought was for connecting to https streams, but I don't remember Winamp having this capability. "Back in the day," I used Winamp for playing local audio and RealPlayer for what little streaming was available.
i remember listening to icecast radio on winamp back in the day
Couldn’t you look at the code and see what ssl calls it’s making?
Looks like curl and opus want it https://github.com/search?q=repo%3AWinampDesktop%2Fwinamp+openssl+language%3AC&type=code
Three streaming (like pointed in the other comment) was my initial reaction too, but indeed at the time https for streaming would be very rare.
Another possibility is to realize that openssl isn't just for communication, but also has implementation of cryptographic algorithms.
Perhaps openssl was used for validation of licensing key? For example they could sign the license with their private key and WinAmp could verify it's authenticity with its public key.
Maybe to connect to their update servers and validate updated binaries or something like that? Not sure if it supported calling home to get updates.
I don't know about https specifically but winamp could handle all kinds of streams.