Thank you Rodrigo for the pgp/signing info - i have now installed the dillo-3.1.0 and it installed and runs fine On Mon, 27 May 2024 22:41:16 +0200 Rodrigo Arias <rodarima@gmail.com> wrote:
Hi,
On Mon, May 27, 2024 at 12:52:12PM -0600, pastebin@gmx.com wrote:
Hello dillo-dev mailing list,
i was able to successfully import into sylpheed what appears to be a complete mbox of the old original dillo.org mailing list and the new mailman3.com mailing list - (thank you very much for this work and setting up the new mailman3.com mailing list)
If you happen to have an old archive I would like to get a copy, as there are some segments of time with missing attachments or other problems. I tried to put it together as best as I could from the copies I could get from the web. You can upload it to archive.org to avoid sending large files to the ML.
i have saved 140 emails from 2019-2022 in (2) tar.bz2 files (total 780K) your archive seems to be missing my posts :) which are in these as well i would have no idea about sending them to the archive.org but what about sending them to you directly rather then through the mailing list? they are in indivdual files just tarred up sylpheed folder dirs not in mbox format
i have reposted my 5/11/24 post to the old (dead) dillo.org mailing list to this list
i am glad to see dillo being reborn - it is my main http/https browser (i use w3m and curl and seamonkey as needed)
Glad to see Dillo is still being used :-)
---
To: dillo-dev@dillo.org Subject: dillo-3.1.0 Date: Sat, 11 May 2024 16:00:22 -0600
Hi
i just saw this on slashdot https://tech.slashdot.org/story/24/05/11/1348216/lightweight-dillo-browser-r...
and downloaded dillo-3.1.0.tar.bz2 from (https://github.com/dillo-browser/dillo/releases/download/v3.1.0/dillo-3.1.0....) configure --enable-ssl --disable-ipv6 (--enable-ssl from dillo-3.0.5 is deprecated in dillo-3.1.0) (
The --enable-ssl flag is renamed to --enable-tls and is now enabled by default.
checking FLTK 1.3... yes checking for libpng version... 1.6.37 configure: Using OpenSSL as TLS library. checking for pthread_create in -lpthread... yes
make good make install didn't do
but because of many known questions of github vulnerability problems (i no longer get any source from github - except this one time)
You don't need to trust GitHub, both the tarball and the release tag are signed with my GPG key:
% gpg --keyserver keys.openpgp.org --recv-keys 32E65EC501A1B6FDF8190D293EE6BA977EB2A253 gpg: key 3EE6BA977EB2A253: "Rodrigo Arias Mallo <rodarima@gmail.com>" 1 new signature gpg: Total number processed: 1 gpg: new signatures: 1
% gpg --verify dillo-3.1.0.tar.gz.asc dillo-3.1.0.tar.gz gpg: Signature made 2024-05-04T22:12:49 CEST gpg: using RSA key 32E65EC501A1B6FDF8190D293EE6BA977EB2A253 gpg: Good signature from "Rodrigo Arias Mallo <rodarima@gmail.com>" [ultimate]
% git tag -v v3.1.0 object 995ed3bd934484df7cfc437324f1eea2202d179b type commit tag v3.1.0 tagger Rodrigo Arias Mallo <rodarima@gmail.com> 1714853597 +0200
Release version 3.1.0 gpg: Signature made 2024-05-04T22:13:25 CEST gpg: using RSA key 32E65EC501A1B6FDF8190D293EE6BA977EB2A253 gpg: issuer "rodarima@gmail.com" gpg: Good signature from "Rodrigo Arias Mallo <rodarima@gmail.com>" [ultimate]
GitHub has not had the chance to write anything to the repository silently. Changes are merged from the command line using git, as I don't trust the web PR merge button.
i didn't install it or run it until i can go over the code myself or someone also does a security check of the source code (added 5/27/24 this is only a reflection on the github problems and not on anyone coding dillo)
If you find any issues, please report them here so we can fix them. I tried my best to improve Dillo, but I may have also accidentally introduced new bugs (as with any piece of software).
my only problems with 3.0.5 where changes in the size of 'dialog' popups that affected other popup sizes (i will be more specific when they next occur) there appears to be one 'size' that applies to all popups? am i correct? if they occur with the dillo-3.1.0 i will report what i find
Keep in mind that running the configure itself is dangerous if you don't trust the source.
I've been compiling source since early red hat and it never dawned on me that running ./configure is as dangerouse as hacked source itself - if the source is not trusted then neither is the ./configure - thanks for straightening me out on a decade old basic false assumption i've had (YIKES!)
If you don't trust doing `make install` as root, you can use the --prefix=/foo/bar flag to install Dillo in a path were your user can write (instead of /usr/local), then you don't need root to install it. You will only need to `export PATH=$PATH:/boo/bar/bin` to get the Dillo binaries in your PATH.
i have done my own dillo-3.1 from dillo-3.0.5
Do you mean you have some patches of your own? It would be nice if you can share them if that is the case.
My changes from 3.0.5 to my 3.1 are largely cosmetic prefernces (local loading of help file vs getting it over the web when click '?' and adding duckduck to primary search choice when click 'magnifying glass' and changing position of dialog buttons i will post them in case someone else wants them -
i will also wait to test the configure option --enable-html-tests Enable HTML tests (requires xvfb, xwd and imagemagick)
Those tests check that Dillo renders a test page pixel-by-pixel identical to a reference page and are designed to catch regressions. They are not required for general use of the browser.
Best, Rodrigo. _______________________________________________ Dillo-dev mailing list -- dillo-dev@mailman3.com To unsubscribe send an email to dillo-dev-leave@mailman3.com