firefox port lacks ssl support?
Joe Marcus Clarke
marcus at marcuscom.com
Fri Jun 29 22:17:34 UTC 2007
On Fri, 2007-06-29 at 12:53 -0700, Jeff Roberson wrote:
> On Fri, 29 Jun 2007, Joe Marcus Clarke wrote:
> > On Fri, 2007-06-29 at 12:28 -0700, Jeff Roberson wrote:
> >> On Fri, 29 Jun 2007, Joe Marcus Clarke wrote:
> >>> On Fri, 2007-06-29 at 00:33 -0700, Jeff Roberson wrote:
> >>>> I recently updated my world and neither firefox or seamonkey support
> >>>> https. Is this a known problem?
> >>>> firefox-18.104.22.168,1 Web browser based on the browser portion of Mozilla
> >>>> seamonkey-1.1.2 The open source, standards compliant web browser
> >>>> Those are my ports versions.
> >>> Rebuild devel/nspr and security/nss, then rebuild Firefox.
> >> Thanks, should this go in the ports UPDATING?
> > We typically require people to use portupgrade, and keep their whole
> > ports tree up-to-date.
> I actually did that. Kris helped me with update with Xorg and I forced
> all new packages using portupgrade.
Then you shouldn't of seen this problem. There is really no magic to
the Firefox/nss integration (i.e. no special UPDATING steps are needed
to get the two to work together). As long as both are kept up-to-date,
HTTPS support should just work.
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20070629/5efbfaa9/attachment.pgp
More information about the freebsd-gnome