Re: FreeBSD Security Advisory: FreeBSD-SA-01:18.bind

From: Garrett Wollman (wollman@khavrinen.lcs.mit.edu)
Date: 02/01/01 

Date: Thu, 1 Feb 2001 10:51:36 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
To: Neil Blakey-Milner <nbm@mithrandr.moria.org>

<<On Thu, 1 Feb 2001 12:02:19 +0200, Neil Blakey-Milner <nbm@mithrandr.moria.org> said:

> It might be an idea to actually research djbdns, consider its design,
> history, and coding standards, and then make a judgement.

While you're doing that, also consider the guy who wrote it, and
whether your view of the universe coincides with his.

-GAWollman

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

Relevant Pages

  • Re: FreeBSD Security Advisory: FreeBSD-SA-01:18.bind
    ... >It might be an idea to actually research djbdns, consider its design, ... >history, and coding standards, and then make a judgement. ...
    (FreeBSD-Security)
  • Re: Data modeling in MV, revisited
    ... Since we can think of files as modeling ... persistence for some reason and popping it back up when using it, ... The history is its own relation. ... how developers are supposed to design the data model in each. ...
    (comp.databases.pick)
  • Re: Order details table reference live data
    ... this means that all orders and history reports can get ... Design the data mart as a star schema. ... Build an ETL procedure that populates your star schema once a day. ...
    (comp.databases.theory)
  • Re: Variables Synthesysable ?
    ... Saves all variable history for a single process uut. ... It's not an unfamiliar command that needs to be mastered, ... maintain that as the design hierarchy evolves) to log that activity. ... I don't doubt that you can debug using the signals that you ...
    (comp.lang.vhdl)
  • Design for historical data
    ... Because my only real design experience is with Access, ... powerful SQL Server can be and the best way to design for it. ... All prior history must be ... patient - this would result in largest number of records in one table ...
    (microsoft.public.sqlserver.programming)