couchbase 4.4.0 → 4.4.1-dev.1

package/deps/couchbase-cxx-cache/mozilla-ca-bundle.crt

@@ -1,7 +1,7 @@
 ##
 ## Bundle of CA Root Certificates
 ##
-## Certificate data from Mozilla as of: Mon Mar 11 15:25:27 2024 GMT
+## Certificate data from Mozilla as of: Tue Jul  2 03:12:04 2024 GMT
 ##
 ## This is a bundle of X.509 certificates of public Certificate Authorities
 ## (CA). These were automatically extracted from Mozilla's root certificates
@@ -14,7 +14,7 @@
 ## Just configure this file as the SSLCACertificateFile.
 ##
 ## Conversion done with mk-ca-bundle.pl version 1.29.
-## SHA256: 4d96bd539f4719e9ace493757afbe4a23ee8579de1c97fbebc50bba3c12e8c1e
+## SHA256: 456ff095dde6dd73354c5c28c73d9c06f53b61a803963414cb91a1d92945cdd3
 ##
 
 
@@ -2600,36 +2600,6 @@ vLtoURMMA/cVi4RguYv/Uo7njLwcAjA8+RHUjE7AwWHCFUyqqx0LMV87HOIAl0Qx5v5zli/altP+
 CAezNIm8BZ/3Hobui3A=
 -----END CERTIFICATE-----
 
-GLOBALTRUST 2020
-================
------BEGIN CERTIFICATE-----
-MIIFgjCCA2qgAwIBAgILWku9WvtPilv6ZeUwDQYJKoZIhvcNAQELBQAwTTELMAkGA1UEBhMCQVQx
-IzAhBgNVBAoTGmUtY29tbWVyY2UgbW9uaXRvcmluZyBHbWJIMRkwFwYDVQQDExBHTE9CQUxUUlVT
-VCAyMDIwMB4XDTIwMDIxMDAwMDAwMFoXDTQwMDYxMDAwMDAwMFowTTELMAkGA1UEBhMCQVQxIzAh
-BgNVBAoTGmUtY29tbWVyY2UgbW9uaXRvcmluZyBHbWJIMRkwFwYDVQQDExBHTE9CQUxUUlVTVCAy
-MDIwMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAri5WrRsc7/aVj6B3GyvTY4+ETUWi
-D59bRatZe1E0+eyLinjF3WuvvcTfk0Uev5E4C64OFudBc/jbu9G4UeDLgztzOG53ig9ZYybNpyrO
-VPu44sB8R85gfD+yc/LAGbaKkoc1DZAoouQVBGM+uq/ufF7MpotQsjj3QWPKzv9pj2gOlTblzLmM
-CcpL3TGQlsjMH/1WljTbjhzqLL6FLmPdqqmV0/0plRPwyJiT2S0WR5ARg6I6IqIoV6Lr/sCMKKCm
-fecqQjuCgGOlYx8ZzHyyZqjC0203b+J+BlHZRYQfEs4kUmSFC0iAToexIiIwquuuvuAC4EDosEKA
-A1GqtH6qRNdDYfOiaxaJSaSjpCuKAsR49GiKweR6NrFvG5Ybd0mN1MkGco/PU+PcF4UgStyYJ9OR
-JitHHmkHr96i5OTUawuzXnzUJIBHKWk7buis/UDr2O1xcSvy6Fgd60GXIsUf1DnQJ4+H4xj04KlG
-DfV0OoIu0G4skaMxXDtG6nsEEFZegB31pWXogvziB4xiRfUg3kZwhqG8k9MedKZssCz3AwyIDMvU
-clOGvGBG85hqwvG/Q/lwIHfKN0F5VVJjjVsSn8VoxIidrPIwq7ejMZdnrY8XD2zHc+0klGvIg5rQ
-mjdJBKuxFshsSUktq6HQjJLyQUp5ISXbY9e2nKd+Qmn7OmMCAwEAAaNjMGEwDwYDVR0TAQH/BAUw
-AwEB/zAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFNwuH9FhN3nkq9XVsxJxaD1qaJwiMB8GA1Ud
-IwQYMBaAFNwuH9FhN3nkq9XVsxJxaD1qaJwiMA0GCSqGSIb3DQEBCwUAA4ICAQCR8EICaEDuw2jA
-VC/f7GLDw56KoDEoqoOOpFaWEhCGVrqXctJUMHytGdUdaG/7FELYjQ7ztdGl4wJCXtzoRlgHNQIw
-4Lx0SsFDKv/bGtCwr2zD/cuz9X9tAy5ZVp0tLTWMstZDFyySCstd6IwPS3BD0IL/qMy/pJTAvoe9
-iuOTe8aPmxadJ2W8esVCgmxcB9CpwYhgROmYhRZf+I/KARDOJcP5YBugxZfD0yyIMaK9MOzQ0MAS
-8cE54+X1+NZK3TTN+2/BT+MAi1bikvcoskJ3ciNnxz8RFbLEAwW+uxF7Cr+obuf/WEPPm2eggAe2
-HcqtbepBEX4tdJP7wry+UUTF72glJ4DjyKDUEuzZpTcdN3y0kcra1LGWge9oXHYQSa9+pTeAsRxS
-vTOBTI/53WXZFM2KJVj04sWDpQmQ1GwUY7VA3+vA/MRYfg0UFodUJ25W5HCEuGwyEn6CMUO+1918
-oa2u1qsgEu8KwxCMSZY13At1XrFP1U80DhEgB3VDRemjEdqso5nCtnkn4rnvyOL2NSl6dPrFf4IF
-YqYK6miyeUcGbvJXqBUzxvd4Sj1Ce2t+/vdG6tHrju+IaFvowdlxfv1k7/9nR4hYJS8+hge9+6jl
-gqispdNpQ80xiEmEU5LAsTkbOYMBMMTyqfrQA71yN2BWHzZ8vTmR9W0Nv3vXkg==
------END CERTIFICATE-----
-
 ANF Secure Server Root CA
 =========================
 -----BEGIN CERTIFICATE-----
