New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SSL support #16

Open

tracend opened this issue Jun 29, 2012 · 2 comments

Member

tracend commented Jun 29, 2012

Consider requiring the transactions to be executed under a secure socket, or at least give the config option to be activated on demand.

Member Author

tracend commented Jun 29, 2012

Here is some helpful info:
http://stackoverflow.com/a/10744484

Member Author

tracend commented Jan 9, 2013

This requirement should be extended to both, sockets and the REST api.

The connect method may lookup for an option like:

ssl : true

or

encrypted: true

tracend closed this as completed

tracend reopened this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment