Groups > linux.debian.user > #201435

Re: basilisk-browser

From	Roberto C. Sánchez <roberto@debian.org>
Newsgroups	linux.debian.user
Subject	Re: basilisk-browser
Date	2018-10-19 15:40 +0200
Message-ID	<wKDap-3k6-9@gated-at.bofh.it> (permalink)
References	(2 earlier) <wKcjU-3Na-9@gated-at.bofh.it> <wKq3v-3WX-1@gated-at.bofh.it> <wKwBY-7Sd-17@gated-at.bofh.it> <wKwVj-7Yp-3@gated-at.bofh.it> <wKzgu-13U-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, Oct 19, 2018 at 12:28:16PM +0300, Reco wrote:
> 
> Ridiculous or not, but stable's firefox-esr contains their own private
> version of NSS - [1]. Same for the thunderbird.
> But they try to keep it sane, so at least firefox does not embed
> 'correct' version of GTK3, for example.
> 

That is very frustrating because there was a time when those
Mozilla-related packages used the system libnss.  Modifying the system
libnss to include an additional cetificate authority was the closest I
could get to deploying an internal CA within a network of Debian
machines (similar to how a Windows admin can push a CA to a bunch of
Windows machines via GPO).

However, they switched to bundled libnss at some point and my choices
became either rebuild each Mozilla-related package (FF, TB, etc.) or
have users manually install the CA.  Rebuilding those packages wasn't
worth the trouble.

It is really frustrating as this is one of those nagging inconveniences
(the lack of a standardized system-wide certificate store that is
actually used by all applications) of Linux that seems like it really
should have been resolved by now.

Regards,

-Roberto
-- 
Roberto C. Sánchez

Thread

basilisk-browser basti <mailinglist@unix-solution.de> - 2018-10-18 09:40 +0200
  Re: basilisk-browser <tomas@tuxteam.de> - 2018-10-18 10:10 +0200
    Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-18 11:00 +0200
      Re: basilisk-browser <tomas@tuxteam.de> - 2018-10-18 11:20 +0200
        Re: basilisk-browser Roberto C. Sánchez <roberto@debian.org> - 2018-10-18 14:50 +0200
          Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-18 16:40 +0200
            Re: basilisk-browser basti <mailinglist@unix-solution.de> - 2018-10-18 17:00 +0200
              Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-18 17:10 +0200
        Re: basilisk-browser John Crawley <john@bunsenlabs.org> - 2018-10-19 03:00 +0200
      Re: basilisk-browser Doug <dmcgarrett@optonline.net> - 2018-10-19 01:40 +0200
        Re: basilisk-browser Ben Finney <bignose@debian.org> - 2018-10-19 06:30 +0200
          Re: basilisk-browser Gene Heskett <gheskett@shentel.net> - 2018-10-19 12:40 +0200
        Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-19 08:40 +0200
          Re: basilisk-browser Dominik George <natureshadow@debian.org> - 2018-10-19 09:00 +0200
            Re: basilisk-browser mick crane <mick.crane@gmail.com> - 2018-10-19 09:30 +0200
              Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-19 12:30 +0200
                Re: basilisk-browser mick crane <mick.crane@gmail.com> - 2018-10-19 13:10 +0200
              Re: basilisk-browser Gene Heskett <gheskett@shentel.net> - 2018-10-19 12:50 +0200
            Re: basilisk-browser Reco <recoverym4n@enotuniq.net> - 2018-10-19 11:30 +0200
              Re: basilisk-browser Roberto C. Sánchez <roberto@debian.org> - 2018-10-19 15:40 +0200
            Re: basilisk-browser Ben Finney <bignose@debian.org> - 2018-10-20 04:20 +0200
              Re: basilisk-browser fmneto@fmneto.com.br - 2018-10-20 05:00 +0200
                Re: basilisk-browser Roberto C. Sánchez <roberto@debian.org> - 2018-10-20 14:00 +0200

csiph-web