./security/boringssl, Fork of OpenSSL designed to meet Googles needs

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 20151230nb5, Package name: boringssl-20151230nb5, Maintainer: pkgsrc-users

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.


Required to build:
[lang/go] [pkgtools/cwrappers]

Master sites: (Expand)

SHA1: eb3681358044990bc54c9ab58a3ce8d951edd022
RMD160: cf2b15e5dc261efcba44cb493947e9c48d346c36
Filesize: 21469.242 KB

Version history: (Expand)


CVS history: (Expand)


   2016-12-21 14:38:16 by Joerg Sonnenberger | Files touched by this commit (2)
Log message:
"false" is spelled 0 when returning integers.
   2016-12-04 17:30:01 by Benny Siegert | Files touched by this commit (35) | Package updated
Log message:
Revbump Go packages after 1.7.4 update.
   2016-10-29 10:59:49 by Benny Siegert | Files touched by this commit (34) | Package updated
Log message:
Revbump packages depending on Go after the Go 1.7.3 update.
   2016-09-10 21:47:21 by Benny Siegert | Files touched by this commit (30) | Package updated
Log message:
Revbump all Go packages after the Go 1.7.1 update.
   2016-07-09 08:39:18 by Thomas Klausner | Files touched by this commit (1068) | Package updated
Log message:
Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.
   2016-02-23 21:18:13 by Benny Siegert | Files touched by this commit (17) | Package updated
Log message:
Revbump packages that build-depend on Go after 1.6 update.

They all build, I checked :)
   2016-01-05 20:47:12 by Alistair G. Crooks | Files touched by this commit (1)
Log message:
Make sure we have a version of go on the machine on which we're
building boringssl.
   2015-12-31 03:57:35 by Alistair G. Crooks | Files touched by this commit (10) | Imported package
Log message:
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.