beingsane / streeme

Automatically exported from code.google.com/p/streeme
MIT License
0 stars 0 forks source link

SSL Support #32

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Install Streeme and test it
2. Install SSL on Apache and generate a Certificate for Streeme
3. Streaming doesn't work anymore :(

What is the expected output? What do you see instead?
I wanted to add a SSL support on Streeme to encrypt transmission between client 
and server.
The site himself work good, but the streaming isn't working.

What version of the product are you using? On what operating system?
Last version on a Debian Squeeze.

Original issue reported on code.google.com by 4rt...@gmail.com on 28 Jun 2011 at 6:36

GoogleCodeExporter commented 8 years ago
I am also having this same issue with Debian Squeeze. 

It would seem to me that there needs to be a change made to a config file 
somewhere, but being a n00b I'm not sure which one.

Original comment by jdlee2...@gmail.com on 21 Sep 2011 at 8:11

GoogleCodeExporter commented 8 years ago
This might be an easy fix. just set the music port in app.yml to the same port 
as your SSL layer in the app/client/config/app.yml file. 

Original comment by chaffn...@gmail.com on 23 Sep 2011 at 4:42

GoogleCodeExporter commented 8 years ago
I did some testing this morning and found that changing the "streaming" port to 
443 in /etc/apache2/sites-enabled and 
/var/www/streeme/apps/client/config/app.yml did work... sort of. Opera, Chrome 
and Internet Explorer all seemed to work okay, however, Firefox did not. 
Furthermore, all browsers (stock, Opera Mobile, Firefox, Firefox Beta, and 
Dolphin) on my Android did not work. I believe the issue is that since my SSL 
cert is unsigned it needs to be approved by the browser/user, but since this 
"streaming" port is on the back end I'm not getting the prompt to accept it. 
Things would be a lot easier (and maybe more secure) I think if everything was 
inside port 443. Although I realize this would probably be a big design 
challenge. I'm sure you designed it with 2 different ports for a good reason.

Original comment by jdlee2...@gmail.com on 23 Sep 2011 at 1:13

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Firefox has it's own certificate store. Just add your self signed cert to 
Firefox by clicking on .crt file with firefox's file browser, choose all of the 
three checkboxes it presents you with and you'll be set. Self signed 
certificates will not work on mobile devices unless you know know how to add it 
to the trusted root certificate authority store on your device. Again Firefox 
mobile maintains its own cert store making mobile devices the most irritating 
things ever for SSL. That said you can try some of the x509 importers, but I 
can't actually help you with support of these, because I don't have a real 
android device 
http://stackoverflow.com/questions/1217141/self-signed-ssl-acceptance-android

-Rich

Original comment by chaffn...@gmail.com on 23 Sep 2011 at 1:54

GoogleCodeExporter commented 8 years ago
Thanks for your suggestions. I've done some extensive testing many times over, 
but I cannot get SSL working on my Android in any web browser. This is even 
when adding my certs into Android itself (via Settings > Location and Security 
> Credential Storage) and using Firefox's permanent exceptions. I also tried 
only using port 443 for the web interface and streaming, but alas that did not 
work on the Android. However, it did work fine on the PC/Mac. After all of this 
testing I actually came across the link below, which let me know that 
everything had been in vain. Under "Network Protocols", it states "Note: HTTPS 
is not supported at this time." So it looks like I'll have to resort to a 
OpenVPN SSL VPN to get this working on the Android.  Hopefully Android will fix 
the HTTPS streaming in a later release. Thanks for your help and for creating a 
really sweet project.
http://developer.android.com/guide/appendix/media-formats.html

Original comment by jdlee2...@gmail.com on 25 Sep 2011 at 7:05

GoogleCodeExporter commented 8 years ago
I am currently having the same issue. I am trying to get this to work with a 
desktop browser, and have tested with firefox and safari. Without ssl the site 
works perfectly. When i enable ssl, the interface of the site continues to 
work; however, it will no longer stream music. 

I created my certificates, placed them in the proper directories, and added the 
lines "SSLEngine On", "SSLCertificateFile /etc/ssl/certs/server.crt", 
"SSLCertificateKeyFile /etc/ssl/private/server.key" to both of two different 
port sections of my virtual host file. The streaming port in app.yml and and my 
virtual host config file are the same.

The browser will show the site is encrypted, and login/navigation works. 
However, nothing will stream. I've tried everything i can think of without 
success. If there is someone who has gotten this to work, would you please post 
your config files as a template, for those of use having issues, to work from?

Original comment by jarring1...@gmail.com on 26 Sep 2011 at 2:00

GoogleCodeExporter commented 8 years ago
Setting the "streaming" port to 443 fixed this for me. Furthermore, it seemed 
that was the only port I needed to use.

Original comment by jdlee2...@gmail.com on 26 Sep 2011 at 2:30

GoogleCodeExporter commented 8 years ago
you also need to add the public key to your certificate store on windows and 
mac. type run>certmgr.msc then choose trusted certificate authorties, right 
click and choose all tasks > import and import your .crt file. Restart all your 
browsers once installed. On osx, just double click the crt file and allow the 
cert to work for https in the keychain. On Firefox, you'll have to open the crt 
file with firefox and click the three checkboxes to import it. 

jdlee - if you wouldn't mind sharing your ssl config template and steps you 
took to get it working, I'll gladly add them to the wiki for others to use.

Original comment by chaffn...@gmail.com on 26 Sep 2011 at 4:20

GoogleCodeExporter commented 8 years ago
Issue 42 has been merged into this issue.

Original comment by chaffn...@gmail.com on 2 Jan 2012 at 11:13