-
Notifications
You must be signed in to change notification settings - Fork 95
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
Fix SMTPS / implicit TLS #292
Open
strongholdmedia
wants to merge
9
commits into
aio-libs:master
Choose a base branch
from
strongholdmedia:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
122f0ee
Moved smtps context determination up so that its state can be passed …
strongholdmedia c2cacac
Changes to account for SMTPS / implicit TLS usage
strongholdmedia 4770b5c
Merge branch 'aio-libs:master' into master
strongholdmedia fc0bae0
Fixed AUTH with SMTPS
strongholdmedia 4aa0cea
Added test for #281
strongholdmedia 7f31ffb
Removed stale import statement
strongholdmedia d36f75e
Fixed assertion of content for changed error message in SMTP test
strongholdmedia 3013c0c
Enable SMTPS explicitly on the controller
strongholdmedia 5625213
Removed nonsense and added another assertion
strongholdmedia File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
After doing some tracing, a thought occurred to me:
Implicit TLS (SMTPS) is triggered if
tls_context
is set, right?Can we just set
is_using_smtps
attribute from that? Soself._is_using_smtps = (tls_context is not None)
?I might've overlooked something, so I welcome a discussion here.
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.
Well, yes and no.
For once,
tls_context
is forSTARTTLS
;SMTPS
usesssl_context
. (This was already such before, I did not change it.)Otherwise we could set that, yep, but this option communicates clear intent.
As you've noted in #281, there is no possible means for detecting whether or not we are using implicit TLS (
SMTPS
) within theSMTP
class.This goes to the extent that
ssl_context
is actually not used by theSMTP
class at all.It is still kept by me, as if later authentication methods will require e.g. client re-validation or something, it could happen.
But unlike
is_using_smtps
,ssl_context
may or may not be an explicit intent.ssl_context
beingNone
could equally mean "should not use SMTPS", as well as "hey, we/they/... failed to handle a key / cert error / expiry / ... somewhere".But as per the above, there is no means to detect whichever from inside the
SMTP
class; as such, if the described scenario happens, the client/user would just note that "hey, we don't haveAUTH
", or even "gotSMTP
error, pls help, it worked yesterday".Currently, if
is_using_smtps
is set with nossl_context
, it should present an error.I understand your point and will change it if that'd be the agreement, but I feel that would be a technically less correct approach.