On 04:32 pm, piper.mas...@gmail.com wrote:
On Fri, Aug 15, 2014 at 2:15 AM, Glyph wrote:
When I use the openssl command you gave me, I get this:
> openssl s_client -connect localhost:8000
CONNECTED(0003)
^C
(I had to Ctrl-C it, because it just stuck there)
You might find it ins
>Maybe I generated my certs wrong or something? I just did
Did you set the "Common Name" (CN) correctly?
FWIW, you might have look at this recipe
https://github.com/crossbario/crossbar/wiki/Secure%20WebSocket%20and%20HTTPS#using-self-signed-certificates
Ignore the other stuff / the site in gen
On Fri, Aug 15, 2014 at 2:15 AM, Glyph wrote:
> On Aug 14, 2014, at 3:54 PM, Piper Masden wrote:
>
> The core of the code looks like this:
>
> resource = WSGIResource(reactor, reactor.getThreadPool(),
> WSGIHandler())
> endpoint = 'tcp:port=8000'
> server = strports.service(endpoin
>generated a .key file and a .crt file with openssl, and then cat'd them
>together to make a pem, and then changed the endpoint to be...
> endpoint = 'ssl:port=8000:privateKey=/path/to/key.pem'
you could try to not concat key and cert, but leave them separate:
endpoint = 'ssl:port=8000:private
On Aug 14, 2014, at 3:54 PM, Piper Masden wrote:
> Hi Twistedeers!
>
> I have a twisted plugin that I created to replace the Django dev server for
> our devs.
Cool!
> It sets up a separate twisted service for serving media, so we don't need any
> urls.py tomfoolery in dev. It also sets up
Hi Twistedeers!
I have a twisted plugin that I created to replace the Django dev server
for our devs. It sets up a separate twisted service for serving media, so
we don't need any urls.py tomfoolery in dev. It also sets up an
experimental REST api server which we hope to make javascript requests
