Re: HMAC and timing based attacks - ticket #14445

On Tue, 2010-10-12 at 12:03 +0100, Luke Plant wrote: > The fixed strings are used to make the keys unique per application - see > below for what the keys are like that actually end up being used. I realise that, I just couldn't remember exactly why that was necessary... but you answered that

Re: Translating Django's documentation

On Tue, Oct 12, 2010 at 9:32 PM, Russell Keith-Magee wrote: > There are a bunch of modifications that we want to make to > docs.djangoproject.com, and providing support for other languages is > part of those improvements. Some recent additions to Sphinx should > make it

Re: Translating Django's documentation

On Wed, Oct 13, 2010 at 11:32 AM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > On Wed, Oct 13, 2010 at 10:20 AM, Ian Lewis wrote: > > Hi all, > > I am a member of the Japanese Django community which is maintaining a > > somewhat(read very) outdated version of the

Translating Django's documentation

Hi all, I am a member of the Japanese Django community which is maintaining a somewhat(read very) outdated version of the Django documentation here: http://djangoproject.jp/doc/ja/1.0/ I'm trying to kickstart a project to update the documentation and in

Re: It is real to add ticket #8054 to 1.3 milestone?

Hi alekam, This is certainly the kind of ticket that we want to deal with in 1.3 since it's been around so long and deferred a couple times. Starting the discussion here is definitely the right way to make it happen. That said, at the very least it needs a thorough code review, a full set of

It is real to add ticket #8054 to 1.3 milestone?

Hi All, I found very useful ticket #8054. This ticket has accepted status and assigned to brosher about 2 years. The problem describes on ticket detail page and in the wiki http://code.djangoproject.com/wiki/ListColumns The ticket has patch witch passes all existing regression tests and I plan to

Re: HMAC and timing based attacks - ticket #14445

On Mon, Oct 11, 2010 at 7:27 PM, Nick Phillips wrote: > First of all I should say that I'm no crypto expert, but I'm worried > about the key. Inclusion of fixed strings in a key for this type of use > rings alarm bells, as does the use of an ASCII key (albeit 50 chars >

Re: 8040 SlugField format not enforced - fixed, closed an "ready for checkin" since two years

I am sorry - you are right, I just found the error in my code sorry, sorry, sorry and thanks for the fast feedback! Sebastian On 12 Okt., 16:49, Peter Baumgartner wrote: > It just moved. See: > >

Re: 8040 SlugField format not enforced - fixed, closed an "ready for checkin" since two years

On Tue, 2010-10-12 at 07:44 -0700, Sebastian wrote: > Hello, > I investigated a bit further, it was commited with r8477 > http://code.djangoproject.com/changeset/8477 > > But somewhere it got lost. In the current definition for SlugField I > can only find a validation for max_length: >

Re: 8040 SlugField format not enforced - fixed, closed an "ready for checkin" since two years

It just moved. See: http://code.djangoproject.com/browser/django/trunk/django/forms/fields.py#L924 http://code.djangoproject.com/browser/django/trunk/django/core/validators.py#L122 -- Pete On Tue, Oct 12, 2010 at 8:44 AM, Sebastian wrote: > Hello, > I investigated a bit

Re: 8040 SlugField format not enforced - fixed, closed an "ready for checkin" since two years

Hello, I investigated a bit further, it was commited with r8477 http://code.djangoproject.com/changeset/8477 But somewhere it got lost. In the current definition for SlugField I can only find a validation for max_length:

Re: 8040 SlugField format not enforced - fixed, closed an "ready for checkin" since two years

On Tue, 2010-10-12 at 04:21 -0700, Sebastian wrote: > Hello, > the ticket "SlugField format not enforced" is fixed, closed an "ready > for checkin" since two years. What can I do? It is 'closed: fixed', which means the fix entered to the code base - two years ago, as you say. There is nothing

8040 SlugField format not enforced - fixed, closed an "ready for checkin" since two years

Hello, the ticket "SlugField format not enforced" is fixed, closed an "ready for checkin" since two years. What can I do? Regards, Sebastian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: HMAC and timing based attacks - ticket #14445

On Tue, 2010-10-12 at 15:27 +1300, Nick Phillips wrote: > First of all I should say that I'm no crypto expert, but I'm worried > about the key. Inclusion of fixed strings in a key for this type of use > rings alarm bells, as does the use of an ASCII key (albeit 50 chars > rather than the 20