[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1032806: RFS: privacybrowser/0.1-1 [ITP] -- web browser that respects your privacy



Paul,


I am one of the Debian Qt WebEngine maintainers, and I also submit code to the upstream Qt project.


The Salsa link you included appears to be a bit misinformed about security support for Qt WebEngine in Debian.  For more accurate information, I would point you to this link:


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032794


Bug fixes for Qt WebEngine are backported every couple of months by upstream Qt:


https://www.qt.io/blog/commercial-lts-qt-5.15.13-released


There are a number of other browsers based on Qt WebEngine currently in Debian.  A non-exhaustive list includes the following:


Konqueror

Falkon

qutebrowser

Angelfish


If you are interested in more information about the subject, I have a section of Privacy Browser’s handbook dedicated to the subject which is included in the index.docbook in the .deb.


Soren


On Tuesday, March 14, 2023 6:19:44 PM MST you wrote:

> On Sat, 2023-03-11 at 14:41 -0700, Soren Stoutner wrote:

> >  * URL              : https://www.stoutner.com/privacy-browser-pc/

> >   privacybrowser - web browser that respects your privacy

>

> I note that this browser depends on Qt WebEngine, all the Qt based web

> engines are not security supported in Debian. I encourage you to switch

> to a browser engine that is security supported, or discuss with the

> Debian and upstream Qt web engine maintainers to add such support.

>

> https://salsa.debian.org/debian/debian-security-support/-/blob/master/securi

> ty-support-limited

>  * qtwebengine-opensource-src: No security support upstream and

>    backports not feasible, only for use on trusted content

>  * qtwebkit: No security support upstream and backports not feasible,

>    only for use on trusted content

>  * qtwebkit-opensource-src: No security support upstream and backports

>    not feasible, only for use on trusted content

>  * kde4libs: khtml has no security support upstream, only for use on

>    trusted content

>  * khtml: khtml has no security support upstream, only for use on

>    trusted content, see #1004293



--

Soren Stoutner

soren@stoutner.com

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: