core/nss to 3.48-1

core/nss/PKGBUILD

@@ -7,8 +7,8 @@
 
 pkgbase=nss
 pkgname=(nss ca-certificates-mozilla)
-pkgver=3.47.1
-pkgrel=5
+pkgver=3.48
+pkgrel=1
 pkgdesc="Network Security Services"
 url="https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS"
 arch=(x86_64)
@@ -20,8 +20,8 @@ source=("https://ftp.mozilla.org/pub/security/nss/releases/NSS_${pkgver//./_}_RT
         nss-3.47-certdb-temp-cert.patch
         certdata2pem.py bundle.sh
         0001-Remove-ARM-AES-from-freebl-gyp.patch)
-sha256sums=('1ae3d1cb1de345b258788f2ef6b10a460068034c3fd64f42427a183d8342a6fb'
-            'e4d7c7d6ac8c8cccd5bb23c217402922aafc1c104e46ae17a39f3c13b0e96002'
+sha256sums=('3f9c822a86a4e3e1bfe63e2ed0f922d8b7c2e0b7cafe36774b1c627970d0f8ac'
+            'bd16ba87e5ea736888f76dd54dff18b25ca6608245c0195fb85bad3d782db73c'
             '0be02cecc27a6e55e1cad1783033b147f502b26f9fb1bb5a53e7a43bbcb68fa0'
             '3bfadf722da6773bdabdd25bdf78158648043d1b7e57615574f189a88ca865dd'
             '8372d34fdeeebd23e1daa7ee1f67510f050cba30c884f81e067dba46f94d1dcf')

core/nss/nss-3.47-certdb-temp-cert.patch

@@ -1,10 +1,8 @@
-# HG changeset patch
-# User Daiki Ueno <dueno@redhat.com>
-# Date 1575450841 -3600
-#      Wed Dec 04 10:14:01 2019 +0100
-# Node ID 017097f0a0eaea1a3d849f3de79475c9bc28fcc2
-# Parent  d64102b76a437f24d98a20480dcc9f1655143e7c
-Bug 1593167, certdb: propagate trust information if trust module is loaded afterwards
+From 9530978d1552674792e281391100269305a38c47 Mon Sep 17 00:00:00 2001
+From: Daiki Ueno <dueno@redhat.com>
+Date: Fri, 6 Dec 2019 10:47:01 +0100
+Subject: [PATCH] Bug 1593167, certdb: propagate trust information if trust
+ module is loaded afterwards, r=rrelyea,keeler
 
 Summary:
 When the builtin trust module is loaded after some temp certs being created, these temp certs are usually not accompanied by trust information. This causes a problem in Firefox as it loads the module from a separate thread while accessing the network cache which populates temp certs.
@@ -13,18 +11,22 @@ This change makes it properly roll up the trust information, if a temp cert does
 
 Reviewers: rrelyea, keeler
 
-Reviewed By: rrelyea
+Reviewed By: rrelyea, keeler
 
 Subscribers: reviewbot, heftig
 
 Bug #: 1593167
 
 Differential Revision: https://phabricator.services.mozilla.com/D54726
+---
+ lib/pki/pki3hack.c | 30 ++++++++++++++++++++++--------
+ 1 file changed, 22 insertions(+), 8 deletions(-)
 
 diff --git a/lib/pki/pki3hack.c b/lib/pki/pki3hack.c
+index 29d2fb5a40..eac4a5705e 100644
 --- a/lib/pki/pki3hack.c
 +++ b/lib/pki/pki3hack.c
-@@ -921,14 +921,28 @@ stan_GetCERTCertificate(NSSCertificate *
+@@ -921,14 +921,28 @@ stan_GetCERTCertificate(NSSCertificate *c, PRBool forceUpdate)
      }
      if (!cc->nssCertificate || forceUpdate) {
          fill_CERTCertificateFields(c, cc, forceUpdate);
@@ -61,3 +63,6 @@ diff --git a/lib/pki/pki3hack.c b/lib/pki/pki3hack.c
  
          CERT_LockCertTrust(cc);
          cc->trust = trust;
+-- 
+2.24.0
+