This page lists teams, groups and individuals within the FreeBSD project with designated project roles and areas of responsibility, along with brief descriptions and contact information.
The FreeBSD Core Team constitutes the project's "Board of Directors", responsible for deciding the project's overall goals and direction as well as managing specific areas of the FreeBSD project landscape. The Core Team is elected by the active developers in the project.
The FreeBSD Documentation Engineering Team is responsible for defining and following up documentation goals for the committers in the Documentation project. The doceng team charter describes the duties and responsibilities of the Documentation Engineering Team in greater detail.
The primary responsibility of the FreeBSD Port Management Team is to ensure that the FreeBSD Ports Developer community provides a ports collection that is functional, stable, up-to-date and full-featured. Its secondary responsibility is to coordinate among the committers and developers who work on it. The portmgr team charter describes the duties and responsibilities of the Port Management Team in greater detail.
The primary responsibility of the FreeBSD Port Security Team is to provide rapid response to security incidents that affects the FreeBSD ports collection and protect the FreeBSD user community by keeping the community informed of bugs, exploits, popular attacks, and other risks. More details are available on the Wiki page.
The Primary Release Engineering Team is responsible for setting and
publishing release schedules for official project releases of FreeBSD,
announcing code freezes and maintaining releng/* branches,
among other things. The
release engineering team charter
describes the duties and responsibilities of the Primary Release
Engineering Team in greater detail.
The builders release engineering team is responsible for building and packaging FreeBSD releases on the various supported platforms.
The FreeBSD Donations Team is responsible for responding to donations offers, establishing donation guidelines and procedures, and coordinating donation offers with the FreeBSD developer community. A more detailed description of the duties of the Donations Team is available on the FreeBSD Donations Liaison page.
The FreeBSD Security Team (headed by the Security Officer) is responsible for keeping the community aware of bugs, exploits and security risks affecting the FreeBSD src and ports trees, and to promote and distribute information needed to safely run FreeBSD systems. Furthermore, it is responsible for resolving software bugs affecting the security of FreeBSD and issuing security advisories. The FreeBSD Security Officer Charter describes the duties and responsibilities of the Security Officer in greater detail.
Vendor Relations is responsible for handling email from hardware and software vendors. Email sent to Vendor Relations is forwarded to the &os; Core Team in addition to the &os; Foundation.
The &os; Core Team Secretary is a non-voting member of the Core Team, responsible for documenting the work done by core, keeping track of the core agenda, contacting non-core members on behalf of core, sending mail to core, and interfacing with the admin team for committer/account approval. The Core Team Secretary is also responsible for writing and sending out monthly status reports to the &os; Developer community, containing a summary of core's latest decisions and actions.
The FreeBSD Port Management Team Secretary is a non-voting member of the Port Management Team, responsible for documenting the work done by portmgr, keeping track of voting procedures, and to be an interface to the other teams, especially the admin and Core teams. The Port Management Team Secretary is also responsible for writing and sending out monthly status reports to the FreeBSD Developer community, containing a summary of portmgr's latest decisions and actions.
The Accounts Team is responsible for setting up accounts for new committers in the project. Requests for new accounts will not be acted upon without the proper approval from the appropriate entity.
Email sent to the Accounts Team is currently forwarded to the Cluster Administrators.
The Backups Administrators handle all backups on the FreeBSD cluster.
Email sent to the Backups Team is currently forwarded to the Cluster Administrators.
The Bugmeisters are responsible for ensuring that the problem report software is in working order, that the entries are correctly categorised and that there are no invalid entries.
The Cluster Administrators consists of the people responsible for maintaing the machines and services that the project relies on for its distributed work and communication. Issues concerning the projects infrastructure or setting up new machines should be directed to them. This team is led by the lead cluster administrator whose duties and responsbilities are described in the cluster administration charter in greater detail.
The DNS Administrators are responsible for managing DNS and related services.
E-mail to the DNS Administrators is currently forwarded to the Cluster Administrators.
The Forum Administrators maintain the &os; Project's Internet forum, located at https://forums.freebsd.org/ and lead the group of moderators who work to ensure the relevance and quality of the forum's content.
The GitHub Automation team oversees the export of &os; source code repository content to the read-only repository instances on GitHub
The Jenkins Administrators maintain the Continuous Integration and testing infrastructure for The &os; Project. This includes maintaining the Jenkins instance and the jobs that run builds and execute tests.
The FTP/WWW Mirror Site Coordinators coordinate all the FTP/WWW mirror site administrators to ensure that they are distributing current versions of the software, that they have the capacity to update themselves when major updates are in progress, and making it easy for the general public to find their closest FTP/WWW mirror.
E-mail to the Mirror Site Coordinators is currently forwarded to the Cluster Administrators with the addition of:
The Phabricator Administrators are responsible for maintaining the &os;'s instance of the Phabricator on-line code review tool located at https://reviews.freebsd.org/
For any problems regarding Phabricator, please open a bug report and select "Services" and then "Code Review".
The Postmaster Team is responsible for mail being correctly delivered to the committers' email address, ensuring that the mailing lists work, and should take measures against possible disruptions of project mail services, such as having troll-, spam- and virus-filters.
The FreeBSD Subversion team is responsible for maintaining the health of the Subversion Repositories.
Email to the Subversion Administration team is currently forwarded to the Cluster Administrators.
The FreeBSD Webmaster Team is appointed by &os; Documentation Engineering Team, and responsible for keeping the main FreeBSD web sites up and running. This means web server configuration, CGI scripts, fulltext and mailing list search. Anything web related, technical stuff belongs to the scope of the Webmaster Team, excluding bugs in the documentation.
Email to the Webmaster Team is currently forwarded to the Documentation Engineering team with the addition of:
The FreeBSD Wiki Team is responsible for keeping the FreeBSD Wiki site up and running. They also shape the overall design and content structure.
FreeBSD security issues specific to the operating system should be reported to the FreeBSD Security Team or, if a higher level of confidentiality is required, PGP encrypted to the Security Officer Team using the Security Officer PGP key.
FreeBSD security issues specific to the Ports Collection should be reported to the FreeBSD Ports Security Team.
All reports should contain at least:
Whenever possible, including the background, problem description, impact, and workaround (if applicable) using the templates for security advisories and errata notices as appropriate would also be helpful.
After this information has been reported the Security Officer or a Security Team delegate will get back to you.
Due to high volume of spam the main security contact mail addresses are subject to spam filtering. If you cannot contact the FreeBSD Security Officers or Security Team due to spam filters (or suspect your mail has been filtered), please send mail to security-officer-XXXX@FreeBSD.org with XXXX replaced with 3432 instead of the normal addresses. Note that this address will be changed periodically so check back here for the latest address. Mails to this address will go to the FreeBSD Security Officer Team.
In order that the FreeBSD Project may respond to vulnerability reports in a timely manner, emails sent to the <security-officer@FreeBSD.org> mail alias are currently delivered to the following people:
| &a.gordon.email; | Security Officer |
| &a.emaste.email; | Deputy Security Officer |
| &a.remko.email; | -Deputy Security Officer | -
| &a.delphij.email; | Security Officer Emeritus |
| &a.des.email; | Security Officer Emeritus |
The Security Officer is supported by the FreeBSD Security Team, <secteam@FreeBSD.org>, a small group of committers vetted by the Security Officer.
As a general policy, the FreeBSD Security Officer favors full disclosure of vulnerability information after a reasonable delay to permit safe analysis and correction of a vulnerability, as well as appropriate testing of the correction, and appropriate coordination with other affected parties.
The Security Officer will notify one or more of the FreeBSD Cluster Admins of vulnerabilities that put the FreeBSD Project's resources under immediate danger.
The Security Officer may bring additional FreeBSD developers or outside developers into discussion of a submitted security vulnerability if their expertise is required to fully understand or correct the problem. Appropriate discretion will be exercised to minimize unnecessary distribution of information about the submitted vulnerability, and any experts brought in will act in accordance of Security Officer policies. In the past, experts have been brought in based on extensive experience with highly complex components of the operating system, including FFS, the VM system, and the network stack.
If a FreeBSD release process is underway, the FreeBSD Release Engineer may also be notified that a vulnerability exists, and its severity, so that informed decisions may be made regarding the release cycle and any serious security bugs present in software associated with an up-coming release. If requested, the Security Officer will not share information regarding the nature of the vulnerability with the Release Engineer, limiting information flow to existence and severity.
The FreeBSD Security Officer has close working relationships with a number of other organizations, including third-party vendors that share code with FreeBSD (the OpenBSD, NetBSD and DragonFlyBSD projects, Apple, and other vendors deriving software from FreeBSD, as well as the Linux vendor security list), as well as organizations that track vulnerabilities and security incidents, such as CERT. Frequently vulnerabilities may extend beyond the scope of the FreeBSD implementation, and (perhaps less frequently) may have broad implications for the global networking community. Under such circumstances, the Security Officer may wish to disclose vulnerability information to these other organizations: if you do not wish the Security Officer to do this, please indicate so explicitly in any submissions.
Submitters should be careful to explicitly document any special information handling requirements.
If the submitter of a vulnerability is interested in a coordinated disclosure process with the submitter and/or other vendors, this should be indicated explicitly in any submissions. In the absence of explicit requests, the FreeBSD Security Officer will select a disclosure schedule that reflects both a desire for timely disclosure and appropriate testing of any solutions. Submitters should be aware that if the vulnerability is being actively discussed in public forums (such as bugtraq), and actively exploited, the Security Officer may choose not to follow a proposed disclosure timeline in order to provide maximum protection for the user community.
Submissions may be protected using PGP. If desired, responses will also be protected using PGP.
Index: head/en_US.ISO8859-1/htdocs/security/security.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/security/security.xml (revision 52957) +++ head/en_US.ISO8859-1/htdocs/security/security.xml (revision 52958) @@ -1,204 +1,242 @@ ]>FreeBSD takes security very seriously and its developers are constantly working on making the operating system as secure as possible. This page will provide information about what to do in the event of a security vulnerability affecting your system
FreeBSD security issues specific to the base system should be reported via email to the FreeBSD Security Team or, if a higher level of confidentiality is required, via PGP encrypted email to the Security Officer Team using the Security Officer PGP key. Additional information can be found at the reporting FreeBSD security incidents page.
+ +For every issue that gets reported, an internal tracking number is + created, unless something is very obviously not a security issue. + To determine whether or not a Security Advisory is warranted we use + the following scheme:
+ +For items that fall under these categories, a Security Advisory is very likely. + Items that are not on this list are looked into individually and it will be determined + then whether or not it will receive a Security Advisory or an Errata Notice.
+ +Once it had been determined that a Security Advisory is warranted, either the + submitter delivers a CVE number if he/she already requested one, or we use one + from the FreeBSD pool available.
+A full list of all security vulnerabilities affecting the base system can be found on this page.
Advisories affecting the base system are sent to the following mailing lists:
The list of released advisories can be found on the FreeBSD Security Advisories page.
Advisories are always signed using the FreeBSD Security Officer PGP key and are archived, along with their associated patches, at the http://security.FreeBSD.org/ web server in the advisories and patches subdirectories.
The FreeBSD Security Officer provides security advisories for -STABLE Branches and the Security Branches. (Advisories are not issued for the -CURRENT Branch, which is primarily oriented towards &os; developers.)
The -STABLE branch tags have names like stable/10. The corresponding builds have names like FreeBSD 10.1-STABLE.
Each FreeBSD Release has an associated Security Branch. The Security Branch tags have names like releng/10.1. The corresponding builds have names like FreeBSD 10.1-RELEASE-p4.
Issues affecting the FreeBSD Ports Collection are covered separately in the FreeBSD VuXML document.
For users that have previously installed a binary version of &os; (e.g., &rel.current; or &rel2.current;), commands:
# freebsd-update fetchIf that fails, follow the other instructions in the security advisory you care about.
Note that the above procedure is only for users who have previously installed a binary distribution. Those who have built from source will need to update their source tree to upgrade.
Each release is supported by the Security Officer for a limited time only.
The designation and expected lifetime of all currently supported branches and their respective releases are given below. The Expected EoL (end-of-life) column indicates the earliest date on which support for that branch or release will end. Please note that these dates may be pushed back if circumstances warrant it.
Older releases are not supported and users are strongly encouraged to upgrade to one of these supported releases:
| Branch | Release | Type | Release Date | Expected EoL |
|---|---|---|---|---|
| stable/12 | n/a | n/a | n/a | June 30, 2020 (TBD) |
| releng/12.0 | 12.0-RELEASE | n/a | December 11, 2018 | 12.1-RELEASE + 3 months |
| stable/11 | n/a | n/a | n/a | September 30, 2021 |
| releng/11.2 | 11.2-RELEASE | n/a | June 28, 2018 | 11.3-RELEASE + 3 months |
In the run-up to a release, a number of -BETA and -RC releases may be published for testing purposes. These releases are only supported for a few weeks, as resources permit, and will not be listed as supported on this page. Users are strongly discouraged from running these releases on production systems.
Under the current support model, each major version's stable branch is explicitly supported for 5 years, while each individual point release is only supported for three months after the next point release.
The details and rationale behind this model can be found in the official announcement sent in February 2015.
Index: head/share/xml/authors.ent =================================================================== --- head/share/xml/authors.ent (revision 52957) +++ head/share/xml/authors.ent (revision 52958) @@ -1,2669 +1,2669 @@ 0mp@FreeBSD.org"> aaron@FreeBSD.org"> abial@FreeBSD.org"> ache@FreeBSD.org"> achim@FreeBSD.org"> acm@FreeBSD.org"> adam@FreeBSD.org"> adamw@FreeBSD.org"> ade@FreeBSD.org"> adrian@FreeBSD.org"> adridg@FreeBSD.org"> ae@FreeBSD.org"> ahasty@FreeBSD.org"> ahd@FreeBSD.org"> ahze@FreeBSD.org"> ak@FreeBSD.org"> akiyama@FreeBSD.org"> alane@FreeBSD.org"> alc@FreeBSD.org"> ale@FreeBSD.org"> alepulver@FreeBSD.org"> alex@FreeBSD.org"> alexbl@FreeBSD.org"> alexey@FreeBSD.org"> alfred@FreeBSD.org"> allanjude@FreeBSD.org"> alm@FreeBSD.org"> alonso@FreeBSD.org"> am@FreeBSD.org"> ambrisko@FreeBSD.org"> amdmi3@FreeBSD.org"> amorita@FreeBSD.org"> amurai@FreeBSD.org"> anchie@FreeBSD.org"> anders@FreeBSD.org"> andre@FreeBSD.org"> andreas@FreeBSD.org"> andreast@FreeBSD.org"> andrew@FreeBSD.org"> andy@FreeBSD.org"> anholt@FreeBSD.org"> anish@FreeBSD.org"> anray@FreeBSD.org"> antoine@FreeBSD.org"> araujo@FreeBSD.org"> archie@FreeBSD.org"> arichardson@FreeBSD.org"> ariff@FreeBSD.org"> arr@FreeBSD.org"> arrowd@FreeBSD.org"> art@FreeBSD.org"> arun@FreeBSD.org"> arundel@FreeBSD.org"> arved@FreeBSD.org"> arybchik@FreeBSD.org"> asami@FreeBSD.org"> ashish@FreeBSD.org"> asmodai@FreeBSD.org"> asomers@FreeBSD.org"> assar@FreeBSD.org"> ats@FreeBSD.org"> attilio@FreeBSD.org"> avatar@FreeBSD.org"> avg@FreeBSD.org"> avilla@FreeBSD.org"> avl@FreeBSD.org"> avos@FreeBSD.org"> awebster@pubnix.net"> az@FreeBSD.org"> babb@FreeBSD.org"> babkin@FreeBSD.org"> badger@FreeBSD.org"> bakul@FreeBSD.org"> bapt@FreeBSD.org"> bar@FreeBSD.org"> barner@FreeBSD.org"> bbraun@FreeBSD.org"> bcr@FreeBSD.org"> bcran@FreeBSD.org"> bde@FreeBSD.org"> bdrewery@FreeBSD.org"> bean@FreeBSD.org"> beat@FreeBSD.org"> beech@FreeBSD.org"> ben@FreeBSD.org"> benjsc@FreeBSD.org"> benl@FreeBSD.org"> benno@FreeBSD.org"> brnrd@FreeBSD.org"> bf@FreeBSD.org"> bgray@FreeBSD.org"> bhaga@FreeBSD.org"> bhd@FreeBSD.org"> billf@FreeBSD.org"> bjk@FreeBSD.org"> bk@FreeBSD.org"> blackend@FreeBSD.org"> bland@FreeBSD.org"> bmah@FreeBSD.org"> bmilekic@FreeBSD.org"> bms@FreeBSD.org"> bofh@FreeBSD.org"> bp@FreeBSD.org"> br@FreeBSD.org"> brandon@FreeBSD.org"> brd@FreeBSD.org"> bhughes@FreeBSD.org"> brian@FreeBSD.org"> brix@FreeBSD.org"> brooks@FreeBSD.org"> brucec@FreeBSD.org"> brueffer@FreeBSD.org"> bruno@FreeBSD.org"> bryanv@FreeBSD.org"> bsam@FreeBSD.org"> bschmidt@FreeBSD.org"> bsd@FreeBSD.org"> bushman@FreeBSD.org"> bvs@FreeBSD.org"> bwidawsky@FreeBSD.org"> bz@FreeBSD.org"> carl@FreeBSD.org"> carvay@FreeBSD.org"> cawimm@FreeBSD.org"> cbzimmer@FreeBSD.org"> cel@FreeBSD.org"> cem@FreeBSD.org"> ceri@FreeBSD.org"> cg@FreeBSD.org"> charnier@FreeBSD.org"> chern@FreeBSD.org"> cherry@FreeBSD.org"> chinsan@FreeBSD.org"> chm@FreeBSD.org"> chmr@FreeBSD.org"> chris@FreeBSD.org"> chuck@FreeBSD.org"> chuckr@FreeBSD.org"> cjc@FreeBSD.org"> cjh@FreeBSD.org"> clement@FreeBSD.org"> clive@FreeBSD.org"> clsung@FreeBSD.org"> cmt@FreeBSD.org"> cognet@FreeBSD.org"> cokane@FreeBSD.org"> conklin@FreeBSD.org"> cp@FreeBSD.org"> cperciva@FreeBSD.org"> cpiazza@FreeBSD.org"> cpm@FreeBSD.org"> cracauer@FreeBSD.org"> crees@FreeBSD.org"> cs@FreeBSD.org"> csgr@FreeBSD.org"> cshumway@FreeBSD.org"> csjp@FreeBSD.org"> culot@FreeBSD.org"> cwt@FreeBSD.org"> cy@FreeBSD.org"> dab@FreeBSD.org"> daichi@FreeBSD.org"> damien@FreeBSD.org"> dan@FreeBSD.org"> danfe@FreeBSD.org"> danger@FreeBSD.org"> danilo@FreeBSD.org"> danny@FreeBSD.org"> dannyboy@FreeBSD.org"> darrenr@FreeBSD.org"> das@FreeBSD.org"> davidc@FreeBSD.org"> davidch@FreeBSD.org"> davidcs@FreeBSD.org"> davide@FreeBSD.org"> davidn@FreeBSD.org"> davidxu@FreeBSD.org"> db@FreeBSD.org"> dbaio@FreeBSD.org"> dbaker@FreeBSD.org"> dbn@FreeBSD.org"> dburr@FreeBSD.org"> dch@FreeBSD.org"> dchagin@FreeBSD.org"> dcs@FreeBSD.org"> dd@FreeBSD.org"> dds@FreeBSD.org"> deb@FreeBSD.org"> dec@FreeBSD.org"> decke@FreeBSD.org"> def@FreeBSD.org"> deischen@FreeBSD.org"> delphij@FreeBSD.org"> demon@FreeBSD.org"> den@FreeBSD.org"> des@FreeBSD.org"> dexter@FreeBSD.org"> dfr@FreeBSD.org"> dg@FreeBSD.org"> dhartmei@FreeBSD.org"> dhn@FreeBSD.org"> dhw@FreeBSD.org"> dick@FreeBSD.org"> dillon@FreeBSD.org"> dim@FreeBSD.org"> dima@FreeBSD.org"> dinoex@FreeBSD.org"> dirk@FreeBSD.org"> dmarion@FreeBSD.org"> dmlb@FreeBSD.org"> don@FreeBSD.org"> dougb@FreeBSD.org"> dru@FreeBSD.org"> dryice@FreeBSD.org"> ds@FreeBSD.org"> dt@FreeBSD.org"> dteske@FreeBSD.org"> dufault@FreeBSD.org"> dumbbell@FreeBSD.org"> dutchdaemon@FreeBSD.org"> dvl@FreeBSD.org"> dwcjr@FreeBSD.org"> dwhite@FreeBSD.org"> dwmalone@FreeBSD.org"> dyson@FreeBSD.org"> eadler@FreeBSD.org"> ebrandi@FreeBSD.org"> ed@FreeBSD.org"> edavis@FreeBSD.org"> edwin@FreeBSD.org"> egypcio@FreeBSD.org"> ehaupt@FreeBSD.org"> eik@FreeBSD.org"> eivind@FreeBSD.org"> ejc@FreeBSD.org"> emaste@FreeBSD.org"> emax@FreeBSD.org"> emoore@FreeBSD.org"> eri@FreeBSD.org"> eric@FreeBSD.org"> ericbsd@FreeBSD.org"> erich@FreeBSD.org"> erik@FreeBSD.org"> erj@FreeBSD.org"> erwin@FreeBSD.org"> eugen@FreeBSD.org"> fabient@FreeBSD.org"> fanf@FreeBSD.org"> farrokhi@FreeBSD.org"> feld@FreeBSD.org"> fenner@FreeBSD.org"> fernape@FreeBSD.org"> fjoe@FreeBSD.org"> flathill@FreeBSD.org"> flo@FreeBSD.org"> fluffy@FreeBSD.org"> flz@FreeBSD.org"> foxfair@FreeBSD.org"> fsmp@FreeBSD.org"> fsu@FreeBSD.org"> furuta@FreeBSD.org"> gabor@FreeBSD.org"> gad@FreeBSD.org"> gahr@FreeBSD.org"> gallatin@FreeBSD.org"> ganbold@FreeBSD.org"> garga@FreeBSD.org"> garys@FreeBSD.org"> gavin@FreeBSD.org"> gber@FreeBSD.org"> gblach@FreeBSD.org"> gclarkii@FreeBSD.org"> gehenna@FreeBSD.org"> gerald@FreeBSD.org"> ghelmer@FreeBSD.org"> gibbs@FreeBSD.org"> gioria@FreeBSD.org"> girgen@FreeBSD.org"> gj@FreeBSD.org"> gjb@FreeBSD.org"> glarkin@FreeBSD.org"> gleb@FreeBSD.org"> glebius@FreeBSD.org"> glewis@FreeBSD.org"> gnn@FreeBSD.org"> gonzo@FreeBSD.org"> gordon@FreeBSD.org"> gpalmer@FreeBSD.org"> graichen@FreeBSD.org"> green@FreeBSD.org"> grehan@FreeBSD.org"> greid@FreeBSD.org"> grembo@FreeBSD.org"> grog@FreeBSD.org"> groudier@FreeBSD.org"> gryphon@FreeBSD.org"> gshapiro@FreeBSD.org"> gsutter@FreeBSD.org"> guido@FreeBSD.org"> hanai@FreeBSD.org"> harti@FreeBSD.org"> helbig@FreeBSD.org"> hiren@FreeBSD.org"> hm@FreeBSD.org"> hmp@FreeBSD.org"> hoek@FreeBSD.org"> horikawa@FreeBSD.org"> hosokawa@FreeBSD.org"> hq@FreeBSD.org"> hrs@FreeBSD.org"> hselasky@FreeBSD.org"> hsu@FreeBSD.org"> ian@FreeBSD.org"> iedowse@FreeBSD.org"> ijliao@FreeBSD.org"> ikob@FreeBSD.org"> imp@FreeBSD.org"> imura@FreeBSD.org"> issei@FreeBSD.org"> issyl0@FreeBSD.org"> itetcu@FreeBSD.org"> itojun@FreeBSD.org"> ivadasz@FreeBSD.org"> ivoras@FreeBSD.org"> iwasaki@FreeBSD.org"> jacula@FreeBSD.org"> jadawin@FreeBSD.org"> jah@FreeBSD.org"> jake@FreeBSD.org"> jamie@FreeBSD.org"> jamil@FreeBSD.org"> jase@FreeBSD.org"> jasone@FreeBSD.org"> jayanth@FreeBSD.org"> jb@FreeBSD.org"> jbeich@FreeBSD.org"> jcamou@FreeBSD.org"> jceel@FreeBSD.org"> jch@FreeBSD.org"> jchandra@FreeBSD.org"> jdp@FreeBSD.org"> jeb@FreeBSD.org"> jedgar@FreeBSD.org"> jeff@FreeBSD.org"> jeh@FreeBSD.org"> jehamby@FreeBSD.org"> jennifer@FreeBSD.org"> jesper@FreeBSD.org"> jesusr@FreeBSD.org"> jfieber@FreeBSD.org"> jfitz@FreeBSD.org"> jfv@FreeBSD.org"> jgh@FreeBSD.org"> jgreco@FreeBSD.org"> jh@FreeBSD.org"> jhale@FreeBSD.org"> jhay@FreeBSD.org"> jhb@FreeBSD.org"> jhibbits@FreeBSD.org"> jhixson@FreeBSD.org"> jhs@FreeBSD.org"> jilles@FreeBSD.org"> jim@FreeBSD.org"> jimharris@FreeBSD.org"> jinmei@FreeBSD.org"> jkb@FreeBSD.org"> jkh@FreeBSD.org"> jkim@FreeBSD.org"> jkois@FreeBSD.org"> jkoshy@FreeBSD.org"> jlaffaye@FreeBSD.org"> jlemon@FreeBSD.org"> jlh@FreeBSD.org"> jlrobin@FreeBSD.org"> jls@FreeBSD.org"> jmacd@FreeBSD.org"> jmallett@FreeBSD.org"> jmas@FreeBSD.org"> jmb@FreeBSD.org"> jmcneill@FreeBSD.org"> jmd@FreeBSD.org"> jmelo@FreeBSD.org"> jmg@FreeBSD.org"> jmmv@FreeBSD.org"> jmz@FreeBSD.org"> joe@FreeBSD.org"> joel@FreeBSD.org"> joerg@FreeBSD.org"> johalun@FreeBSD.org"> johan@FreeBSD.org"> johans@FreeBSD.org"> john@FreeBSD.org"> jon@FreeBSD.org"> jonathan@FreeBSD.org"> joneum@FreeBSD.org"> josef@FreeBSD.org"> jpaetzel@FreeBSD.org"> jraynard@FreeBSD.org"> jrm@FreeBSD.org"> jsa@FreeBSD.org"> jseger@FreeBSD.org"> jsm@FreeBSD.org"> jtc@FreeBSD.org"> jtl@FreeBSD.org"> julian@FreeBSD.org"> junovitch@FreeBSD.org"> jvh@FreeBSD.org"> jwb@FreeBSD.org"> jwd@FreeBSD.org"> jylefort@FreeBSD.org"> kai@FreeBSD.org"> kaiw@FreeBSD.org"> kan@FreeBSD.org"> karels@FreeBSD.org"> kargl@FreeBSD.org"> karl@FreeBSD.org"> kato@FreeBSD.org"> kbowling@FreeBSD.org"> kbyanc@FreeBSD.org"> keichii@FreeBSD.org"> keith@FreeBSD.org"> kadesai@FreeBSD.org"> ken@FreeBSD.org"> kensmith@FreeBSD.org"> keramida@FreeBSD.org"> kevans@FreeBSD.org"> kevlo@FreeBSD.org"> kib@FreeBSD.org"> kibab@FreeBSD.org"> kientzle@FreeBSD.org"> kiri@FreeBSD.org"> kishore@FreeBSD.org"> kjc@FreeBSD.org"> kmacy@FreeBSD.org"> kmoore@FreeBSD.org"> knu@FreeBSD.org"> koitsu@FreeBSD.org"> koobs@FreeBSD.org"> kp@FreeBSD.org"> krion@FreeBSD.org"> kris@FreeBSD.org"> kuku@FreeBSD.org"> kuriyama@FreeBSD.org"> kwm@FreeBSD.org"> landonf@FreeBSD.org"> lars@FreeBSD.org"> laszlof@FreeBSD.org"> lawrance@FreeBSD.org"> lbr@FreeBSD.org"> le@FreeBSD.org"> leeym@FreeBSD.org"> leitao@FreeBSD.org"> ler@FreeBSD.org"> leres@FreeBSD.org"> lesi@FreeBSD.org"> lev@FreeBSD.org"> lidl@FreeBSD.org"> lifanov@FreeBSD.org"> lile@FreeBSD.org"> linimon@FreeBSD.org"> lioux@FreeBSD.org"> lippe@FreeBSD.org"> ljo@FreeBSD.org"> lkoeller@FreeBSD.org"> lme@FreeBSD.org"> loader@FreeBSD.org"> lofi@FreeBSD.org"> logo@FreeBSD.org"> loos@FreeBSD.org"> lstewart@FreeBSD.org"> lth@FreeBSD.org"> luigi@FreeBSD.org"> lulf@FreeBSD.org"> luoqi@FreeBSD.org"> luporl@FreeBSD.org"> lwhsu@FreeBSD.org"> lx@FreeBSD.org"> madpilot@FreeBSD.org"> maho@FreeBSD.org"> mahrens@FreeBSD.org"> makc@FreeBSD.org"> mandree@FreeBSD.org"> manolis@FreeBSD.org"> manu@FreeBSD.org"> marcel@FreeBSD.org"> marck@FreeBSD.org"> marcus@FreeBSD.org"> marino@FreeBSD.org"> marius@FreeBSD.org"> markj@FreeBSD.org"> markm@FreeBSD.org"> marko@FreeBSD.org"> markp@FreeBSD.org"> marks@FreeBSD.org"> markus@FreeBSD.org"> martin@FreeBSD.org"> martymac@FreeBSD.org"> mat@FreeBSD.org"> matk@FreeBSD.org"> matt@FreeBSD.org"> matteo@FreeBSD.org"> matthew@FreeBSD.org"> matusita@FreeBSD.org"> mav@FreeBSD.org"> max@FreeBSD.org"> maxim@FreeBSD.org"> mb@FreeBSD.org"> mbarkah@FreeBSD.org"> mbr@FreeBSD.org"> mckay@FreeBSD.org"> mckusick@FreeBSD.org"> mdf@FreeBSD.org"> mdodd@FreeBSD.org"> meganm@FreeBSD.org"> melifaro@FreeBSD.org"> meta@FreeBSD.org"> metal@FreeBSD.org"> mezz@FreeBSD.org"> mfechner@FreeBSD.org"> mharo@FreeBSD.org"> mheinen@FreeBSD.org"> mhorne@FreeBSD.org"> mi@FreeBSD.org"> mich@FreeBSD.org"> mike@FreeBSD.org"> mikeh@FreeBSD.org"> milki@FreeBSD.org"> mini@FreeBSD.org"> misha@FreeBSD.org"> mita@FreeBSD.org"> miwi@FreeBSD.org"> mizhka@FreeBSD.org"> mjacob@FreeBSD.org"> mjg@FreeBSD.org"> mjoras@FreeBSD.org"> mks@FreeBSD.org"> mlaier@FreeBSD.org"> mm@FreeBSD.org"> mmel@FreeBSD.org"> mmokhi@FreeBSD.org"> mmoll@FreeBSD.org"> mnag@FreeBSD.org"> mohans@FreeBSD.org"> monthadar@FreeBSD.org"> motoyuki@FreeBSD.org"> mp@FreeBSD.org"> mph@FreeBSD.org"> mpp@FreeBSD.org"> mr@FreeBSD.org"> msmith@FreeBSD.org"> mtaylor@FreeBSD.org"> mtm@FreeBSD.org"> murray@FreeBSD.org"> mux@FreeBSD.org"> mva@FreeBSD.org"> mw@FreeBSD.org"> mwlucas@FreeBSD.org"> naddy@FreeBSD.org"> nakai@FreeBSD.org"> nate@FreeBSD.org"> nbm@FreeBSD.org"> nectar@FreeBSD.org"> neel@FreeBSD.org"> nemoliu@FreeBSD.org"> netchild@FreeBSD.org"> newton@FreeBSD.org"> ngie@FreeBSD.org"> n_hibma@FreeBSD.org"> niels@FreeBSD.org"> nik@FreeBSD.org"> niklas@FreeBSD.org"> nivit@FreeBSD.org"> njl@FreeBSD.org"> nobutaka@FreeBSD.org"> non@FreeBSD.org"> nork@FreeBSD.org"> novel@FreeBSD.org"> nox@FreeBSD.org"> np@FreeBSD.org"> nra@FreeBSD.org"> nsayer@FreeBSD.org"> nsj@FreeBSD.org"> nsouch@FreeBSD.org"> nwhitehorn@FreeBSD.org"> nyan@FreeBSD.org"> obraun@FreeBSD.org"> obrien@FreeBSD.org"> ohauer@FreeBSD.org"> okazaki@FreeBSD.org"> olah@FreeBSD.org"> oleg@FreeBSD.org"> olgeni@FreeBSD.org"> oliver@FreeBSD.org"> olivier@FreeBSD.org"> olivierd@FreeBSD.org"> olli@FreeBSD.org"> onoe@FreeBSD.org"> orion@FreeBSD.org"> osa@FreeBSD.org"> oshogbo@FreeBSD.org"> pat@FreeBSD.org"> patrick@FreeBSD.org"> paul@FreeBSD.org"> pav@FreeBSD.org"> pawel@FreeBSD.org"> pb@FreeBSD.org"> pclin@FreeBSD.org"> pdeuskar@FreeBSD.org"> pds@FreeBSD.org"> peadar@FreeBSD.org"> perky@FreeBSD.org"> petef@FreeBSD.org"> peter@FreeBSD.org"> peterj@FreeBSD.org"> pfg@FreeBSD.org"> pgj@FreeBSD.org"> pgollucci@FreeBSD.org"> phantom@FreeBSD.org"> phil@FreeBSD.org"> philip@FreeBSD.org"> phk@FreeBSD.org"> pho@FreeBSD.org"> pi@FreeBSD.org"> piero@FreeBSD.org"> pirzyk@FreeBSD.org"> piso@FreeBSD.org"> pizzamig@FreeBSD.org"> pjd@FreeBSD.org"> pkelsey@FreeBSD.org"> pkubaj@FreeBSD.org"> plosher@FreeBSD.org"> pluknet@FreeBSD.org"> proven@FreeBSD.org"> ps@FreeBSD.org"> pst@FreeBSD.org"> pstef@FreeBSD.org"> qingli@FreeBSD.org"> ram@FreeBSD.org"> rafan@FreeBSD.org"> raj@FreeBSD.org"> rakuco@FreeBSD.org"> randi@FreeBSD.org"> ray@FreeBSD.org"> rcyu@FreeBSD.org"> rdivacky@FreeBSD.org"> rea@FreeBSD.org"> rees@FreeBSD.org"> reg@FreeBSD.org"> remko@FreeBSD.org"> rene@FreeBSD.org"> rezny@FreeBSD.org"> rgrimes@FreeBSD.org"> ricardag@FreeBSD.org"> rich@FreeBSD.org"> riggs@FreeBSD.org"> rigoletto@FreeBSD.org"> rik@FreeBSD.org"> rink@FreeBSD.org"> rlibby@FreeBSD.org"> rpokala@FreeBSD.org"> rm@FreeBSD.org"> nemysis@FreeBSD.org"> rmacklem@FreeBSD.org"> rmh@FreeBSD.org"> rnoland@FreeBSD.org"> rnordier@FreeBSD.org"> roam@FreeBSD.org"> robak@FreeBSD.org"> robert@FreeBSD.org"> roberto@FreeBSD.org"> rodrigc@FreeBSD.org"> rodrigo@FreeBSD.org"> roger@FreeBSD.org"> romain@FreeBSD.org"> royger@FreeBSD.org"> rpaulo@FreeBSD.org"> rpratt@FreeBSD.org"> rrs@FreeBSD.org"> rse@FreeBSD.org"> rsm@FreeBSD.org"> rstone@FreeBSD.org"> ru@FreeBSD.org"> rushani@FreeBSD.org"> rv@FreeBSD.org"> rvb@FreeBSD.org"> rwatson@FreeBSD.org"> ryusuke@FreeBSD.org"> sada@FreeBSD.org"> sah@FreeBSD.org"> sahil@FreeBSD.org"> sam@FreeBSD.org"> sanpei@FreeBSD.org"> sat@FreeBSD.org"> sbruno@FreeBSD.org"> sbz@FreeBSD.org"> scf@FreeBSD.org"> scheidell@FreeBSD.org"> schweikh@FreeBSD.org"> scop@FreeBSD.org"> scottl@FreeBSD.org"> scrappy@FreeBSD.org"> se@FreeBSD.org"> sean@FreeBSD.org"> seanc@FreeBSD.org"> sef@FreeBSD.org"> sem@FreeBSD.org"> semenu@FreeBSD.org"> sephe@FreeBSD.org"> sepotvin@FreeBSD.org"> sergei@FreeBSD.org"> sevan@FreeBSD.org"> sf@FreeBSD.org"> sgalabov@FreeBSD.org"> shafeeq@FreeBSD.org"> shaun@FreeBSD.org"> sheldonh@FreeBSD.org"> shiba@FreeBSD.org"> shige@FreeBSD.org"> shin@FreeBSD.org"> shurd@FreeBSD.org"> silby@FreeBSD.org"> simokawa@FreeBSD.org"> simon@FreeBSD.org"> sjg@FreeBSD.org"> skozlov@FreeBSD.org"> skra@FreeBSD.org"> skreuzer@FreeBSD.org"> skv@FreeBSD.org"> slavash@FreeBSD.org"> slm@FreeBSD.org"> smace@FreeBSD.org"> smh@FreeBSD.org"> smkelly@FreeBSD.org"> smpatel@FreeBSD.org"> snb@FreeBSD.org"> sobomax@FreeBSD.org"> sos@FreeBSD.org"> sperber@FreeBSD.org"> sson@FreeBSD.org"> ssouhlal@FreeBSD.org"> adam@redprince.net"> stark@FreeBSD.org"> stas@FreeBSD.org"> stb@FreeBSD.org"> stefan@FreeBSD.org"> stefanf@FreeBSD.org"> stephane@FreeBSD.org"> stephen@FreeBSD.org"> steve@FreeBSD.org"> stevek@FreeBSD.org"> sumikawa@FreeBSD.org"> sunpoet@FreeBSD.org"> suz@FreeBSD.org"> swallace@FreeBSD.org"> swills@FreeBSD.org"> sylvio@FreeBSD.org"> syrinx@FreeBSD.org"> syuu@FreeBSD.org"> tabthorpe@FreeBSD.org"> tackerman@FreeBSD.org"> takawata@FreeBSD.org"> tanimura@FreeBSD.org"> taoka@FreeBSD.org"> taras@FreeBSD.org"> tcberner@FreeBSD.org"> tdb@FreeBSD.org"> tedm@FreeBSD.org"> tegge@FreeBSD.org"> tg@FreeBSD.org"> thepish@FreeBSD.org"> theraven@FreeBSD.org"> thierry@FreeBSD.org"> thj@FreeBSD.org"> thomas@FreeBSD.org"> thompsa@FreeBSD.org"> ticso@FreeBSD.org"> tijl@FreeBSD.org"> timur@FreeBSD.org"> tj@FreeBSD.org"> tjr@FreeBSD.org"> tmclaugh@FreeBSD.org"> tmm@FreeBSD.org"> tmseck@FreeBSD.org"> tmunro@FreeBSD.org"> tobez@FreeBSD.org"> tobik@FreeBSD.org"> tom@FreeBSD.org"> tomsoft@FreeBSD.org"> torstenb@FreeBSD.org"> toshi@FreeBSD.org"> tota@FreeBSD.org"> trasz@FreeBSD.org"> trevor@FreeBSD.org"> trhodes@FreeBSD.org"> trociny@FreeBSD.org"> truckman@FreeBSD.org"> tshiozak@FreeBSD.org"> tsoome@FreeBSD.org"> tuexen@FreeBSD.org"> tweten@FreeBSD.org"> twinterg@FreeBSD.org"> tychon@FreeBSD.org"> tz@FreeBSD.org"> uch@FreeBSD.org"> ue@FreeBSD.org"> ugen@FreeBSD.org"> uhclem@FreeBSD.org"> ulf@FreeBSD.org"> ultima@FreeBSD.org"> ume@FreeBSD.org"> unfurl@FreeBSD.org"> ups@FreeBSD.org"> uqs@FreeBSD.org"> vangyzen@FreeBSD.org"> vanhu@FreeBSD.org"> vanilla@FreeBSD.org"> vd@FreeBSD.org"> versus@FreeBSD.org"> vg@FreeBSD.org"> viny@FreeBSD.org"> vkashyap@FreeBSD.org"> vmaffione@FreeBSD.org"> vs@FreeBSD.org"> vsevolod@FreeBSD.org"> vwe@FreeBSD.org"> wblock@FreeBSD.org"> wen@FreeBSD.org"> weongyo@FreeBSD.org"> wes@FreeBSD.org"> wg@FreeBSD.org"> whiteside@acm.org"> whu@FreeBSD.org"> wilko@FreeBSD.org"> will@FreeBSD.org"> wjv@FreeBSD.org"> wkoszek@FreeBSD.org"> wma@FreeBSD.org"> wolf@FreeBSD.org"> wollman@FreeBSD.org"> woodsb02@FreeBSD.org"> wosch@FreeBSD.org"> wpaul@FreeBSD.org"> wsalamon@FreeBSD.org"> wsanchez@FreeBSD.org"> wulf@FreeBSD.org"> wxs@FreeBSD.org"> wylie@magnesium.net"> xmj@FreeBSD.org"> xride@FreeBSD.org"> yar@FreeBSD.org"> ygy@FreeBSD.org"> yoichi@FreeBSD.org"> yokota@FreeBSD.org"> yongari@FreeBSD.org"> yuri@FreeBSD.org"> yuripv@FreeBSD.org"> yzlin@FreeBSD.org"> zack@FreeBSD.org"> zarzycki@FreeBSD.org"> zbb@FreeBSD.org"> zec@FreeBSD.org"> zeising@FreeBSD.org"> zi@FreeBSD.org"> zleslie@FreeBSD.org"> zml@FreeBSD.org"> znerd@FreeBSD.org"> zont@FreeBSD.org"> kami@FreeBSD.org"> irc@FreeBSD.org"> - + keymaster@FreeBSD.org">