@@ -3579,3 +3549,20 @@ wPfc5+pbrrLMtTWGS9DiP7bY+A4A7l3j941Y/8+LN+ljX273CXE2whJdV/LItM3z7gLfEdxquVeE
 HVlNjM7IDiPCtyaaEBRx/pOyiriA8A4QntOoUAw3gi/q4Iqd4Sw5/7W0cwDk90imc6y/st53BIe0
 o82bNSQ3+pCTE4FCxpgmdTdmQRCsu/WU48IxK63nI1bMNSWSs1A=
 -----END CERTIFICATE-----
+
+FIRMAPROFESIONAL CA ROOT-A WEB
+==============================
+-----BEGIN CERTIFICATE-----
+MIICejCCAgCgAwIBAgIQMZch7a+JQn81QYehZ1ZMbTAKBggqhkjOPQQDAzBuMQswCQYDVQQGEwJF
+UzEcMBoGA1UECgwTRmlybWFwcm9mZXNpb25hbCBTQTEYMBYGA1UEYQwPVkFURVMtQTYyNjM0MDY4
+MScwJQYDVQQDDB5GSVJNQVBST0ZFU0lPTkFMIENBIFJPT1QtQSBXRUIwHhcNMjIwNDA2MDkwMTM2
+WhcNNDcwMzMxMDkwMTM2WjBuMQswCQYDVQQGEwJFUzEcMBoGA1UECgwTRmlybWFwcm9mZXNpb25h
+bCBTQTEYMBYGA1UEYQwPVkFURVMtQTYyNjM0MDY4MScwJQYDVQQDDB5GSVJNQVBST0ZFU0lPTkFM
+IENBIFJPT1QtQSBXRUIwdjAQBgcqhkjOPQIBBgUrgQQAIgNiAARHU+osEaR3xyrq89Zfe9MEkVz6
+iMYiuYMQYneEMy3pA4jU4DP37XcsSmDq5G+tbbT4TIqk5B/K6k84Si6CcyvHZpsKjECcfIr28jlg
+st7L7Ljkb+qbXbdTkBgyVcUgt5SjYzBhMA8GA1UdEwEB/wQFMAMBAf8wHwYDVR0jBBgwFoAUk+FD
+Y1w8ndYn81LsF7Kpryz3dvgwHQYDVR0OBBYEFJPhQ2NcPJ3WJ/NS7Beyqa8s93b4MA4GA1UdDwEB
+/wQEAwIBBjAKBggqhkjOPQQDAwNoADBlAjAdfKR7w4l1M+E7qUW/Runpod3JIha3RxEL2Jq68cgL
+cFBTApFwhVmpHqTm6iMxoAACMQD94vizrxa5HnPEluPBMBnYfubDl94cT7iJLzPrSA8Z94dGXSaQ
+pYXFuXqUPoeovQA=
+-----END CERTIFICATE-----

package/deps/couchbase-cxx-cache/mozilla-ca-bundle.sha256

@@ -1 +1 @@
-1794c1d4f7055b7d02c2170337b61b48a2ef6c90d77e95444fd2596f4cac609f  cacert.pem
+1bf458412568e134a4514f5e170a328d11091e071c7110955c9884ed87972ac9  cacert.pem

