secure

Describe the feature you'd like supported

We should change the CID after enough idle time so that any possible NAT rebinding would be harder to be tracked by an outside observer. The simplest way to implement this would be in the flush send code path. When first starting a flush, check how much time has elapsed since the last send. If it's greater than X (20? 30?) seconds force a CID update

binserve seems really great but I really wish it were a bit easier to use:

1. It would be really great to be able to just do binserver --auto-self-signed-tls --dir ./www and have it generate a self-signed key/cert and serve from the directory.
2. I have no idea how to generate certs/keys for this. I have my openssl one-liner and if I try to use that I get:

[cole@slynux:~/code/webrtcs

As hinted in aidantwoods/SecureHeaders#67 (comment), the public API could do with some better coverage.

Blocked by #2