New FreeBSD Security Officer

From: Jacques Vidrine (nectar_at_freebsd.org)
Date: 08/18/05

  • Next message: Attila Nagy: "Closing information leaks in jails?" 
    To: freebsd-security@FreeBSD.org
Date: Thu, 18 Aug 2005 07:58:34 -0500

    Hello Everyone!

    It has been my pleasure and privilege to serve as the FreeBSD
    Security Officer for the past 3+ years. With the crucial support of
    the FreeBSD Security Team members, a lot has been accomplished:
    hundreds of security issues have been researched and tracked, with
    some resulting in security advisories and patches; software in the
    Ports Collection are updated more quickly to remove vulnerabilities;
    flaws are well-documented in the Vulnerabilities and Exposures Markup
    Language (VuXML); communication with other software and hardware
    vendors, security researchers, and emergency response organizations
    has grown greatly; and the FreeBSD Security Branches are now
    supported for much longer period of time over a greater number of
    releases. I'd like to thank the members of the security team over
    the past few years for these accomplishments: Eivind Eklund, Julian
    Elischer, Chris Faulhaber, Bill Fumerola, Daniel Harris, Trevor
    Johnson, Remko Lodder, Simon Nielsen, Christian Peron, Wes Peters,
    Josef El-Rayes, Tom Rhodes, Gregory Shapiro, Bruce Simpson, Dag-
    Erling Smørgrav, and Robert Watson. Several of our previous security
    officers have also given much help: Kris Kennaway, Warner Losh, and
    Guido van Rooij.

    I asked the FreeBSD Core Team to offer the security officer role to
    Colin Percival, and I am happy to say that they agreed and that Colin
    accepted. Colin has been a FreeBSD committer since January 2004, and
    has been an energetic member of the FreeBSD Security Team for most of
    that time. He is well-known for his software creations "FreeBSD
    Update", "portsnap", and "bsdiff"; as well as his paper published
    earlier this year, "Cache Missing for Fun and Profit" <URL:http://
    www.daemonology.net/papers/htt.pdf>. I have no doubt that he will do
    an outstanding job fulfilling the FreeBSD Security Officer's charter.

    Thanks for everyone's support over the years, and please extend the
    same and more for Colin! Cheers, 

    -- 
Jacques Vidrine <nectar@FreeBSD.org>
_______________________________________________
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
  • Next message: Attila Nagy: "Closing information leaks in jails?"

    Relevant Pages

    • Security branch lifetime changes
      ... security branches in general: ... designation is used as a guideline for determining the lifetime of the branch ... the Security Officer for a minimum of 6 months after the release. ... would lead to a branch's support being dropped earlier than the date listed. ...
      (FreeBSD-Security)
    • @BSDcon: FreeBSD Security Officer BoF
      ... I have scheduled a birds-of-a-feather meeting at BSDcon to ... Please *do not* attend expecting to discuss general FreeBSD security ...
      (FreeBSD-Security)
    • Re: securing beyond the handbook.
      ... any of these that you know are such huge security ... Check some man pages for jail information: ... consider running host intrusion detection. ... FreeBSD security & hardening guide: http://www.syslog.org/Content-5-4.phtml ...
      (freebsd-questions)
    • Estimated EoL for 6.1-Release
      ... As per the security advisories page on the FreeBSD website, ... release is to be supported by the security officer for a period of 24 ... security support period. ...
      (freebsd-questions)
    • FW: {RTCProd#003-520-317}Windows Update Support Request
      ... support policy for Windows NT 4.0 Workstation SP6a. ... The Microsoft Support Lifecycle defines the support policies for all ... This means that after this date, Microsoft would no longer create ... security fixes for this platform, nor automatically post to WU, etc. ...
      (NT-Bugtraq)