public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@gmail.com>
To: The Vulgar and Statistically Questionable Cygwin-Talk Maiming
	List <cygwin-talk@cygwin.com>
Subject: Re: hardware upgrade status
Date: Wed, 20 Mar 2013 13:43:00 -0000	[thread overview]
Message-ID: <5149BDAB.6090709@gmail.com> (raw)
In-Reply-To: <20130319213054.GA1821@ednor.casa.cgf.cx>

On 19/03/2013 21:30, Christopher Faylor wrote:

> ----- Forwarded message from "Frank Ch. Eigler" -----
> 
> From: "Frank Ch. Eigler"
> To: Sourceware Overseers
> Subject: sourceware hardware transition plan, part 1/N
> Date: Fri, 7 Sep 2012 17:46:32 -0400

> I would like to move from unusual/obsolete services to mainstream ones if
> at all possible, for simplicity of administration, and to reduce exposure
> to vulnerabilities.

>         old:                          new:

>         djbdns                        bind


  Heh.  That's a questionable statement, at best:

http://www.cvedetails.com/vulnerability-list/vendor_id-9069/product_id-16058/D.j.bernstein-Djbdns.html

> Total number of vulnerabilities : 3

http://www.cvedetails.com/vulnerability-list/vendor_id-64/product_id-144/ISC-Bind.html

> Total number of vulnerabilities : 72


  BTW, was it totally irrational of me to be so chuffed to see CGF using the
term "administering" a server rather than "administrating"?  I really dislike
the latter usage.

    cheers,
      DaveK

       reply	other threads:[~2013-03-20 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130319162805.GA5736@ednor.casa.cgf.cx>
     [not found] ` <20130319194322.GE40309@justpickone.org>
     [not found]   ` <20130319213054.GA1821@ednor.casa.cgf.cx>
2013-03-20 13:43     ` Dave Korn [this message]
2013-03-20 14:21       ` marco atzeri
2013-03-20 14:56       ` Christopher Faylor
2013-03-20 20:06         ` Linda Walsh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5149BDAB.6090709@gmail.com \
    --to=dave.korn.cygwin@gmail.com \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).