summaryrefslogtreecommitdiffstats
path: root/debian/browser.README.Debian.in
blob: 5359fe24e6ba3d366fed25fea4b96924ee9a58e7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
@Browser@ for Debian
====================

Please read the file /usr/share/bug/@browser@/presubj for information
you may want to know if you will report a bug.

Buttons
-------

Some people have complained that the button order in dialogs is
non-intuitive (ie, they don't like it). To reverse the order, add the
following to your chrome/userChrome.css file, under the
~/.mozilla/firefox directory:

.dialog-button-box { -moz-box-direction: reverse; -moz-box-pack: right; }
.dialog-button-box spacer { display: none ! important; }

Emacs keybindings
-----------------

Versions of Firefox before 1.0 supported Emacs style keybindings in
text entry boxes. Version 1.0 now merely follows the GTK keybindings
settings. To enable Emacs keybindings in GTK, follow the instructions
at http://kb.mozillazine.org/Emacs_Keybindings_(Firefox).

Well Known Ports
----------------

To prevent @Browser@ from being used to launch attacks against other
protocols, certain ports cannot be connected to by default. See
http://www.mozilla.org/projects/netlib/PortBanning.html for further
information. To allow the port numbers being used, enter
"about:config" in the URL bar and edit the
"network.security.ports.banned.override" entry to list the ports you
wish to allow (eg "2049,4045,6000").

Safe Browsing
-------------

Phishing and malware protection, also known as Safe Browsing, makes use
of a third party web service and regularly downloads updates. More
information on how this works and what is being sent and downloaded are
available on the following page:
http://www.mozilla.com/en-US/firefox/phishing-protection/

NTLM
----

Since version 30.0, NTLMv1 authentication has been disabled because
it's known as insecure. Companies and organizations still deploying
the older protocol should upgrade to NTLMv2, unfortunately, it's not
supported by @Browser@.
It is however still possible to toggle the preference to continue using
NTLMv1, though the NTLM auth support is considered deprecated, by
switching the network.negotiate-auth.allow-insecure-ntlm-v1 preference
in about:config.

See https://developer.mozilla.org/en-US/Firefox/Releases/30/Site_Compatibility#Security
for more details.

 -- Mike Hommey <glandium@debian.org>, Mon, 7 Mar 2016 07:42:57 +0200