| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Now that the cert sideband thread is gone, threading can be removed.
Making GTK calls across multiple threads is also deprecated in newer
GTK versions and is severly broken on Windows, so there's no point in
keeping this around.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes the side channel for getting and verifying remote HTTPS
certificates. As the http_proxy settings only affected messages
downloaded as part of the webkit soup session, this side channel would
create its own TCP connections which sidesteped the proxy, leaving a
privacy leak.
For simplicity, the remote certificate chain is now saved in pem
format as part of the tab structure, and converted to a gnutls
certificate chain when needed for viewing and displaying certs.
Most of the initial code done by dhill@ and marco@
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Based on initial patch from Tim Meunier <trondd@gmail.com>).
Add temporary files to .gitignore.
|
| |
|
| |
|
|
|
|
|
| |
This fixes issues when installing to a clean path such as with
package creation.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
requested by many
|
| |
|
|
|
|
|
|
|
| |
This prevents displaying any extra whitespace between the comma and
the url in the alias definition from being displayed in the statusbar.
Found by Cody Write (writecode on Flyspray)
|
|
|
|
| |
Found by Cody Write (writecode on flyspray)
|
| |
|
| |
|
|
|
|
| |
From cody on irc
|
|
|
|
| |
From cody on irc
|
|
|
|
| |
Patch from cody in irc
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change introduces a new RB tree to keep track of identities
(defined as being different combinations of modified HTTP headers, so
far only User-Agent and Accept). Whenever a site is visited, this
tree is checked to see if it has been accessed before, and if it has,
the previously used Accept and User-Agent headers will be used. If
the site has not been visited before during the browser's lifetime, a
new entry will be created in this tree to keep track of which headers
to use the next time. A site is defined as a FQDN, so requests made
to cross site resources or resources on a different subdomain will
generate a new saved identity.
The second change adds two new config files to the resource dir to
read in additional user_agent and http_accept values scraped from the
logs of www.bitrig.org. The idea of this is to keep rotating through
each of these on every new site visit to provide more anonymity and
thwart web tracking by looking at the headers being sent.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This modifies the whitelist and https forcing code to internally use
unix extended regular expressions to match domains. The old config
syntax converted to an appropiate regular expression. Inputing of raw
regular expressions is possible by prepending the string "re:" in
front of a regular expression, for example:
js_wl = re:^(.*\.)*cyphertite\.com$
would be the same as
js_wl = .cyphertite.com
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This changes the order custom and invalid URI checking so that items
set with custom_uri are still able to be handled properly, even if the
URI scheme is invalid (not whitelisted) and we don't want xombrero
opening it.
|
|
|
|
| |
Reported by Thomas in the irc channel
|
| |
|
|
|
|
| |
Patch from user Zplay on the forum
|
|
|
|
|
|
|
|
|
| |
This change makes the can_go_* and go_* back/forward functions use the
same logic when determining whether we are on an about page, and makes
it so about:secviolation warning pages do not save the page that
generated the warning to t->item. This prevents hitting back and
going back to the exact same page that generated the warning
(triggering the warning a second time).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This should incorporate all the fixes in my previous back/forward list
change, but still uses marco's horrible hack for determining if and
how back/forward works. Code is still ugly but deal with it.
Any remaining issues will be worked out in-tree.
|
|
|
|
|
|
| |
This changed worked wonders for me but others still saw some problems.
I could not reproduce any of them. This will bring back some problems
with refresh not working again, but I'll work around that next.
|
| |
|
| |
|