Date: Fri, 29 Jun 2007 15:42:51 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Jeff Roberson <jroberson@chesapeake.net> Cc: gnome@freebsd.org Subject: Re: firefox port lacks ssl support? Message-ID: <1183146171.53232.29.camel@shumai.marcuscom.com> In-Reply-To: <20070629122704.O552@10.0.0.1> References: <20070629003214.E552@10.0.0.1> <1183133343.53232.0.camel@shumai.marcuscom.com> <20070629122704.O552@10.0.0.1>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-BkTkycWUCl7l76N/RgTa Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2007-06-29 at 12:28 -0700, Jeff Roberson wrote: > On Fri, 29 Jun 2007, Joe Marcus Clarke wrote: >=20 > > 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-2.0.0.4,1 Web browser based on the browser portion of Mozill= a > >> 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. >=20 > Thanks, should this go in the ports UPDATING? We typically require people to use portupgrade, and keep their whole ports tree up-to-date. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-BkTkycWUCl7l76N/RgTa Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGhWC5b2iPiv4Uz4cRAv/rAJ49jC/iTuJgBu9PogX+bO/oPkB4wgCdHm/g FKhmRk6OlFZqMYeQI9Qq0UM= =iDzH -----END PGP SIGNATURE----- --=-BkTkycWUCl7l76N/RgTa--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1183146171.53232.29.camel>