Hey Christian, On Wed, Aug 19, 2015 at 02:41:49PM -0700, Christian Hammond wrote:
Regarding the version number, from what I've read, there's still a reported compatibility issue if we use the +localidentifer part of a version number with older versions of setuptools. I need to do some testing on this. If I don't hit any issues, I'm very happy to put an identifier on there. I would like to keep it at 1.6.11.x, rather than 1.6.12+, so that it's very clear we're based on upstream Django 1.6.11.
Thanks, that sounds good to me. 1.6.11.x+unofficial if possible, otherwise 1.6.11.x
I want HTTPS on this pretty badly, though, so we might try that approach when we can get to it.
Good :)
To attempt to compensate for this, though, we sign all the builds and include checksums in both the links and in dedicated .sha256sum files. Not the best solution, but it's something at least :/
Checksums alone won't provide integrity checks if I can play MITM. Only (e.g. pgp) signatures will help. But then make sure the key ID is published on an HTTPS page ;) /Markus
On Wed, Aug 19, 2015 at 9:08 AM, Carl Meyer <c...@oddbird.net> wrote:Hi Christian, On 08/18/2015 08:01 PM, Christian Hammond wrote: [snip] > Also as a status update, we've started a fork and applied for the > pre-notification list. I've backported all current security fixes to a > branch, ensured the test suite passes with flying colors, and have added > a README detailing everything you've requested. This is all up at > https://github.com/beanbaginc/django. Let me know if there's anything > you'd like changed. One thing was pointed out to me just now -- the downloads page _really_ should use TLS. Any chance you could make that happen? Carl -- You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/69fOquu8v-U/unsubscribe . To unsubscribe from this group and all its topics, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/55D4AA04.3090403%40oddbird.net . For more options, visit https://groups.google.com/d/optout.-- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAHfcSbz%3DN9%2BFduAcSODtTVLEVmbD42Nu_CsiJHAQiXxtU70kCg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
-- -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20150819234311.GA2502%40pyler.local. For more options, visit https://groups.google.com/d/optout.
pgphn7ufHtysd.pgp
Description: PGP signature
