-
Notifications
You must be signed in to change notification settings - Fork 512
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.
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
SSL/TLS implementation #37
Conversation
range iteration is random and SQL server expects the prelogin items to be in ascending order
Only the first TDS packet of the Login message MUST be encrypted using TLS/SSL and encapsulated in a TLS/SSL message. All other TDS packets sent or received MUST be in plaintext.
} | ||
if encrypt == encryptOff { | ||
outbuf.afterFirst = func() { | ||
outbuf.transport = toconn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you sure this will work? I mean will server drop encryption after login, I didn't see such feature in docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copying from table in 2.2.6.4: Value returned from server is ENCRYPT_OFF: Encrypt login packet only
copying from 3.2.5.2:
If login-only encryption was negotiated as described in section 2.2 in the PRELOGIN message description, then the first TDS packet of the Login message MUST be encrypted using TLS/SSL and encapsulated in a TLS/SSL message. All other TDS packets sent or received MUST be in plaintext.
Ok, I approve this pull request |
@denisenkom please review
closes #27