pkgsrc

Projects that follow the best practices below can voluntarily self-certify and show that they've achieved an Open Source Security Foundation (OpenSSF) best practices badge.

If this is your project, please show your badge status on your project page! The badge status looks like this: Badge level for project 112 is passing Here is how to embed it:

These are the Passing level criteria. You can also view the Silver or Gold level criteria.

        

 Basics 13/13

  • Identification

    Portable package manager

    What programming language(s) are used to implement the project?
  • Basic project website content


    The project website MUST succinctly describe what the software does (what problem does it solve?). [description_good]

    "portable package build system", near the logo.



    The project website MUST provide information on how to: obtain, provide feedback (as bug reports or enhancements), and contribute to the software. [interact]

    Mentions mailing list, IRC on the front page



    Habari juu ya jinsi ya kuchangia LAZIMA ieleze mchakato wa uchangiaji (kwa mfano, je! Maombi ya kuvuta yanatumika?) (URL required) [contribution]

    Chapter 21 of the pkgsrc guide: http://www.netbsd.org/docs/pkgsrc/submit.html "Submitting source packages (for non-NetBSD-developers)" mentions: - using the bug repository (send-PR) - the open access (after providing an SSH key) "work in progress" repository, which has a website with detailed instructions about how to receive commit access: http://pkgsrc.org/wip/users/



    Habari juu ya jinsi ya kuchangia INAPASWA kujumuisha mahitaji ya michango inayokubalika (k.m., rejeleo la kiwango chochote kinachohitajika cha usimbaji). (URL required) [contribution_requirements]

    Contributors are often referred to the pkgsrc guide, for example the following example exists for making a package: http://www.netbsd.org/docs/pkgsrc/examples.html


  • FLOSS license

    What license(s) is the project released under?



    The software produced by the project MUST be released as FLOSS. [floss_license]

    All of the pkgsrc infrastructure is released under various BSD licenses.



    It is SUGGESTED that any required license(s) for the software produced by the project be approved by the Open Source Initiative (OSI). [floss_license_osi]

    Most code is released under BSD license, but a small amount of it is still BSD 4 clause license.



    The project MUST post the license(s) of its results in a standard location in their source repository. (URL required) [license_location]
  • Documentation


    The project MUST provide basic documentation for the software produced by the project. [documentation_basics]

    the pkgsrc guide is extremely detailed. http://www.netbsd.org/docs/pkgsrc/



    The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project. [documentation_interface]
  • Other


    The project sites (website, repository, and download URLs) MUST support HTTPS using TLS. [sites_https]

    Download URL: https://ftp.netbsd.org/pub/pkgsrc/pkgsrc-2016Q1/ Project website: https://pkgsrc.org/ Repository is over CVS (thus SSH) or git



    The project MUST have one or more mechanisms for discussion (including proposed changes and issues) that are searchable, allow messages and topics to be addressed by URL, enable new people to participate in some of the discussions, and do not require client-side installation of proprietary software. [discussion]

    Mailing lists: pkgsrc-users (for users, suggested for new contributors too): http://mail-index.netbsd.org/pkgsrc-users/2016/04/thread1.html tech-pkg (very technical discussion of packaging problems): http://mail-index.netbsd.org/tech-pkg/2016/04/thread1.html



    The project SHOULD provide documentation in English and be able to accept bug reports and comments about code in English. [english]

    Every website to do with the project is in English.



    The project MUST be maintained. [maintained]


(Advanced) What other users have additional rights to edit this badge entry? Currently: []



