Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 01 May 2012 13:03:56 +0200
From: Florian Weimer <>
Subject: Re: weak use of crypto in python-elixir can lead to information disclosure (CVE and peer review request)

* Florian Weimer:

> * Vincent Danen:
>>>And you can group by encrypted column values in the database.  That's
>>>why I'm not sure if it's actually possible to address this issue in a
>>>satisfying manner.
>> So the encryption can be more fine-grained than just per-table?  You can
>> also do it per-column?  If that's the case, this does sound a lot uglier
>> to deal with.
> This test case suggests to me that you have to specify the list of
> encrypted columns explicitly:
> <>
> Based on this example, it's not clear to me if the current
> implementation supports get_by with an encrypted column.  If this is a
> feature which needs preserving, there is no apparent way around
> convergent encryption.

So it turns out that this passes the assert:

        p = Person.get_by(password='r\\x9d\\xa8\\xb4\\x8d|\\xffp\\xf5\\x0e')
        assert == 'Jonathan LaCour'

But this fails because p is None:

        p = Person.get_by(ssn='123-45-6789')
        assert == 'Jonathan LaCour'

This suggests to me that get_by on an encrypted column is not actually

The documentation doesn't describe which queries are supported:

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.