github-actions[bot] opened a new pull request, #65364:
URL: https://github.com/apache/airflow/pull/65364

   * Validate SMTP server certificate on STARTTLS upgrade
   
   smtplib.SMTP.starttls() does not validate the server certificate
   unless an SSL context is passed. airflow.utils.email.send_mime_email
   and the SMTP provider's SmtpHook (both sync get_conn and async
   aget_conn) were calling starttls() without a context, so the STARTTLS
   upgrade accepted any certificate and the subsequent login() call
   could send credentials over a connection terminated by a MITM.
   
   Pass the existing SSL-context machinery (the email.ssl_context
   config in core and the ssl_context connection extra in the provider)
   to starttls() at all three call sites. The default becomes
   ssl.create_default_context(), which validates against the system's
   trusted CAs. Users who intentionally use self-signed certificates
   can still opt out by setting the value to "none".
   
   Generated-by: Claude Opus 4.6 (1M context) following the guidelines at
   
https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions
   
   * Add newsfragment and SMTP provider changelog for STARTTLS cert default
   
   Document the default behaviour change introduced by passing an SSL
   context to the STARTTLS upgrade: system-default CA validation now
   applies to both airflow.utils.email.send_email (via
   email.ssl_context) and the SMTP provider's SmtpHook (via the
   ssl_context connection extra). Users who intentionally run against
   self-signed SMTP servers can preserve the old behaviour by setting
   the value to "none".
   (cherry picked from commit 06981d4ad8249bfd371bd718d37c7f04eec7c151)
   
   Co-authored-by: Jarek Potiuk <[email protected]>
   Generated-by: Claude Opus 4.6 (1M context) <[email protected]>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to