[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160306161617.GA30781@openwall.com>
Date: Sun, 6 Mar 2016 19:16:17 +0300
From: Solar Designer <solar@...nwall.com>
To: oss-security@...ts.openwall.com
Subject: Re: Concerns about CVE coverage shrinking - direct impact to researchers/companies
On Sun, Mar 06, 2016 at 03:47:19PM +0000, op7ic x00 wrote:
> agree, the vanity hunting is going to be there but I suppose as with any
> bug ID that is going to happen.
> But beyond that I don't think it matters as much. In the end of the day if
> somebody can use OVI or OVE to identify their bug then at least we got some
> level of reference to look it up on google.
Right.
> I was toying with 4digit IDs that would be random enough, thats a
> possiblity too, the only problem is that there is a overhead of doing DB
> sorting and lookups to make sure their don't clash. Thats why ovi uses
> sequential numbers - its just easier to manage.
Oh, you (would) use an actual database backend? OVE currently uses a C
program with a tiny binary data file (to keep track of per-IP and
per-netblock consumption of IDs, as well as the current date and ID),
and the file is wiped clean (by this same program) on first access after
midnight. I wrote this yesterday in response to the thread in here.
For random IDs, if we wanted those, there are shuffling algorithms that
don't require storage yet guarantee unique numbers (until the target
range is exhausted) - they're good e.g. for IP ID and DNS sequence
numbers - although checking against an array of 10k numbers is almost
instant anyway (as far as this application is concerned).
Anyway, this is getting off-topic.
Alexander
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.
