Sonarr needs native SSL support in Mono (Linux)

Devs, I think it’s about time to seriously fix SSL for Sonarr in Linux (using Mono).

All other Sonarr competitors, and other related software as Couchpotato, Emby… all of them manage to implement it. Even Emby that also uses Mono for Linux version.

Me and lots of users don’t want to create reverse proxies ONLY for Sonarr, when the feature could be correctly implemented.

If you still think that SSL is impossible for Mono (be it any version), we can have a chat with Luke, the main dev of Emby, and question how he did it.

Thanks!
Anderson

Complementing…
The tutorial seen in http://nzbdrone.readthedocs.io/SSL/ isn’t an acceptable “fix” for people (like me) that depends on Docker images of Sonarr, because we can’t install-and-keep-installed packages as httpcfg (that doesn’t come natively). We use docker to keep untouched the main system (OMV, in my case).

So… please look how other have done it, and please make Sonarr do it, too.

It comes down to the webserver that we’re using for Sonarr which at the time was the only one that was really ready for use when v2 was written. We’ll be re-evaluating the options that are available as we work on v3.

1 Like

I appreciate a lot! Thanks!

We’ll keep talking in this topic about this, agree? I intended to ask here like twice a month to follow the development of the solution.

See ya

PS: some more info about EMBY (soft that already uses SSL and Mono)

Also… maybe reading http://www.mono-project.com/docs/faq/security/ can also help… don’t know for sure.

Not really anything to follow up on, we’ll get it done when it gets done, but we can’t (and won’t) commit to when that will be or provide status updates to ongoing work, the entity of the work being done on Sonarr is in our free time.

Okay… didn’t know that

Also about that… Have you already gave a thought about opening the code as make it open source in GitHub? Because that usually speeds development, as users tend to collaborate with coding suggestions, and you’d had only to approve it.

It’s already on GitHub:

1 Like

Just checking in to keep the topic alive (avoid auto-close).

About GitHub, I don’t understand programming well enough for this SSL issue. Just hoped that someone did and collaborate.

If you ever confirm that v3 will allow SSL in Mono, please let us know.

anderbytes,

You can implement this in about 5 minutes and have TLS for Sonarr: https://www.stunnel.org/index.html

Seriously, you really think bumping a thread like that is gonna make it happen?
You’ve pretty much annoyed every single developer in the Sonarr team, so they’re not gonna do it unless they really want to.
And any potential contributor probably does the smart thing and use a nginx/apache reverse proxy to provide better security, which is the best approach anyway.
As Markus said, in v3 it might be possible to implement an easier way to configure ssl with mono, but I wouldn’t keep your hopes up. Trust me, you’ll have fewer headaches if you just configure a nice ssl reverse proxy with nginx/apache.

Not really forcing any “make it happen”.
I already do use the reverse proxy. The topic is actually about making Sonarr better and natively more secure.

This thread was only meant to follow the topic of SSL implementation… if it ever happens… and the thing you confused as “bump” is the only thing I can do so the topic doesn’t vanish every 2 months… and leaving me with nothing to follow. Recreating the same topic each 2 months would make any difference? Surely no.

I’m not posting any more topics here… so you won’t be bothered anymore.
farewell

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.