Age | Commit message (Collapse) | Author |
|
The macro hides a return path and makes it more difficult to read the
condition as it is negated.
|
|
|
|
The website is now at https://dillo-browser.github.io/ and the
repository at https://github.com/dillo-browser/dillo.
|
|
|
|
|
|
Before OpenSSL 3.0, the EVP_PKEY_get_id() was named EVP_PKEY_id().
|
|
The SSLv23_client_method() function is deprecated:
https://www.openssl.org/docs/man3.2/man3/SSLv23_client_method.html
|
|
Brings the previous OpenSSL implementation into src/IO/tls_openssl.c.
Now, the TLS functions have the implementation name as prefix, like
a_Tls_openssl_connect().
The generic interface at IO/tls.h hides the implementation which is
selected at configure time. The appropriate functions of that
implementation are called from IO/tls.c to IO/tls_<impl>.c. In this way,
support for more TLS libraries can easily be added.
In the case of mbedTLS, there are some incompatible changes from version
2 to 3, so we use some ifdefs to fix the differences.
|
|
|
|
When using the mouse wheel to scroll a page, the default scroll step was
causing a very slow scrolling speed. The new option "scroll_step" allows
the user to define how many pixels the page is moved in every step of
the mouse wheel. The default is increased to 100 pixels per step.
|
|
The DuckDuckGo service that redirects the links from the search page is
returning a broken page for non-javascript browsers. They have a meta
refresh tag in the body, instead of in the head.
Adding the kd=-1 argument causes the DuckDuckGo search results to point
directly to the target page avoiding the redirection.
Based on this patch:
https://salsa.debian.org/debian/dillo/-/commit/ffbd4fc0e6cf94b3947d02766224c0e80344a017
Thanks: liftof+dbug@gmail.com
Thanks: Axel Beckert <abe@debian.org>
Bug-Debian: https://bugs.debian/org/924357
|
|
|
|
|
|
Doxygen introduces a extra header line with a comment
which is now captured.
|
|
Add option to disable XEmbed support.
This can be useful to avoid compilation issues on non-X11 systems.
|
|
This should fix "-x <window id>" when dillo is compiled with fltk-1.3.4.
Reported-by: Arthur Huillet
|
|
|
|
It wasn't necessary! ;)
|
|
|
|
|
|
|
|
|
|
The handshake stuff should be named handshake. What should you call
initialize/setup plus handshake, then? I don't know, but 'connect'
for now, anyway.
|
|
as mentioned in the previous commit msg
|
|
Johannes reported that mbed TLS didn't like the connect() to be ongoing
still when the tls handshake was started on osx or dragonfly.
For an earlier version of the fix (which failed), it was basically free
to iterate through the IP address list upon connect() failure, so that
was implemented, and now I'm artificially breaking this patch into two
pieces to commit that separately.
|
|
|
|
You can trust an intermediate certificate in a chain, so let's be careful
with words here. It would of course be better to tell the user which
certificate was trusted in that case, but my understanding is that I would
have to go through each certificate in the chain and try to match it against
all of the trusted certificates, like mbed tls's verification code does in
the first place. This would involve a lot of digging around in mbed tls's
structures and using resources...
|
|
Until late 2007, it set a variable showing that ipv6 was working.
|
|
|
|
|
|
algorithms
|
|
|
|
|
|
reported by Nick Warne http://lists.dillo.org/pipermail/dillo-dev/2016-July/010941.html
checking mbedtls/ssl.h usability... no
checking mbedtls/ssl.h presence... yes
configure: WARNING: mbedtls/ssl.h: present but cannot be compiled
configure: WARNING: mbedtls/ssl.h: check for missing prerequisite headers?
configure: WARNING: mbedtls/ssl.h: see the Autoconf documentation
configure: WARNING: mbedtls/ssl.h: section "Present But Cannot Be Compiled"
configure: WARNING: mbedtls/ssl.h: proceeding with the compiler's result checking for mbedtls/ssl.h... no
configure: WARNING: *** mbed TLS 2 not found. Disabling SSL/HTTPS/TLS support. ***
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Avoid closing the <A> element until HTML5 rules are in place for the parser.
|
|
No longer necessary since the new nesting-cleanup design.
|
|
No longer necessary after the redesign of the parser's cleanup
process for tag nesting.
|
|
This needed moving around some functions, nothing else.
FWIW, we had it declared extern because that's C++ way to declare a forward
variable, the side effect of it being extern linkage.
|
|
* Forbidden nesting now is handled by cleanup_at_open.
(it previously used an ad-hoc function hooked into the process)
Much safer and versatile now. [1],[2],[4]
* Heuristical cleanup at close is no longer used.
cleanup_at_close is now based on block/inline element/container semantics,
and also cosiders special nesting rules expressed in the DTD for HTML-4.01.
Note: this design is easy to tailor for HTML5. [2]
* Bug reporting changed and is now is more centralized in cleanup_to_idx.
* The bug meter gives more accurate and concise messages. [4]
* Page rendering improved as now the cleanup process strives to produce
a correct tree out of Tag Soup, before feeding it to Dw. [4]
* Better handling/recovery from Tag Soup (even in the worst cases). [5]
* The w3c_plus_heuristics=FALSE mode was removed (not necessary anymore)
* Elements with optional close also follow Firefox de facto rules.
* Special case logic is now isolated in helper functions.
A few examples:
[1] http://dillo.org/test/cross-nesting-simple.html
[2] http://slashdot.org/
[3] http://apod.nasa.gov/apod/ap160604.html
[4] http://www.mypetchicken.com:80/catalog/Day-Old-Baby-Chicks/Olive-Eggers-p1478.aspx
[5] http://dillo.org/test/sd3.html
|
|
It was redundant with the "inline element" flag. i.e.
"block element" = ~"inline element"
|
|
|