Public SourceMage Discussion List

["Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org>]

On Jul 19, Arwed von Merkatz [v.merkatz AT gmx.net] wrote:
> On Mon, Jul 18, 2005 at 08:11:29PM -0500, Jeremy Blosser (emrys) wrote:
> > On Jul 18, David Brown [dmlb2000 AT gmail.com] wrote:
> > > This is a reminder for any bug fixes/reports about atable-rc to be put
> > > on the wiki
> > > http://wiki.sourcemage.org/index.php?page=Stable0.1Notes
> > 
> > I added http://bugs.sourcemage.org/show_bug.cgi?id=9208 under "major
> > issues".  sandalle and alley_cat have both indicated they think this is
> > important; alley_cat I believe said firefox was "unusable" as it currently
> > is.
> 
> Can't say much about firefox as I don't use that one, but mozilla/galeon
> is very annoying. Unusable might have been an exagerration, but getting
> swamped with several "Trust this site?" messages when you go to
> sourceforge through https (it loads the ads by https from other servers
> apparently) just leads to me ignoring those messages completely and just
> giving every site trust so I can actually do some browsing. Not really
> what certificates and https are for ;)
> 
> > > Hopefully we'll be integrating the stable-rc to stable and make it
> > > official in a couple of days so if anyone has objections or fixes better
> > > get them in soon.
> > 
> > Sergey said today he's working on this bug, but if it's not ready in time,
> > maybe we could roll back the nss changes so the security version bump 
> > makes
> > it anyway.
> 
> I'd prefer if it could be fixed, but rolling back mozilla and firefox
> would be a possibility otherwise.

Well, I just found something sort of interesting.  It looks like the certs
end up in the file libnssckbi.so when NSS builds.  Firefox used to have
this file at /usr/lib/firefox/libnssckbi.so, but now it's just there as the
NSS copy at /usr/lib/libnssckbi.so.  However, the NSS copy still appears to
have the certs.

If I do 'ln -s /usr/lib/libnssckbi.so /usr/lib/firefox/.', I get a copy of
firefox that has all the root certs and appears to work like it should.
So, we apparently still have the certs, we just have to make the browsers
use them.  I don't know if this ln is the way to do that, or if the "right
way" is something else.

Arwed, can you see if you see something similar for mozilla/galeon?

Attachment: pgpSjREvGHNGw.pgp
Description: PGP signature