3 ms·

foobar is only for windows..

by brulard 11y ago

yoodenvranx 11y ago
It runs perfectly fine in wine, I am doing this for years.
- throwanem 11y ago
  I've done the same, on OS X yet, and had no trouble. Unfortunately, fb2k ended up being unsuitable for my purposes for other reasons - namely, that it can't handle self-signed TLS certificates, and probably never will be able to because the developer doesn't care about that use case. I still use it at home, but for remote streaming I've found Subsonic to be an amazingly effective solution, not least thanks to the excellent iSub app.
  - cptskippy 11y ago
    Supporting self-signed certs is typically done by ignoring cert chain and trust issues which is a major component of TLS. A better option is for you to explicitly trust the authority that signed the cert.
    - throwanem 11y ago
      Well, yes, I'm not completely ignorant of how TLS works, so that was of course my first thought on discovering fb2k lacked any interface by which I could tell it to trust my server cert. That's why, in the process of investigating the issue, I added the root CA cert I'd created, and used to sign the server cert, to the Windows certificate store. That was enough to stop applications using the Windows TLS stack, such as Internet Explorer, from complaining any longer about being unable to verify the certificate. It didn't change anything about fb2k's behavior, though, which led me to surmise that fb2k was doing something wonky in its TLS implementation. On the other hand, there's a forum thread from late last year [1] in which the fb2k developer appears to have addressed the issue at least in part, by making it possible to whitelist hosts and thus bypass certificate validity checking. That's...hardly ideal, but it would probably have solved my problem, if it existed four years ago when I last tried to get this working. The same thread includes more information on the same kind of problem I was having; from it I can surmise that if I'd created an empty CRL and had my root CA cert point to it, I probably would've been able to get it working. Would've been nice to know that four years ago, too. But it looks like I'd have needed to hook the process with a debugger and monitor system calls to find out about it, and I wanted to listen to music more than I wanted to use unfamiliar tools to debug unfamiliar API calls made by an opaque binary blob. In any case, if I'd gotten fb2k working four years ago, I probably wouldn't have been motivated to keep hunting for a solution until I found Subsonic, which serves my remote-streaming purposes better than fb2k ever will. So however frustrating it was at the time, it's been all to the good in the long run. [1] https://hydrogenaud.io/index.php/topic,110065.0.html https://hydrogenaud.io/index.php/topic,110065.0.html
touristtam 11y ago
try deadbeef ?

foobar is only for windows..

by brulard 11y ago

foobar is only for windows..

yoodenvranx 11y ago

It runs perfectly fine in wine, I am doing this for years.

throwanem 11y ago
I've done the same, on OS X yet, and had no trouble. Unfortunately, fb2k ended up being unsuitable for my purposes for other reasons - namely, that it can't handle self-signed TLS certificates, and probably never will be able to because the developer doesn't care about that use case. I still use it at home, but for remote streaming I've found Subsonic to be an amazingly effective solution, not least thanks to the excellent iSub app.
- cptskippy 11y ago
  Supporting self-signed certs is typically done by ignoring cert chain and trust issues which is a major component of TLS. A better option is for you to explicitly trust the authority that signed the cert.
  - throwanem 11y ago
    Well, yes, I'm not completely ignorant of how TLS works, so that was of course my first thought on discovering fb2k lacked any interface by which I could tell it to trust my server cert. That's why, in the process of investigating the issue, I added the root CA cert I'd created, and used to sign the server cert, to the Windows certificate store. That was enough to stop applications using the Windows TLS stack, such as Internet Explorer, from complaining any longer about being unable to verify the certificate. It didn't change anything about fb2k's behavior, though, which led me to surmise that fb2k was doing something wonky in its TLS implementation. On the other hand, there's a forum thread from late last year [1] in which the fb2k developer appears to have addressed the issue at least in part, by making it possible to whitelist hosts and thus bypass certificate validity checking. That's...hardly ideal, but it would probably have solved my problem, if it existed four years ago when I last tried to get this working. The same thread includes more information on the same kind of problem I was having; from it I can surmise that if I'd created an empty CRL and had my root CA cert point to it, I probably would've been able to get it working. Would've been nice to know that four years ago, too. But it looks like I'd have needed to hook the process with a debugger and monitor system calls to find out about it, and I wanted to listen to music more than I wanted to use unfamiliar tools to debug unfamiliar API calls made by an opaque binary blob. In any case, if I'd gotten fb2k working four years ago, I probably wouldn't have been motivated to keep hunting for a solution until I found Subsonic, which serves my remote-streaming purposes better than fb2k ever will. So however frustrating it was at the time, it's been all to the good in the long run. [1] https://hydrogenaud.io/index.php/topic,110065.0.html https://hydrogenaud.io/index.php/topic,110065.0.html

touristtam 11y ago

try deadbeef ?