sslconn | Experimental golang wrapper around OpenSSL | TLS library
kandi X-RAY | sslconn Summary
kandi X-RAY | sslconn Summary
This is an experimental golang (CGO) wrapper around OpenSSL. The crypto/tls package does not support (1) SSLv2 compatible handshakes, so this is an attempt to use OpenSSL in golang. The reason SSLv2 handshake is desired is for compatibility (2) with a variety of clients. The suggested approach is to provide SSL termination upstream, however some protocols upgrade plain text connections using STARTTLS (3) which would require a smart and protocol aware SSL terminator. This wrapper only exposes only a tiny subset of the OpenSSL API, just enough to enable the use-case described above. In order to multiplex a OpenSSL connection the underlying IO needs to be non blocking. To support that, a NonBlockingReader and NonBlockingWriter were implemented to provide the necessary semantics. Most of the OpenSSL integration is done in C to avoid locking the OS thread required for error checking (thread locals.).
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- newSSLConnConfig creates a new SSLConnConfig
- NewConn creates a new connection .
- NewPrivateKey creates a new PrivateKey .
- NewCert creates a new TLS connection .
- query io . Reader
- NewNonBlockingWriter returns a new non - blocking writer
- gocn .
- NewNonBlockingReader returns a new NonBlockingReader .
- writeBytesTo writes bytes to io . Writer .
- Cleanup SSLConnConfig object
sslconn Key Features
sslconn Examples and Code Snippets
Community Discussions
Trending Discussions on sslconn
QUESTION
I am trying to modify a socket server I wrote with the python socket library to use encryption using python's SSL library.
I am no able to successfully open a connection to the server, wrap it with an SSL context and send data to the server, but data sent back to the client is not what it should be.
My suspicion is that the server responses are not being decrypted on the client side, but I don't know why. I'm pretty new to SSL/TLS, and networking in general so... what am I missing?
The client is also written in python (for now, to facilitate testing)
Code:
Relevant Server stuff:
...ANSWER
Answered 2018-Mar-14 at 00:29It is not legal to shutdown a socket that is being used for SSL. It is a protocol violation. You must close via the SSL/TLS API you are using.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install sslconn
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page