FAQ
#22646: MySQL dbshell command should respect the encryption flag
-------------------------------+----------------------
      Reporter: zsoldosp | Owner: zsoldosp
          Type: Uncategorized | Status: new
     Component: Uncategorized | Version: master
      Severity: Normal | Keywords:
  Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+----------------------
  the {{{'OPTIONS': {'ssl': {'ca': '....'}}}}} database setting should
  translate to {{{--ssl-ca=...}}} command line option to the mysql
  executable

--
Ticket URL: <https://code.djangoproject.com/ticket/22646>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups "Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscribe@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/051.7e572aacc38ff69a7526c98dbaa8b632%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

  • Django at May 17, 2014 at 10:04 am
    #22646: MySQL dbshell command should respect the encryption flag
    -------------------------------+--------------------------------------
          Reporter: zsoldosp | Owner: zsoldosp
              Type: Uncategorized | Status: new
         Component: Uncategorized | Version: master
          Severity: Normal | Resolution:
          Keywords: | Triage Stage: Unreviewed
         Has patch: 1 | Needs documentation: 0
       Needs tests: 0 | Patch needs improvement: 0
    Easy pickings: 0 | UI/UX: 0
    -------------------------------+--------------------------------------
    Changes (by zsoldosp):

      * needs_better_patch: => 0
      * has_patch: 0 => 1
      * needs_tests: => 0
      * needs_docs: => 0


    Comment:

      See pull request https://github.com/django/django/pull/2674

    --
    Ticket URL: <https://code.djangoproject.com/ticket/22646#comment:1>
    Django <https://code.djangoproject.com/>
    The Web framework for perfectionists with deadlines.

    --
    You received this message because you are subscribed to the Google Groups "Django updates" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscribe@googlegroups.com.
    To post to this group, send email to django-updates@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.cdc6b5ebc4b477e5ec6b773ec260bd30%40djangoproject.com.
    For more options, visit https://groups.google.com/d/optout.
  • Django at May 17, 2014 at 10:10 am
    #22646: MySQL dbshell command should respect the encryption flag
    -------------------------------+--------------------------------------
          Reporter: zsoldosp | Owner: zsoldosp
              Type: Uncategorized | Status: new
         Component: Uncategorized | Version: master
          Severity: Normal | Resolution:
          Keywords: | Triage Stage: Unreviewed
         Has patch: 1 | Needs documentation: 0
       Needs tests: 0 | Patch needs improvement: 0
    Easy pickings: 0 | UI/UX: 0
    -------------------------------+--------------------------------------

    Comment (by benjaoming):

      No regressions found: Verified that all dbshell tests are running for
      MySQL and that newly created MySQL project still connects via non-SSL.

    --
    Ticket URL: <https://code.djangoproject.com/ticket/22646#comment:2>
    Django <https://code.djangoproject.com/>
    The Web framework for perfectionists with deadlines.

    --
    You received this message because you are subscribed to the Google Groups "Django updates" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscribe@googlegroups.com.
    To post to this group, send email to django-updates@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.92f45145a2a76d80d9b1d00b1b2ba6ea%40djangoproject.com.
    For more options, visit https://groups.google.com/d/optout.
  • Django at May 17, 2014 at 1:07 pm
    #22646: MySQL dbshell command should respect the encryption flag
    -------------------------------------+-------------------------------------
          Reporter: zsoldosp | Owner: zsoldosp
              Type: | Status: new
       Cleanup/optimization | Version: master
         Component: Database layer | Resolution:
       (models, ORM) | Triage Stage: Accepted
          Severity: Normal | Needs documentation: 0
          Keywords: | Patch needs improvement: 0
         Has patch: 1 | UI/UX: 0
       Needs tests: 0 |
    Easy pickings: 0 |
    -------------------------------------+-------------------------------------
    Changes (by syphar):

      * cc: denis.cornehl@… (added)
      * type: Uncategorized => Cleanup/optimization
      * component: Uncategorized => Database layer (models, ORM)
      * stage: Unreviewed => Accepted


    --
    Ticket URL: <https://code.djangoproject.com/ticket/22646#comment:3>
    Django <https://code.djangoproject.com/>
    The Web framework for perfectionists with deadlines.

    --
    You received this message because you are subscribed to the Google Groups "Django updates" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscribe@googlegroups.com.
    To post to this group, send email to django-updates@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.1a06bff77f39b5c6ceb8ee468b55db1f%40djangoproject.com.
    For more options, visit https://groups.google.com/d/optout.
  • Django at May 17, 2014 at 1:16 pm
    #22646: MySQL dbshell command should respect the encryption flag
    -------------------------------------+-------------------------------------
          Reporter: zsoldosp | Owner: zsoldosp
              Type: | Status: new
       Cleanup/optimization | Version: master
         Component: Database layer | Resolution:
       (models, ORM) | Triage Stage: Ready for
          Severity: Normal | checkin
          Keywords: | Needs documentation: 0
         Has patch: 1 | Patch needs improvement: 0
       Needs tests: 0 | UI/UX: 0
    Easy pickings: 0 |
    -------------------------------------+-------------------------------------
    Changes (by syphar):

      * stage: Accepted => Ready for checkin


    Comment:

      verified, too (before I set the "ready" flag.

      Connect to local, remote, with or without ca is fine (and the CA is used).

    --
    Ticket URL: <https://code.djangoproject.com/ticket/22646#comment:4>
    Django <https://code.djangoproject.com/>
    The Web framework for perfectionists with deadlines.

    --
    You received this message because you are subscribed to the Google Groups "Django updates" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscribe@googlegroups.com.
    To post to this group, send email to django-updates@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.71019ec6a0459c6557a32bf6a3bf1a50%40djangoproject.com.
    For more options, visit https://groups.google.com/d/optout.
  • Django at May 17, 2014 at 1:36 pm
    #22646: MySQL dbshell command should respect the encryption flag
    -------------------------------------+-------------------------------------
          Reporter: zsoldosp | Owner: zsoldosp
              Type: | Status: new
       Cleanup/optimization | Version: master
         Component: Database layer | Resolution:
       (models, ORM) | Triage Stage: Accepted
          Severity: Normal | Needs documentation: 1
          Keywords: | Patch needs improvement: 1
         Has patch: 1 | UI/UX: 0
       Needs tests: 0 |
    Easy pickings: 0 |
    -------------------------------------+-------------------------------------
    Changes (by erikr):

      * needs_better_patch: 0 => 1
      * stage: Ready for checkin => Accepted
      * needs_docs: 0 => 1


    Comment:

      I can see the use for `dbshell` here, but `ca` is not a [[http://mysql-
      python.sourceforge.net/MySQLdb.html|supported parameter in MySQLdb]]. As
      far as I can see, all currently supported `OPTION`'s are, i.e. they are
      both MySQLdb options and can be translated to `mysql` command line
      options. However, this change would only apply to `dbshell`, which may be
      entirely unexpected by users.

      The [[https://docs.djangoproject.com/en/dev/ref/databases/#connecting-to-
      the-database|current documentation]] simply refers to MySQLdb to figure
      out which options exist, so the `ca` option also has no documentation in
      this patch, as MySQLdb doesn't mention it, as it's not a MySQLdb option.

    --
    Ticket URL: <https://code.djangoproject.com/ticket/22646#comment:5>
    Django <https://code.djangoproject.com/>
    The Web framework for perfectionists with deadlines.

    --
    You received this message because you are subscribed to the Google Groups "Django updates" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscribe@googlegroups.com.
    To post to this group, send email to django-updates@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.b50fcf10e4b5d584ba760f834bcaaef2%40djangoproject.com.
    For more options, visit https://groups.google.com/d/optout.
  • Django at May 18, 2014 at 9:33 am
    #22646: MySQL dbshell command should respect the encryption flag
    -------------------------------------+-------------------------------------
          Reporter: zsoldosp | Owner: zsoldosp
              Type: | Status: new
       Cleanup/optimization | Version: master
         Component: Database layer | Resolution:
       (models, ORM) | Triage Stage: Accepted
          Severity: Normal | Needs documentation: 1
          Keywords: | Patch needs improvement: 1
         Has patch: 1 | UI/UX: 0
       Needs tests: 0 |
    Easy pickings: 0 |
    -------------------------------------+-------------------------------------

    Comment (by syphar):

      In the doc you provided, there is an parameter {{{ssl}}} which translates
      the given dict to [http://dev.mysql.com/doc/refman/5.0/en/mysql-ssl-
      set.html], which accepts a {{{ca}}} as a parameter. Since our backend just
      adds all provided options to the {{{connect}}} call, I think this ''is''
      supported by the mysql backend at the moment.

      Or did I misread anything? Looks like this ''is'' supported at the moment.

    --
    Ticket URL: <https://code.djangoproject.com/ticket/22646#comment:6>
    Django <https://code.djangoproject.com/>
    The Web framework for perfectionists with deadlines.

    --
    You received this message because you are subscribed to the Google Groups "Django updates" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscribe@googlegroups.com.
    To post to this group, send email to django-updates@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.3b000bd536021f0ae34c67de5de035d7%40djangoproject.com.
    For more options, visit https://groups.google.com/d/optout.
  • Django at May 18, 2014 at 3:27 pm
    #22646: MySQL dbshell command should respect the encryption flag
    -------------------------------------+-------------------------------------
          Reporter: zsoldosp | Owner: zsoldosp
              Type: | Status: new
       Cleanup/optimization | Version: master
         Component: Database layer | Resolution:
       (models, ORM) | Triage Stage: Accepted
          Severity: Normal | Needs documentation: 1
          Keywords: | Patch needs improvement: 1
         Has patch: 1 | UI/UX: 0
       Needs tests: 0 |
    Easy pickings: 0 |
    -------------------------------------+-------------------------------------

    Comment (by erikr):

      Well yes, MySQLdb does appear to support this kind of option, but the
      mapping seems currently incorrect. The existing PR will have Django
      [[https://github.com/django/django/blob/master/django/db/backends/mysql/base.py#L467|pass
      a `ca` parameter to MySQLdb]]. However, it should pass a dict into the
      `ssl` parameter, with a `ca` key, in my interpretation of the docs, and
      that seems
      [[https://github.com/farcepest/MySQLdb1/blob/master/_mysql.c#L620|confirmed
      by the source]]. I think it silently ignores unknown kwargs, causing the
      tests to still succeed.

    --
    Ticket URL: <https://code.djangoproject.com/ticket/22646#comment:7>
    Django <https://code.djangoproject.com/>
    The Web framework for perfectionists with deadlines.

    --
    You received this message because you are subscribed to the Google Groups "Django updates" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscribe@googlegroups.com.
    To post to this group, send email to django-updates@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.7884a1287c24046d06fa5270b2c71a1d%40djangoproject.com.
    For more options, visit https://groups.google.com/d/optout.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdjango-updates @
categoriesdjango, python
postedMay 17, '14 at 10:02a
activeMay 18, '14 at 3:27p
posts8
users1
websitedjangoproject.com

1 user in discussion

Django: 8 posts

People

Translate

site design / logo © 2018 Grokbase