![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / security / boringssl / patches
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.2, Tue Jul 7 23:47:41 2020 UTC (3 years, 9 months ago) by nia
Branch: MAIN
CVS Tags: HEAD
Changes since 1.1: +1 -1
lines
FILE REMOVED
security: Remove boringssl This is a really old version that is likely vulnerable. AFAIK the only consumer of boringssl is Chromium which vendors its own variant, otherwise the library is just for internal Google use
Revision 1.1.1.1 / (download) - annotate - [select for diffs] (vendor branch), Thu Dec 31 02:57:35 2015 UTC (8 years, 3 months ago) by agc
Branch: TNF
CVS Tags: pkgsrc-base,
pkgsrc-2020Q2-base,
pkgsrc-2020Q2,
pkgsrc-2020Q1-base,
pkgsrc-2020Q1,
pkgsrc-2019Q4-base,
pkgsrc-2019Q4,
pkgsrc-2019Q3-base,
pkgsrc-2019Q3,
pkgsrc-2019Q2-base,
pkgsrc-2019Q2,
pkgsrc-2019Q1-base,
pkgsrc-2019Q1,
pkgsrc-2018Q4-base,
pkgsrc-2018Q4,
pkgsrc-2018Q3-base,
pkgsrc-2018Q3,
pkgsrc-2018Q2-base,
pkgsrc-2018Q2,
pkgsrc-2018Q1-base,
pkgsrc-2018Q1,
pkgsrc-2017Q4-base,
pkgsrc-2017Q4,
pkgsrc-2017Q3-base,
pkgsrc-2017Q3,
pkgsrc-2017Q2-base,
pkgsrc-2017Q2,
pkgsrc-2017Q1-base,
pkgsrc-2017Q1,
pkgsrc-2016Q4-base,
pkgsrc-2016Q4,
pkgsrc-2016Q3-base,
pkgsrc-2016Q3,
pkgsrc-2016Q2-base,
pkgsrc-2016Q2,
pkgsrc-2016Q1-base,
pkgsrc-2016Q1
Changes since 1.1: +0 -0
lines
Diff to previous 1.1 (colored)
Import boringssl into the packages collection. This is a tar file of
the sources taken at 20151230 from
https://boringssl.googlesource.com/boringssl/
with portability fixes for NetBSD. It installs into ${PREFIX}/bssl to
avoid conflicts with openssl.
BoringSSL is a fork of OpenSSL that is designed to meet Google's
needs.
Although BoringSSL is an open source project, it is not intended for
general use, as OpenSSL is. We don't recommend that third parties
depend upon it. Doing so is likely to be frustrating because there
are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we
update everything as needed when deciding to make API changes. This
allows us to mostly avoid compromises in the name of compatibility.
It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various
ways and, over time, built up a large number of patches that were
maintained while tracking upstream OpenSSL. As Google's product
portfolio became more complex, more copies of OpenSSL sprung up and
the effort involved in maintaining all these patches in multiple
places was growing steadily.
Revision 1.1 / (download) - annotate - [select for diffs], Thu Dec 31 02:57:35 2015 UTC (8 years, 3 months ago) by agc
Branch: MAIN
Initial revision