Default package manager for several open source operating systems, including: NetBSD, SmartOS, MINIX3. It works very well on others, too: OS X, Linux, etc. Every file downloaded for building a package is checked against a SHA sum. Several built in tools allow auditing for security purposes. It optionally warns you about any known vulnerability when building a package, and provides a tool to check if there are any (even new) vulnerabilities in installed packages. This is the database of known package vulnerabilities: https://ftp.netbsd.org/pub/NetBSD/packages/vulns/pkg-vulnerabilities It doesn't allow packages that cannot be built exclusively from source code: even compilers such as Go are booted from C - first by building Go 1.4, then building the latest Go compiler using the booted Go 1.4 compiler.

  • Public version-controlled source repository


    The project MUST have a version-controlled source repository that is publicly readable and has a URL. [repo_public]

    The project's source repository MUST track what changes were made, who made the changes, and when the changes were made. [repo_track]

    Through CVS.



    To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases. [repo_interim]

    pkgsrc supports two branches: pkgsrc-current, which has the latest packages and uses a freeze period for extensive review (but is possible to review continuously) pkgsrc-stable, which is a release branch.



    It is SUGGESTED that common distributed version control software be used (e.g., git) for the project's source repository. [repo_distributed]

  • Unique version numbering


    The project results MUST have a unique version identifier for each release intended to be used by users. [version_unique]

    Quarterly releases are made. The current release is 2016Q1. It is not properly a "release", because security and significant bug fixes can be done, but stability must be preserved.



    It is SUGGESTED that the Semantic Versioning (SemVer) or Calendar Versioning (CalVer) version numbering format be used for releases. It is SUGGESTED that those who use CalVer include a micro level value. [version_semver]

    It is a package manager - the releases exist to avoid major instability-inducing changes. they are not properly a released version, but a branch which is guaranteed to only have minimal, required changes, such as security backports.



    It is SUGGESTED that projects identify each release within their version control system. For example, it is SUGGESTED that those using git identify each release using git tags. [version_tags]

    Releases are CVS branches. For example, it may be used with cvs ... -r2016Q1.


  • Release notes


    The project MUST provide, in each release, release notes that are a human-readable summary of major changes in that release to help users determine if they should upgrade and what the upgrade impact will be. The release notes MUST NOT be the raw output of a version control log (e.g., the "git log" command results are not release notes). Projects whose results are not intended for reuse in multiple locations (such as the software for a single website or service) AND employ continuous delivery MAY select "N/A". (URL required) [release_notes]

    It contains a doc/CHANGES-YEAR file. the latest, viewed from cvsweb, is the following: http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/pkgsrc/doc/CHANGES-2016?rev=1.1833&content-type=text/plain



    The release notes MUST identify every publicly known run-time vulnerability fixed in this release that already had a CVE assignment or similar when the release was created. This criterion may be marked as not applicable (N/A) if users typically cannot practically update the software themselves (e.g., as is often true for kernel updates). This criterion applies only to the project results, not to its dependencies. If there are no release notes or there have been no publicly known vulnerabilities, choose N/A. [release_notes_vulns]

    Rather than offer a singular list which must be viewed by a human, it offers extensive tools for checking for vulnerabilities. Upon install, the user can opt to disallow packages known to be vulnerable (ALLOW_VULNERABLE_PACKAGES=yes), or audit already installed packages using convenient tools: https://www.netbsd.org/docs/pkgsrc/using.html#vulnerabilities


  • Bug-reporting process


    The project MUST provide a process for users to submit bug reports (e.g., using an issue tracker or a mailing list). (URL required) [report_process]

    The project SHOULD use an issue tracker for tracking individual issues. [report_tracker]

    You may search the issue tracker here: http://www.netbsd.org/support/query-pr.html



    The project MUST acknowledge a majority of bug reports submitted in the last 2-12 months (inclusive); the response need not include a fix. [report_responses]

    While no link for statistics exist, it is uncommon for a bug report to be unacknowledged.



    The project SHOULD respond to a majority (>50%) of enhancement requests in the last 2-12 months (inclusive). [enhancement_responses]


    The project MUST have a publicly available archive for reports and responses for later searching. (URL required) [report_archive]

    You may search the issue tracker here: http://www.netbsd.org/support/query-pr.html Or the mailing lists of said issue tracker: http://mail-index.netbsd.org/pkgsrc-bugs/index.html


  • Vulnerability report process


    The project MUST publish the process for reporting vulnerabilities on the project site. (URL required) [vulnerability_report_process]

    It suggests contacting the pkgsrc-security team in the pkgsrc guide: http://www.netbsd.org/docs/pkgsrc/fixes.html#security-handling



    If private vulnerability reports are supported, the project MUST include how to send the information in a way that is kept private. (URL required) [vulnerability_report_private]

    Contacting pkgsrc-security is strongly recommended, and emails to this list are not public by default: http://www.netbsd.org/docs/pkgsrc/fixes.html#security-handling



    The project's initial response time for any vulnerability report received in the last 6 months MUST be less than or equal to 14 days. [vulnerability_report_response]

  • Working build system


    Ikiwa programu iliyotengenezwa na mradi inahitaji ujenzi wa matumizi, mradi LAZIMA utoe mfumo wa kujenga ambao unaweza kujenga programu kiotomatiki kutoka kwa chanzo-msimbo. [build]

    pkgsrc carries a bootstrap tool: cd pkgsrc/bootstrap && ./bootstrap it will build all the required tools from source code.



    INAPENDEKEZWA kuwa zana za kawaida zitumike kujenga programu. [build_common_tools]

    It uses mostly BSD makefiles. It contains any tools required for building packages.



    Mradi UNAPASWA kujengwa kwa kutumia zana za FLOSS pekee yake. [build_floss_tools]

  • Automated test suite


    The project MUST use at least one automated test suite that is publicly released as FLOSS (this test suite may be maintained as a separate FLOSS project). The project MUST clearly show or document how to run the test suite(s) (e.g., via a continuous integration (CI) script or via documentation in files such as BUILD.md, README.md, or CONTRIBUTING.md). [test]

    pkglint is the common tool for testing an individual package and is BSD-2 licensed, it is also a package hosted within pkgsrc. mass build tests can be done using bulkbuild, a BSD licensed package also hosted within pkgsrc.



    A test suite SHOULD be invocable in a standard way for that language. [test_invocation]

    typical invocation of pkglint: pkglint -Wall -Call.



    It is SUGGESTED that the test suite cover most (or ideally all) the code branches, input fields, and functionality. [test_most]


    It is SUGGESTED that the project implement continuous integration (where new or changed code is frequently integrated into a central code repository and automated tests are run on the result). [test_continuous_integration]

    raw bulk build test reports, on a mailing list archive: http://mail-index.netbsd.org/pkgsrc-bulk/2016/04/thread1.html


  • New functionality testing


    The project MUST have a general policy (formal or not) that as major new functionality is added to the software produced by the project, tests of that functionality should be added to an automated test suite. [test_policy]


    The project MUST have evidence that the test_policy for adding tests has been adhered to in the most recent major changes to the software produced by the project. [tests_are_added]

    Bulk build reports are publicly viewable on a mailing list archive: http://mail-index.netbsd.org/pkgsrc-bulk/2016/04/thread1.html



    It is SUGGESTED that this policy on adding tests (see test_policy) be documented in the instructions for change proposals. [tests_documented_added]

    The addition of pkgsrc infrastructure requiring additional tests is very rarely done, most of the work is on the packages themselves. Discussions of additional infrastructure are expected to take place in tech-pkg, but it is very infrequently done, so it is undocumented.


  • Warning flags


    The project MUST enable one or more compiler warning flags, a "safe" language mode, or use a separate "linter" tool to look for code quality errors or common simple mistakes, if there is at least one FLOSS tool that can implement this criterion in the selected language. [warnings]

    pkglint is used, and checks new packages for problems. it is a BSD-2 licensed project hosted within pkgsrc.



    The project MUST address warnings. [warnings_fixed]


    It is SUGGESTED that projects be maximally strict with warnings in the software produced by the project, where practical. [warnings_strict]

  • Secure development knowledge


    The project MUST have at least one primary developer who knows how to design secure software. (See ‘details’ for the exact requirements.) [know_secure_design]

    It has the pkgsrc-security team with several such members.



    At least one of the project's primary developers MUST know of common kinds of errors that lead to vulnerabilities in this kind of software, as well as at least one method to counter or mitigate each of them. [know_common_errors]

  • Use basic good cryptographic practices

    Note that some software does not need to use cryptographic mechanisms. If your project produces software that (1) includes, activates, or enables encryption functionality, and (2) might be released from the United States (US) to outside the US or to a non-US-citizen, you may be legally required to take a few extra steps. Typically this just involves sending an email. For more information, see the encryption section of Understanding Open Source Technology & US Export Controls.

    Programu iliyotengenezwa na mradi LAZIMA itumie, kwa chaguo-msingi, tu itifaki za kriptografia na mifumbo ambazo zimechapishwa hadharani na kukaguliwa na wataalam (ikiwa itifaki za kriptografia na mafumbo imetumika). [crypto_published]

    SHA-3



    Ikiwa programu iliyotengenezwa na mradi ni programu au maktaba, na kusudi lake la msingi sio kutekeleza usimbuaji, basi INAPASWA tu kuita programu iliyoundwa kihususa kutekeleza kazi za kielelezo; HAIPASWI kutekeleza-upya shughuli hiyo. [crypto_call]

    SHA-3 code that is BSD-licensed could not be found.



    Utendaji wote katika programu iliyotengenezwa na mradi ambayo inategemea usimbuaji LAZIMA iweze kutekelezwa kwa kutumia FLOSS. [crypto_floss]


    Mifumo ya usalama ndani ya programu inayozalishwa na mradi LAZIMA itumie kwa msingi keylengths ambazo angalau zinakidhi mahitaji ya chini ya NIST kufikia mwaka wa 2030 (kama ilivyoelezwa mnamo 2012). LAZIMA iwe rahisi kusanidi programu ili keylengths ndogo zimezimwa kabisa. [crypto_keylength]

    SHA-3 is used.



    The default security mechanisms within the software produced by the project MUST NOT depend on broken cryptographic algorithms (e.g., MD4, MD5, single DES, RC4, Dual_EC_DRBG), or use cipher modes that are inappropriate to the context, unless they are necessary to implement an interoperable protocol (where the protocol implemented is the most recent version of that standard broadly supported by the network ecosystem, that ecosystem requires the use of such an algorithm or mode, and that ecosystem does not offer any more secure alternative). The documentation MUST describe any relevant security risks and any known mitigations if these broken algorithms or modes are necessary for an interoperable protocol. [crypto_working]


    The default security mechanisms within the software produced by the project SHOULD NOT depend on cryptographic algorithms or modes with known serious weaknesses (e.g., the SHA-1 cryptographic hash algorithm or the CBC mode in SSH). [crypto_weaknesses]

    pkgsrc itself uses a SHA3 sum for online source code downloads.



    Mifumo ya usalama ndani ya programu iliyotengenezwa na mradi INAPASWA kutekeleza kwa ukamilifu usiri wa umbele ya itifaki za makubaliano ya funguo ili funguo la kipindi kilicho tokana na kikao cha vifungo muda-mrefu haziwezi kuridhi mabaya ikiwa mojawapo ya vifunguo vya muda-mrefu imeridhi mabaya katika usoni. [crypto_pfs]


    Ikiwa programu iliyotengenezwa na mradi imesababisha uhifadhi wa nywila kwa minajili ya uthibitishaji ya watumiaji wa kutoka nje, nywila LAZIMA zihifadhiwe kwa mficho uliorudiarudia na chumvi kwa kila-mtumiaji kwa kutumia kanuni ya upanuaji (rudiarudia) wa funguo (k.m., Argon2id, Bcrypt, Scrypt, or PBKDF2). Ona pia Kurasadogo ya Uhifadhi wa Nywila la OWASP). [crypto_password_storage]

    No passwords.



    Mifumo ya usalama ndani ya programu iliyotengenezwa na mradi LAZIMA itoe funguo zote za kriptologia na nonces kwa kutumia kitengeneza cha nambari za bahati kuptia kriptologia salama, na ISIWEZE kufanya hivo kutumia vitengenezi zisizo salama kikriptologia. [crypto_random]

  • Secured delivery against man-in-the-middle (MITM) attacks


    The project MUST use a delivery mechanism that counters MITM attacks. Using https or ssh+scp is acceptable. [delivery_mitm]

    CVS is done over SSH. source code downloads are checked against SHA3 sums, as the downloads are typically done from the original source, not a rehosted repository of source code, and not all packages use HTTPS, and even if they did, they could not be trusted to not have a security problem and change the source code for a package.



    A cryptographic hash (e.g., a sha1sum) MUST NOT be retrieved over http and used without checking for a cryptographic signature. [delivery_unsigned]

  • Publicly known vulnerabilities fixed


    There MUST be no unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days. [vulnerabilities_fixed_60_days]

    pkgsrc tools have no known vulnerabilities (they are extremely minimal). packages with vulnerabilities are patched when possible.



    Projects SHOULD fix all critical vulnerabilities rapidly after they are reported. [vulnerabilities_critical_fixed]

    pkgsrc infrastructure has no known vulnerabilities. some packages do and do not contain any fixes - when they do, they are updated.


  • Other security issues


    The public repositories MUST NOT leak a valid private credential (e.g., a working password or private key) that is intended to limit public access. [no_leaked_credentials]

    Private credentials are not used.


  • Static code analysis


    At least one static code analysis tool (beyond compiler warnings and "safe" language modes) MUST be applied to any proposed major production release of the software before its release, if there is at least one FLOSS tool that implements this criterion in the selected language. [static_analysis]

    It is a package manager using primarily makefiles, so only the pkgsrc tool pkglint can be reasonably used.



    It is SUGGESTED that at least one of the static analysis tools used for the static_analysis criterion include rules or approaches to look for common vulnerabilities in the analyzed language or environment. [static_analysis_common_vulnerabilities]

    Downloaded external files are checked against a SHA3 sum, but no further checks are possible.



    All medium and higher severity exploitable vulnerabilities discovered with static code analysis MUST be fixed in a timely way after they are confirmed. [static_analysis_fixed]

    pkglint should not be capable of discovering vulnerabilities except for MITM attacks (by a mismatched signature for downloaded files), which are tested at every use.



    It is SUGGESTED that static source code analysis occur on every commit or at least daily. [static_analysis_often]

    Contributors are strongly encouraged to use pkglint


  • Dynamic code analysis


    It is SUGGESTED that at least one dynamic analysis tool be applied to any proposed major production release of the software before its release. [dynamic_analysis]

    pkgsrc only contains the files required to build the packages. the packages themselves are expected to contain most of the vulnerabilities.



    It is SUGGESTED that if the software produced by the project includes software written using a memory-unsafe language (e.g., C or C++), then at least one dynamic tool (e.g., a fuzzer or web application scanner) be routinely used in combination with a mechanism to detect memory safety problems such as buffer overwrites. If the project does not produce software written in a memory-unsafe language, choose "not applicable" (N/A). [dynamic_analysis_unsafe]

    most of pkgsrc is the makefiles, which aren't normally tested for such things.



    It is SUGGESTED that the project use a configuration for at least some dynamic analysis (such as testing or fuzzing) which enables many assertions. In many cases these assertions should not be enabled in production builds. [dynamic_analysis_enable_assertions]


    All medium and higher severity exploitable vulnerabilities discovered with dynamic code analysis MUST be fixed in a timely way after they are confirmed. [dynamic_analysis_fixed]

    Typically no dynamic code analysis is done. however, any reports will be answered.



This data is available under the Creative Commons Attribution version 3.0 license (CC-BY-3.0) per the terms of use. All are free to share and adapt the data, but must give appropriate credit. Please credit Maya Rashish and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: Maya Rashish.
Entry created on 2016-05-04 21:27:53 UTC, last updated on 2016-06-29 23:49:16 UTC. Last achieved passing badge on 2016-06-29 23:49:00 UTC.

Back