Comments on: Secure your Browser against the Poodle Attack; SSL 3.0 is Dead

By: abbazabapress

abbazabapress — Fri, 07 Nov 2014 02:53:00 +0000

In reply to FleeWee. real activation, to get what you want by search @@@windows 8.1 key sale@@@ from bing.

By: FleeWee

FleeWee — Fri, 07 Nov 2014 01:03:00 +0000

That is a very cute poodle!

By: Dan

Dan — Wed, 29 Oct 2014 06:50:00 +0000

Thanks for this reminder! In return, here are three reminders about Firefox configurations which some have an interest in: first, re “about:config”, browser.display.use_document_fonts will always revert to a value of “1” every time the browser is closed/re-opened (those wishing to have Firefox blab about fewer fonts always have to reset the value to “0” as it doesn’t persist); second, browsersession.max_entries will always revert to a value of “50” every time FF is closed/re-opened (those wanting to have FF blab less about number of pages in tab history will have to reset the value to “2” every time they open FF…setting doesn’t persist); and finally, dom.storage.enabled has to be reset to “false” every time as this change too never persists, for those who don’t want dom storage. Thanks again, cheers!

By: Anand Khanse

Anand Khanse — Wed, 29 Oct 2014 03:59:00 +0000

In reply to Al Jenke. There are two dashes "-" before the ssl. But they are appearing merged in the text above. So I have added a new line which gives the full path after it is appended

By: Al Jenke

Al Jenke — Tue, 28 Oct 2014 22:53:00 +0000

Your procedure for setting in Google Chrome is INCORRECT and does NOT work !

This is correct procedure: “My understanding is that the user can configure SSL/TLS settings for Chrome browser from [Settings] -> [Change Proxy Settings] -> [Advanced].”