Re: Updated plans for NSPR: merge into NSS
Kai Engert <[email protected]> Thu, 16 Apr 2026 16:36:10 +0200
| Newsgroups | gmane.comp.mozilla.crypto |
|---|---|
| Message-ID | <[email protected]> |
--------------QNj2XA8j5SqlXU7vzevWEaZ6 Sig: t=p; b= wnsEABYIACMWIQTbU6PYxn9IFjJ1R6JpevsbNyK8BAUCaeDz2gUDAAAAAAAKCRBpevsbNyK8BByH AQC2MqaAR2PcFJic7VTuFnlXqLuFnSoOf1qPBx7i6zP62wD9GqlJ8UrhrqSS1PXqeaFWHhUe1z1w uzpz/frU3HD/rwI= Message-ID: <[email protected]> Date: Thu, 16 Apr 2026 16:36:10 +0200 MIME-Version: 1.0 User-Agent: Thunderbird Daily Subject: Re: [dev-tech-crypto] Updated plans for NSPR: merge into NSS Content-Language: en-US From: Kai Engert <[email protected]> To: Robert Relyea <[email protected]>, [email protected] References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> Autocrypt: [email protected]; keydata= xsFNBE8oE/UBEAC/Vx4tHVkfPdGf0BFMGcidXzAXKQ4+gI2F5rPBoV9fEtYngLHzm7+a6DL2 v5Jl5b4by9KtUbfIJysR1iniLWMJVPXZcyC4ovGouZ4MGK5cD9kMy+JdwebCs5/tj51vcvrS 08dP7r9Q0f0H7tsqhtVWuPFt+ZZEj8fIxjMgE3Z5BcyoGT1mXQ544RA0vr0fB9MngvfteD3L /wL2miDnYVtwB+VHC6kEB75Pte/yz1kFc/TDqKT8F45M3invhccY8Zwe7F88+uS+tgR5B3Ga RMc9WChZr5ed5vRxSLrGqBGSWBKomKuWXNFVMrZAOaq+W/+kOdNSXLdJSvXIAgV4Gywf1D0r ZTi8V+UoiTY8eDfT4OlBJrbbkge92/lrqaorAsuo/DVmfv7ARk7q2jvbSZD39zkWpLNsAulz gZOr+ffEHKy0f9fNwzenHpKvNtTUWGChEyDf7a6EtTBZsxAYco0xAtFOoQVwx5UzZk4tMVhv lrATrvmFdK5SLroDuwtSLUBJ5MhICyaB1kN7YSatQs33D+M5oPKVC+mn1WB/nznU475cssBW Asw+/K4VtXN08HxVFEvpV5MtpoYGe/cqsV87aVr/Igg45DVKtMMK8W5AmJDdGru3caxdVkkW fis9F1GBkk7ZPgip4cprh3KicuKsXhVrjk2mC/kCR+mrlY8ncQARAQABzRlLYWkgRW5nZXJ0 IDxLYWlFQGt1aXguZGU+wsGXBBMBCABBAhsDBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheAAhkB FiEEIdFuZ+GDmMjand8uHCdCNyUAdyQFAmm9Kt8FCRzF/OsACgkQHCdCNyUAdyQkjw/9GdUH bmB9+tTLMpnr5rmJkIqZ8pXQQXEi/pKENGSNzaGHSeXAIptGH7DWKa3DfGHR3TsaREz9RiW9 vK7jQBzPUZpx4Jne5vpNEpe0U0vjxRpehO6tjn0MIsxa4dlwk3+VZG7CJuOCbyDHLhmz+uTn MpaZB96mtLtBcNA5vjroR0mcuc1K9CPaD6+RfUHgoE0/AJGnhdH4WbwCAZ3iMEAqkPXSqifJ 7R8257wbYdigbKXybdu5qHc0t4EjnPAfYE5Q+2SIYS2F/Y9wJhBdZDak3fiiLFhNBGK/yiWT IRarP+lqCSUDQ7wYJuh0J9HrblraiFWErPI2OI9fS0Pd19U8jwb6jdz4maGNz8UUs+JOxKzL AZ7voNZvno4tci7mRBOVPtisD0m3Kh93sF7JVYjp2SYUZFgP2BIbaHDLWgKONrn87VmQrNVn z7fLvFvg372A8wNaXUZMcDmduTxco5EHI0+O3TKdK6uor9opydONcrpfm1JaN+Fp4diWhgUc qaT5R2UHzcGHHztiayfJlm+UvSVO3P68iTZI9i07MWkXdQu65N57OgWLGNB/5S5ms+gm0lSV D3Ph6q0X9ZV3hFc5cDiDUyMofMFyJWk7bC4CqZxvOBabkmVErYb2wvUYLwmR99xqQxvQ+7hZ XqbSHhZhs93KR1JsHhkdIjSO5A/SgQDOOARmQ8MuEgorBgEEAZdVAQUBAQdAc9UYbulbMQUm 5xftvu1VkBrFWKTLmD4udR62yP2IfzkDAQgHwsF8BBgBCAAmAhsMFiEEIdFuZ+GDmMjand8u HCdCNyUAdyQFAmm9KvYFCQWqTbIACgkQHCdCNyUAdyRvJw//SHoUu7H+GxnXFtIAhW0nlES6 QHgpd1BQV014ueG3HxqXhdHEz2wqsdP0qnqUOn7uWH0+MR2BF5h4DCWfYhHnNDliZGq7Sug3 I5a7AuLFZZTTv4O1GE2jwbwnFS+4mZiMdz0XayHMB2FjeSInOiuIfBf//20utFPwzLPaXQdR qPRJ51DU1HhRNs8H0Wh3sSkrtfFQvIzLuqoDzvpXInh1t9Brq1nDbdEYJTnu2kVgDaNbFG16 DN/phEOTTOZKLbbE97mIzc9wizNJTT3TjLHu7CKeFKfLyc3usEVR0QiyOqtvlnPlKj+sMgR3 egStlen7ipre7lug+W/QBY4hK4+S0C9rkAMOiWUMJytJZK9gDoQv8ubeeAdo4SLaMd2VzD2k bIPNk5RKQjprWhe+CivNBZdooQNZ06NTzaIvHNlbspI+e2UF5zKJuMlVou+ulnq5lUiqW+R3 IjqszzokTUmoDXoUbt+a+q5PYD/ijkznGWhi+OE/4+mWMnx8JVEaPm2Kttoyy+CS/5Dt6Acn 8FjxlxaMAm6aFota+Y53X81cS7oixz8sLgg5D8JBHV3D+P1iyrgiZRbD5+LtCED1jh2Xjs24 rj9eXJn/AZG7ixR9D1ijhbG7ZjOtrWes7LipBueYZkoLew7drDNHKEFKSGFvbaatyQdb7sIt v57v8GkeKAs= In-Reply-To: <[email protected]> Content-Type: text/plain; charset="UTF-8"; format=flowed; hp=clear Note my previous message was an attempt to help in thinking about options for your needs. From our perspective, I think the intention is to no longer make promises about NSPR/MPR APIs remaining available. Brainstorming again about your needs, maybe it would be more practical for you if you took to opposite approach? You could decide that you keep maintaining the old NSPR libraries, as long as you need them, and backport upstream MPR fixes to it, if necessary. And instead of having a shim from NSPR to MPR, maybe you need it the other way round? Don't use MPR as distributed with NSS, but rather use a shim MPR library that maps the new symbol names to the old NSPR symbols? I think the dilemma here is that the Firefox team would like to be more flexible and make changes more easily, which isn't easy to align with your needs for long term stability. Kai -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/b53d860f-a62d-4107-a52e-ff938c732bfb%40kuix.de. --------------QNj2XA8j5SqlXU7vzevWEaZ6--