package/package.json

@@ -54,7 +54,7 @@
     "type": "git",
     "url": "http://github.com/couchbase/couchnode.git"
   },
-  "version": "4.4.0",
+  "version": "4.4.1-dev.1",
   "config": {
     "native": false
   },
@@ -79,12 +79,13 @@
     ]
   },
   "optionalDependencies": {
-    "@couchbase/couchbase-darwin-arm64-napi": "4.4.0",
-    "@couchbase/couchbase-darwin-x64-napi": "4.4.0",
-    "@couchbase/couchbase-linux-arm64-napi": "4.4.0",
-    "@couchbase/couchbase-linuxmusl-x64-napi": "4.4.0",
-    "@couchbase/couchbase-linux-x64-napi": "4.4.0",
-    "@couchbase/couchbase-win32-x64-napi": "4.4.0"
+    "@couchbase/couchbase-darwin-arm64-napi": "4.4.1-dev.1",
+    "@couchbase/couchbase-darwin-x64-napi": "4.4.1-dev.1",
+    "@couchbase/couchbase-linux-arm64-napi": "4.4.1-dev.1",
+    "@couchbase/couchbase-linuxmusl-arm64-napi": "4.4.1-dev.1",
+    "@couchbase/couchbase-linuxmusl-x64-napi": "4.4.1-dev.1",
+    "@couchbase/couchbase-linux-x64-napi": "4.4.1-dev.1",
+    "@couchbase/couchbase-win32-x64-napi": "4.4.1-dev.1"
   },
   "files": [
     "LICENSE",

package/deps/couchbase-cxx-cache/asio/41f31469d0dd420500b334dc8c2fd3ffe7320d8e/asio/asio/COPYING

@@ -1,4 +0,0 @@
-Copyright (c) 2003-2023 Christopher M. Kohlhoff (chris at kohlhoff dot com)
-
-Distributed under the Boost Software License, Version 1.0. (See accompanying
-file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)

package/deps/couchbase-cxx-cache/asio/41f31469d0dd420500b334dc8c2fd3ffe7320d8e/asio/asio/README

@@ -1,4 +0,0 @@
-asio version 1.29.0
-Released Thursday, 09 November 2023.
-
-See doc/index.html for API documentation and a tutorial.

package/deps/couchbase-cxx-cache/boringssl/e31ea00c1ea52052d2d78d44006cc88c80fa24a9/boringssl/src/crypto/obj/README

@@ -1,15 +0,0 @@
-The files nid.h, obj_mac.num, and obj_dat.h are generated from objects.txt and
-obj_mac.num. To regenerate them, run:
-
-    go run objects.go
-
-objects.txt contains the list of all built-in OIDs. It is processed by
-objects.go to output obj_mac.num, obj_dat.h, and nid.h.
-
-obj_mac.num is the list of NID values for each OID. This is an input/output
-file so NID values are stable across regenerations.
-
-nid.h is the header which defines macros for all the built-in OIDs in C.
-
-obj_dat.h contains the ASN1_OBJECTs corresponding to built-in OIDs themselves
-along with lookup tables for search by short name, OID, etc.

package/deps/couchbase-cxx-cache/boringssl/e31ea00c1ea52052d2d78d44006cc88c80fa24a9/boringssl/src/crypto/perlasm/readme

@@ -1,100 +0,0 @@
-The perl scripts in this directory are my 'hack' to generate
-multiple different assembler formats via the one origional script.
-
-The way to use this library is to start with adding the path to this directory
-and then include it.
-
-push(@INC,"perlasm","../../perlasm");
-require "x86asm.pl";
-
-The first thing we do is setup the file and type of assembler
-
-&asm_init($ARGV[0]);
-
-The first argument is the 'type'.  Currently
-'cpp', 'sol', 'a.out', 'elf' or 'win32'.
-Argument 2 is the file name.
-
-The reciprocal function is
-&asm_finish() which should be called at the end.
-
-There are 2 main 'packages'. x86ms.pl, which is the Microsoft assembler,
-and x86unix.pl which is the unix (gas) version.
-
-Functions of interest are:
-&external_label("des_SPtrans");	declare and external variable
-&LB(reg);			Low byte for a register
-&HB(reg);			High byte for a register
-&BP(off,base,index,scale)	Byte pointer addressing
-&DWP(off,base,index,scale)	Word pointer addressing
-&stack_push(num)		Basically a 'sub esp, num*4' with extra
-&stack_pop(num)			inverse of stack_push
-&function_begin(name,extra)	Start a function with pushing of
-				edi, esi, ebx and ebp.  extra is extra win32
-				external info that may be required.
-&function_begin_B(name,extra)	Same as normal function_begin but no pushing.
-&function_end(name)		Call at end of function.
-&function_end_A(name)		Standard pop and ret, for use inside functions
-&function_end_B(name)		Call at end but with poping or 'ret'.
-&swtmp(num)			Address on stack temp word.
-&wparam(num)			Parameter number num, that was push
-				in C convention.  This all works over pushes
-				and pops.
-&comment("hello there")		Put in a comment.
-&label("loop")			Refer to a label, normally a jmp target.
-&set_label("loop")		Set a label at this point.
-&data_word(word)		Put in a word of data.
-
-So how does this all hold together?  Given
-
-int calc(int len, int *data)
-	{
-	int i,j=0;
-
-	for (i=0; i<len; i++)
-		{
-		j+=other(data[i]);
-		}
-	}
-
-So a very simple version of this function could be coded as
-
-	push(@INC,"perlasm","../../perlasm");
-	require "x86asm.pl";
-	
-	&asm_init($ARGV[0]);
-
-	&external_label("other");
-
-	$tmp1=	"eax";
-	$j=	"edi";
-	$data=	"esi";
-	$i=	"ebp";
-
-	&comment("a simple function");
-	&function_begin("calc");
-	&mov(	$data,		&wparam(1)); # data
-	&xor(	$j,		$j);
-	&xor(	$i,		$i);
-
-	&set_label("loop");
-	&cmp(	$i,		&wparam(0));
-	&jge(	&label("end"));
-
-	&mov(	$tmp1,		&DWP(0,$data,$i,4));
-	&push(	$tmp1);
-	&call(	"other");
-	&add(	$j,		"eax");
-	&pop(	$tmp1);
-	&inc(	$i);
-	&jmp(	&label("loop"));
-
-	&set_label("end");
-	&mov(	"eax",		$j);
-
-	&function_end("calc");
-
-	&asm_finish();
-
-The above example is very very unoptimised but gives an idea of how
-things work.

package/deps/couchbase-cxx-cache/boringssl/e31ea00c1ea52052d2d78d44006cc88c80fa24a9/boringssl/src/pki/testdata/nist-pkits/README.chromium

@@ -1,19 +0,0 @@
-Name: NIST Public Key Interoperability Test Suite
-Short Name: NIST PKITS
-URL: http://csrc.nist.gov/groups/ST/crypto_apps_infra/pki/pkitesting.html
-Version: 1.0.1
-Date: April 14, 2011
-License: Public Domain: United States Government Work under 17 U.S.C. 105
-Shipped: no
-
-Description:
-The Public Key Interoperability Test Suite (PKITS) is a comprehensive X.509
-path validation test suite that was developed by NIST in conjunction with BAE
-Systems and NSA.  The PKITS path validation test suite is designed to cover
-most of the features specified in X.509 and RFC 3280.
-
-Local Modifications:
-Only the certs/ and crls/ directories were extracted from PKITS_data.zip.
-
-pkits_testcases-inl.h is generated from the test descriptions in PKITS.pdf
-using generate_tests.py.

package/deps/couchbase-cxx-cache/boringssl/e31ea00c1ea52052d2d78d44006cc88c80fa24a9/boringssl/src/pki/testdata/ssl/certificates/README

@@ -1,318 +0,0 @@
-This directory contains various certificates for use with SSL-related
-unit tests.
-
-===== Real-world certificates that need manual updating
-- google.binary.p7b
-- google.chain.pem
-- google.pem_cert.p7b
-- google.pem_pkcs7.p7b
-- google.pkcs7.p7b
-- google.single.der
-- google.single.pem : Certificates for testing parsing of different formats.
-
-- mit.davidben.der : An expired MIT client certificate.
-
-- foaf.me.chromium-test-cert.der : A client certificate for a FOAF.ME identity
-     created for testing.
-
-- google_diginotar.pem
-- diginotar_public_ca_2025.pem : A certificate chain for the regression test
-      of http://crbug.com/94673
-
-- salesforce_com_test.pem
-- verisign_intermediate_ca_2011.pem
-- verisign_intermediate_ca_2016.pem : Certificates for testing two
-     X509Certificate objects that contain the same server certificate but
-     different intermediate CA certificates.  The two intermediate CA
-     certificates actually represent the same intermediate CA but have
-     different validity periods.
-
-- ndn.ca.crt: "New Dream Network Certificate Authority" root certificate.
-     This is an X.509 v1 certificate that omits the version field. Used to
-     test that the certificate version gets the default value v1.
-
-- ct-test-embedded-cert.pem
-- ct-test-embedded-with-intermediate-chain.pem
-- ct-test-embedded-with-intermediate-preca-chain.pem
-- ct-test-embedded-with-preca-chain.pem
-     Test certificate chains for Certificate Transparency: Each of these
-     files contains a leaf certificate as the first certificate, which has
-     embedded SCTs, followed by the issuer certificates chain.
-     All files are from the src/test/testdada directory in
-     https://code.google.com/p/certificate-transparency/
-
-- leaf_from_known_root.pem : A certificate issued by a public trust anchor,
-     used for CertVerifyProcInternalTest.TestKnownRoot. Using for other
-     purposes is not recommended. This needs to be updated periodically so the
-     server name the cert is valid for may change.
-
-- lets-encrypt-dst-x3-root.pem: A chain that ends in the Lets encrypt DST X3
-  root (https://crt.sh/?id=8395). Has the same leaf as
-  lets-encrypt-isrg-x1-root.pem.
-- lets-encrypt-isrg-x1-root.pem: A chain that ends in the Lets encrypt ISRG X1
-  root (https://crt.sh/?id=9314791). Has the same leaf as
-  lets-encrypt-dst-x3-root.pem.
-
-===== Manually generated certificates
-- client.p12 : A PKCS #12 file containing a client certificate and a private
-     key created for testing.  The password is "12345".
-
-- client-nokey.p12 : A PKCS #12 file containing a client certificate (the same
-     as the one in client.p12) but no private key. The password is "12345".
-
-- client-empty-password.p12 : A PKCS #12 file containing an unencrypted client
-     certificate and a encrypted private key.  The password is the empty string,
-     encoded as two zero bytes.  (PKCS#12 passwords are encoded as
-     NUL-terminated UTF-16.)
-
-- client-null-password.p12 : A PKCS #12 file containing an unencrypted client
-     certificate and a encrypted private key.  The password is the empty string,
-     encoded as the empty byte string.
-
-- unittest.selfsigned.der : A self-signed certificate generated using private
-     key in unittest.key.bin. The common name is "unittest".
-
-- unittest.key.bin : private key stored unencrypted.
-
-- multivalue_rdn.pem : A regression test for http://crbug.com/101009. A
-     certificate with all of the AttributeTypeAndValues stored within a single
-     RelativeDistinguishedName, rather than one AVA per RDN as normally seen.
-
-- unescaped.pem : Regression test for http://crbug.com/102839. Contains
-     characters such as '=' and '"' that would normally be escaped when
-     converting a subject/issuer name to their stringized form.
-
-- websocket_cacert.pem : The testing root CA for testing WebSocket client
-     certificate authentication.
-     This file is used in SSLUITest.TestWSSClientCert.
-
-- websocket_client_cert.p12 : A PKCS #12 file containing a client certificate
-     and a private key created for WebSocket testing. The password is "".
-     This file is used in SSLUITest.TestWSSClientCert.
-
-- no_subject_common_name_cert.pem: Used to test the function that generates a
-  NSS certificate nickname for a user certificate. This certificate's Subject
-  field doesn't have a common name.
-
-- ct-test-embedded-with-uids.pem: A certificate with embedded SCT and
-  issuer/subject unique IDs. This certificate should only be used in parsing
-  tests and otherwise kept fixed. The signature, etc., are intentionally
-  invalid.
-
-- name_constrained_key.pem
-  The private key matching the public_key_hash of the kDomainsTest constraint
-  in CertVerifyProc::HasNameConstraintsViolation.
-
-===== From net/data/ssl/scripts/generate-quic-chain.sh
-- quic-chain.pem
-- quic-leaf-cert.key
-- quic-leaf-cert.key.pkcs8.pem
-- quic-root.pem
-     These certificates are used by integration tests that use QUIC.
-
-- quic-leaf-cert.key.sct
-     This isn't generated and just contains a simple text file (the contents
-     don't actually matter, just the presence of the file).
-
-===== From net/data/ssl/scripts/generate-test-certs.sh
-- expired_cert.pem
-- ok_cert.pem
-- root_ca_cert.pem
-    These certificates are the common certificates used by the Python test
-    server for simulating HTTPS connections.
-
-- intermediate_ca_cert.pem
-- ok_cert_by_intermediate.pem
-    These certificates simulate a more common chain of root (root_ca_cert.pem)
-    to intermediate (intermediate_ca_cert.pem) to leaf
-    (ok_cert_by_intermediate.pem).
-
-- wildcard_.pem
-    A certificate and private key valid for *.example.org, used in various
-    net unit tests.
-
-- test_names.pem
-    A certificate and private key valid for a number of test names. See
-    [test_names] in ee.cnf. Other names may be added as needed.
-
-- bad_validity.pem
-    A certificate and private key only valid on 0001-01-01. Windows refuses to
-    parse this certificate.
-
-- spdy_pooling.pem : Used to test the handling of spdy IP connection pooling
-
-- subjectAltName_sanity_check.pem : Used to test the handling of various types
-     within the subjectAltName extension of a certificate.
-
-- policies_sanity_check.pem : Used to test the parsing of various types of
-     certificatePolicies extension policyQualifiers.
-
-- punycodetest.pem : A test self-signed server certificate with punycode name.
-     The common name is "xn--wgv71a119e.com" (日本語.com)
-
-- sha1_2016.pem
-    Used to test the handling of SHA1 certificates expiring in 2016.
-
-- 10_year_validity.pem
-- 11_year_validity.pem
-- 39_months_after_2015_04.pem
-- 40_months_after_2015_04.pem
-- 60_months_after_2012_07.pem
-- 61_months_after_2012_07.pem
-- pre_br_validity_bad_121.pem
-- pre_br_validity_bad_2020.pem
-- pre_br_validity_ok.pem
-- start_after_expiry.pem
-    Certs to test that the maximum validity durations set by the CA/Browser
-    Forum Baseline Requirements are enforced.
-
-- pre_june_2016.pem
-- post_june_2016.pem
-- dec_2017.pem
-   Certs to test that policies related to enforcing CT on Symantec are
-   properly gated on the issuance date. See
-   https://g.co/chrome/symantecpkicerts. (Note, however, that the leaf and
-   root do not actually form a chain.)
-
-- may_2018.pem
-   An 825-day certificate issued on May 1, 2018, the official start of
-   enforcement requiring Certificate Transparency for new certificates. This
-   certificate does not have any embedded SCTs.
-
-- x509_verify_results.chain.pem : A simple certificate chain used to test that
-    the correctly ordered, filtered certificate chain is returned during
-    verification, regardless of the order in which the intermediate/root CA
-    certificates are provided.
-
-- ev_test.pem
-- ev_test_state_only.pem
-     Certificates for testing EV display (including regression test for
-     https://crbug.com/1069113).
-
-===== From net/data/ssl/scripts/generate-test-keys.sh
-- rsa-{768,1024,2048}-{1..3}.key
-- ec-prime256v1-{1..3}.key
-     Pre-generated keys of various types/sizes.
-     Useful for tests that generate RSA certificates with CertBuilder without
-     having to pay the cost of generating RSA keys at runtime. Multiple keys
-     of each size are provided. (EC keys are cheap to generate at runtime, but
-     having some as files simplifies test logic in cases where the test is
-     reading both RSA and EC keys from files.)
-
-===== From net/data/ssl/scripts/generate-redundant-test-chains.sh
-- redundant-validated-chain.pem
-- redundant-server-chain.pem
-- redundant-validated-chain-root.pem
-
-     Two chains, A -> B -> C -> D and A -> B -> C2 (C and C2 share the same
-     public key) to test that SSLInfo gets the reconstructed, re-ordered
-     chain instead of the chain as served. See
-     SSLClientSocketTest.VerifyReturnChainProperlyOrdered in
-     net/socket/ssl_client_socket_unittest.cc. These chains are valid until
-     26 Feb 2022 and are generated by
-     net/data/ssl/scripts/generate-redundant-test-chains.sh.
-
-===== From net/data/ssl/scripts/generate-client-certificates.sh
-- client_1.pem
-- client_1.key
-- client_1.pk8
-- client_1_ca.pem
-- client_2.pem
-- client_2.key
-- client_2.pk8
-- client_2_ca.pem
-- client_3.pem
-- client_3.key
-- client_3.pk8
-- client_3_ca.pem
-- client_4.pem
-- client_4.key
-- client_4.pk8
-- client_4_ca.pem
-- client_5.pem
-- client_5.key
-- client_5.pk8
-- client_5_ca.pem
-- client_6.pem
-- client_6.key
-- client_6.pk8
-- client_6_ca.pem
-- client_root_ca.pem
-     This is a set of files used to unit test SSL client certificate
-     authentication.
-     - client_1_ca.pem and client_2_ca.pem are the certificates of
-       two distinct signing CAs.
-     - client_1.pem and client_1.key correspond to the certificate and
-       private key for a first certificate signed by client_1_ca.pem.
-     - client_2.pem and client_2.key correspond to the certificate and
-       private key for a second certificate signed by client_2_ca.pem.
-     - each .pk8 file contains the same key as the corresponding .key file
-       as PKCS#8 PrivateKeyInfo in DER encoding.
-     - client_3.pem is nearly identical to client_2.pem, except it is used
-       to test wifi EAP-TLS authentication so it uses a different set
-       of X509v3 extensions.  Specifically it includes two Subject
-       Alternative Name fields recognized by Chrome OS.
-     - client_4.pem is similar to client_2.pem but is a P-256 ECDSA key rather
-       than RSA.
-     - client_5.pem is similar to client_2.pem but is a P-384 ECDSA key rather
-       than RSA.
-     - client_6.pem is similar to client_2.pem but is a P-521 ECDSA key rather
-       than RSA.
-     - client_root_ca.pem is the CA certificate which signed client_*_ca.pem.
-
-===== From net/data/ssl/scripts/generate-bad-eku-certs.sh
-- eku-test-root.pem
-- non-crit-codeSigning-chain.pem
-- crit-codeSigning-chain.pem
-     Two code-signing certificates (eKU: codeSigning; eKU: critical,
-     codeSigning) which we use to test that clients are making sure that web
-     server certs are checked for correct eKU fields (when an eKU field is
-     present). Since codeSigning is not valid for web server auth, the checks
-     should fail.
-
-===== From net/data/ssl/scripts/generate-multi-root-test-chains.sh
-- multi-root-chain1.pem
-- multi-root-chain2.pem
-     Two chains, A -> B -> C -> D and A -> B -> C2 -> E (C and C2 share the
-     same public key) to test that certificate validation caching does not
-     interfere with the chain_verify_callback used by CertVerifyProcChromeOS.
-     See CertVerifyProcChromeOSTest.
-
-===== From net/data/ssl/scripts/generate-multi-root-keychain.sh
-- multi-root.keychain: An OSX Keychain containing the generated
-  certificates multi-root-*-by-*.pem
-
-===== From net/data/ssl/scripts/generate-duplicate-cn-certs.sh
-- duplicate_cn_1.p12
-- duplicate_cn_1.pem
-- duplicate_cn_2.p12
-- duplicate_cn_2.pem
-     Two certificates from the same issuer that share the same common name,
-     but have distinct subject names (namely, their O fields differ). NSS
-     requires that certificates have unique nicknames if they do not share the
-     same subject, and these certificates are used to test that the nickname
-     generation algorithm generates unique nicknames.
-     The .pem versions contain just the certs, while the .p12 versions contain
-     both the cert and a private key, since there are multiple ways to import
-     certificates into NSS.
-
-===== From net/data/ssl/scripts/generate-self-signed-certs.sh
-- self-signed-invalid-name.pem
-- self-signed-invalid-sig.pem
-     Two "self-signed" certificates with mismatched names or an invalid
-     signature, respectively.
-
-===== From net/data/ssl/scripts/generate-key-usage-certs.sh
-- key_usage_rsa_no_extension.pem
-- key_usage_rsa_keyencipherment.pem
-- key_usage_rsa_digitalsignature.pem
-- key_usage_rsa_both.pem
-     Self-signed RSA certificates with various combinations of keyUsage
-     flags. Their private key is key_usage_rsa.key.
-
-- key_usage_p256_no_extension.pem
-- key_usage_p256_keyagreement.pem
-- key_usage_p256_digitalsignature.pem
-- key_usage_p256_both.pem
-     Self-signed P-256 certificates with various combinations of keyUsage
-     flags. Their private key is key_usage_p256.key.

package/deps/couchbase-cxx-cache/boringssl/e31ea00c1ea52052d2d78d44006cc88c80fa24a9/boringssl/src/pki/testdata/verify_certificate_chain_unittest/README

@@ -1,87 +0,0 @@
-This directory contains test data for verifying certificate chains.
-
-Tests are grouped into directories that contain the keys, python to generate
-chains, and test expectations. "DIR" is used as a generic placeholder below to
-identify such a directory.
-
-===============================
-DIR/generate-chains.py
-===============================
-
-Python script that generates one or more ".pem" file containing a sequence of
-CERTIFICATE blocks. In most cases it will generate a single chain called
-"chain.pem".
-
-===============================
-DIR/keys/*.key
-===============================
-
-The keys used (as well as generated) by the .py file generate-chains.py. The
-private keys shouldn't be needed to run the tests, however are useful when
-re-generating the test data to have stable results (at least for signature
-types which are deterministic, like RSASSA PKCS#1 which is used by most of the
-certificates data).
-
-===============================
-DIR/*.pem
-===============================
-
-A sequence of CERTIFICATE blocks that was created by the generate-chains.py
-script. (Although in a few cases there are manually created .pem files that
-lack a generator script).
-
-===============================
-DIR/*.test
-===============================
-
-A sequence of key-value pairs that identify the inputs to certificate
-verification, as well as the expected outputs. The format is essentially a
-newline separated sequence of key/value pairs:
-
-key: value\n
-
-All keys must be specified by tests, although they can be in any order.
-The possible keys are:
-
-  "chain" - The value is a file path (relative to the test file) to a .pem
-      containing the CERTIFICATE chain.
-
-  "last_cert_trust" - The value identifies the trustedness of the last
-      certificate in the chain (i.e. whether it is a trust anchor or not). This
-      maps to the CertificateTrustType enum. Possible values are:
-          "TRUSTED_ANCHOR"
-          "TRUSTED_ANCHOR_WITH_EXPIRATION"
-          "TRUSTED_ANCHOR_WITH_CONSTRAINTS"
-          "UNSPECIFIED"
-          "DISTRUSTED"
-
-  "utc_time" - A string encoding for the generalized time at which verification
-      should be done. Example "150302120000Z"
-
-  "key_purpose" - The expected EKU to use when verifying. Maps to
-      KeyPurpose enum. Possible values are:
-      "ANY_EKU"
-      "SERVER_AUTH"
-      "CLIENT_AUTH"
-
-  "errors" - This has special parsing rules: it is interpreted as the
-      final key in the file. All lines after "errors:\n" are read as being the
-      error string (this allows embedding newlines in it).
-
-Additionally, it is possible to add python-style comments by starting a line
-with "#".
-
-===============================
-pkits_errors/*.txt
-===============================
-
-These files contain the expected errors for PKITS tests
-(third_party/nist-pkits). The file name correspond so the PKITS tests number.
-They are baselined specifically for VerifyCertificateChain().
-
-===============================
-generate-all.sh
-===============================
-
-Runs all of the generate-chains.py scripts and cleans up the temp files
-afterwards.

package/deps/couchbase-cxx-cache/boringssl/e31ea00c1ea52052d2d78d44006cc88c80fa24a9/boringssl/src/pki/testdata/verify_signed_data_unittest/README

@@ -1,35 +0,0 @@
-This directory contains test data for testing net::VerifySignedData().
-
-When adding or changing test data, run the script
-  $ python annotate_test_data.py
-
-This script will apply a uniform formatting. For instance it will add a
-comment showing what the parsed ASN.1 looks like, and reformat the base64 to
-have consistent line breaks.
-
-The general format for the test files is as follows:
-
-
-  <A description of the test>
-
-  -----BEGIN PUBLIC KEY-----
-  <base64-encoded, DER-encoded, SPKI>
-  -----END PUBLIC KEY-----
-
-  -----BEGIN ALGORITHM-----
-  <base64-encoded, DER-encoded, AlgorithmIdentifier for the signature.>
-  -----END ALGORITHM-----
-
-  -----BEGIN DATA-----
-  <base64-encoded data that is being verified>
-  -----END DATA-----
-
-  -----BEGIN SIGNATURE-----
-  <base64-encoded, DER-encoded, BIT STRING of the signature>
-  -----END SIGNATURE-----
-
-
-Comments for a PEM block should be placed immediately below that block.
-The script will also insert a comment after the block describing its parsed
-ASN.1 structure (your extra comments need to be above the script-generated
-comments or they will be stripped).

package/deps/couchbase-cxx-cache/boringssl/e31ea00c1ea52052d2d78d44006cc88c80fa24a9/boringssl/src/third_party/fiat/README.chromium

@@ -1,11 +0,0 @@
-Name: Fiat-Crypto: Synthesizing Correct-by-Construction Code for Cryptographic Primitives
-Short Name: fiat-crypto
-URL: https://github.com/mit-plv/fiat-crypto
-Version: git (see METADATA)
-License: MIT
-License File: LICENSE
-Security Critical: yes
-Shipped: yes
-
-Description:
-See README.md and METADATA.

package/deps/couchbase-cxx-cache/boringssl/e31ea00c1ea52052d2d78d44006cc88c80fa24a9/boringssl/src/util/bot/README

@@ -1,3 +0,0 @@
-This directory contains tools for setting up a hermetic toolchain on the
-continuous integration bots. It is in the repository for convenience and can be
-ignored in development.

package/deps/couchbase-cxx-cache/fmt/d3c862243fcf1c41b4c09903f35479bd42f135b7/fmt/support/README

@@ -1,4 +0,0 @@
-This directory contains build support files such as
-
-* CMake modules
-* Build scripts