On 161218-02:04-0500, Walter Dnes wrote: > > How come people are so little interested to read the traffic, to learn > > how sites behave which they visit, and often to discover what sites > > really do to them? > > > > I'll go and inquire at the Pale Moon forum about the issues above, and > > will post there this exact question above, I think. > > This is a very obscure topic. Maybe nobody who knows about it read > that post. I only read 3 sub-forums... > > * Announcements... for new versions, etc > * Pale Moon for Linux... because I run the linux version > * Contributed builds... I do an SSE-only contributed 32-bit build. It > is useful for older Pentium 3 class machines, which will not run the > regular Pale Moon build. > > I couldn't find anything about NSS logging on Google... except your Why the Schmoog engine? duckduckgo.com is some much more privacy acceptable... But there are links too in the page that I posted the patch, below... > question. I followed the instructions in your post here, and that's how > I got it to work. I did not know about it until you told me. If Palemoon logs SSL-keys, then it must use some of openssl, libressl, gnutls, or the Mozilla/Google/Oracle (IIRC), but primary Mozilla program Network Security Services, dev-libs/nss-3.27.2 . > > Wait... Did you need to patch the nss library to get the $SSLKEYLOGFILE > > being written to? Like in this bug: > > > > >=dev-libs/nss-3.24 - Add USE flag to enable SSL key logging > > https://bugs.gentoo.org/show_bug.cgi?id=587116 https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.24_release_notes#Notable_changes_in_NSS_3.24 https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Reference/NSS_environment_variables (from that Bugzilla page) > > > > Did you? (That's about the only patch there, that I submitted to > > Bugzilla anywhere ;-) btw.) > > No patches required to the source code for that. Probably that means what it meant in some of the Mozilla pages... That's not good. Because it means the SSL-key logging is enabled by default. Was in Firefox too. Not, it need to be at user's decision, compile time only possible in Firefox, in optimize ebuilds, with my (minuscule) patch... But in binary releases, it is enabled by default in Firefox... > I do my own custom > manual build, to eliminate the dependancy on dbus, plus other tweaks. > That involves setting options in the mozconfig file, but no source code > changes. If you want to do your own build, see my post on December 9th > https://forum.palemoon.org/viewtopic.php?f=37&t=13898&start=20#p100625 > Note; this is version 2 of my build environment. You should see an > attached file "pmmain.tgz" on that post. Do not use version 1, with > (utils.tgz) in the first post of that thread. You know why the no-dbus way above may be my only way of doing it? Or for which reason I might have to give up? The only way, because after: $ git clone https://github.com/deuiore/palemoon-overlay I grep'd a log of dbus lines in that repo :-( , so Palemoon has the dbus dependency... Firefox does not. And not only in Gentoo. (And I don't intend to install no poetterware whatsoever --dbus being at least a relative, or maybe better defined as the precursor, which prepared the way for poetterware, IMO.) And that also may prove to be the reason that I might have to give up. Which I will only do if it shows to be too difficult for me. I've only just downloaded: https://forum.palemoon.org/download/file.php?id=6761 from: https://forum.palemoon.org/viewtopic.php?f=37&t=13898&start=20#p100625 so I don't yet know... We'll see... > -- > Walter Dnes > I don't run "desktop environments"; I run useful applications > Thanks also to Martin Vaeth for his correcting of my assumption. Regards! -- Miroslav Rovis Zagreb, Croatia http://www.CroatiaFidelis.hr