From sdavies at umw.edu  Sat Apr 14 20:55:55 2018
From: sdavies at umw.edu (Stephen Davies (sdavies))
Date: Sat, 14 Apr 2018 18:55:55 +0000
Subject: [qutebrowser] certificate errors
Message-ID: <20180414185453.GD2888@umw.edu>


    When I visit certain websites, especially on certain wireless networks,
qutebrowser gets peppered with periodic messages that I have to click through:

        Certificate errors -- continue?
        Server's certificate is not trusted.

    Is there a way to disable these?

    Perhaps you'll tell me that it's dangerous and evil to do so. That's as
may be, but I do know that these are sites I check periodically, recognize the
content on, and have strong reason to believe are not compromised in any way.
Further, other browsers never complain about them.

- Stephen Davies, Ph.D.
  (stephen at umw.edu)

From jaygkamat at gmail.com  Sat Apr 14 21:32:06 2018
From: jaygkamat at gmail.com (Jay Kamat)
Date: Sat, 14 Apr 2018 15:32:06 -0400
Subject: [qutebrowser] certificate errors
In-Reply-To: <20180414185453.GD2888@umw.edu> (Stephen Davies's message of
 "Sat, 14 Apr 2018 18:55:55 +0000")
References: <20180414185453.GD2888@umw.edu>
Message-ID: <871sfh4ma1.fsf@gmail.com>

Hi Stephen!

"Stephen Davies (sdavies)" <sdavies at umw.edu> writes:

>     Is there a way to disable these?

I think you can do this with :set content.ssl_strict false

>     Perhaps you'll tell me that it's dangerous and evil to do so. That's as
> may be, but I do know that these are sites I check periodically, recognize the
> content on, and have strong reason to believe are not compromised in any way.
> Further, other browsers never complain about them.

Yes, this is probably a very bad idea, since you wouldn't know if you're
being MITM'd. I'm not sure why there are more SSL warnings in
qutebrowser than in normal ones (I see them too). I think this might be
qutebrowser using system certs rather than the built-in ones (but I'm
not sure if that's the case).

-Jay


From mail at fritzreichwald.de  Sun Apr 15 00:19:56 2018
From: mail at fritzreichwald.de (Fritz Reichwald)
Date: Sun, 15 Apr 2018 00:19:56 +0200
Subject: [qutebrowser] certificate errors
In-Reply-To: <871sfh4ma1.fsf@gmail.com>
References: <20180414185453.GD2888@umw.edu> <871sfh4ma1.fsf@gmail.com>
Message-ID: <87muy5whv7.fsf@fritz-gpd.i-did-not-set--mail-host-address--so-tickle-me>

Hi Jay

> I'm not sure why there are more SSL warnings in
> qutebrowser than in normal ones (I see them too). I think this might be
> qutebrowser using system certs rather than the built-in ones (but I'm
> not sure if that's the case).

I think its because qutebrowser tells you about the issues with a popup
but other browsers only show some small icon somewhere you are not
looking at regularly.

Fritz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://listi.jpberlin.de/pipermail/qutebrowser/attachments/20180415/7ae76aec/attachment.asc>

From me at the-compiler.org  Sun Apr 15 10:07:40 2018
From: me at the-compiler.org (Florian Bruhin)
Date: Sun, 15 Apr 2018 10:07:40 +0200
Subject: [qutebrowser] certificate errors
In-Reply-To: <871sfh4ma1.fsf@gmail.com>
References: <20180414185453.GD2888@umw.edu>
 <871sfh4ma1.fsf@gmail.com>
Message-ID: <20180415080740.4ki36gx7lx7hlqoi@hooch.localdomain>

On Sat, Apr 14, 2018 at 03:32:06PM -0400, Jay Kamat wrote:
> Hi Stephen!
> 
> "Stephen Davies (sdavies)" <sdavies at umw.edu> writes:
> 
> >     Is there a way to disable these?
> 
> I think you can do this with :set content.ssl_strict false

Or set it to "true" instead and see how that goes, where it silently
drops those connections.

> >     Perhaps you'll tell me that it's dangerous and evil to do so. That's as
> > may be, but I do know that these are sites I check periodically, recognize the
> > content on, and have strong reason to believe are not compromised in any way.
> > Further, other browsers never complain about them.
> 
> Yes, this is probably a very bad idea, since you wouldn't know if you're
> being MITM'd. I'm not sure why there are more SSL warnings in
> qutebrowser than in normal ones (I see them too). I think this might be
> qutebrowser using system certs rather than the built-in ones (but I'm
> not sure if that's the case).

Likely because other browsers only allow you to bypass it if it's a
toplevel navigation, while qutebrowser also asks for resources which are
loaded from a page with invalid certificate.

Related issue: https://github.com/qutebrowser/qutebrowser/issues/3418

Florian

-- 
https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
         I love long mails! | https://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://listi.jpberlin.de/pipermail/qutebrowser/attachments/20180415/f104b740/attachment.asc>

From jonathan at saunderstech.org  Tue Apr  3 16:52:49 2018
From: jonathan at saunderstech.org (Jonathan Saunders)
Date: Tue, 03 Apr 2018 14:52:49 -0000
Subject: [qutebrowser] Keybindings reset?
Message-ID: <CAPgn+G5VeH66CeRPEKBT+e-oDY9bYjtOzS3T92HW9HHu32S84Q@mail.gmail.com>

Out of nowhere, "j" and "k" on qutebrowser started working as :tab-prev and
:tab-next instead of scrolling down and up. Then, I pressed another key
("a", I think) and the browser crashed. Upon re-startup, all my custom
keybindings (of which I have many) were reset!

Has anyone else experienced this issue? Or, did I not catch the news that
the latest version resets keybindings or something?

I'm running qutebrowser v1.2.1-1 on Arch Linux. The last update I performed
was a day ago...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://listi.jpberlin.de/pipermail/qutebrowser/attachments/20180403/d155cd1c/attachment.htm>

From efokken at posteo.de  Fri Apr 13 15:14:55 2018
From: efokken at posteo.de (Eike Fokken)
Date: Fri, 13 Apr 2018 13:14:55 -0000
Subject: [qutebrowser] patch for background window behaviour
Message-ID: <478a05c4-2628-f7e2-628e-de986e51703b@posteo.de>

Dear all,

in issue 818 [1] people (among them me) had the problem that background 
windows grab focus and as it were I could only tell the window manager 
to unfocus all qutebrowser windows or none.
I wrote a patch that gives background windows the window_role 
"qutebrowser_background" so that the window manager can tell them apart 
and treat them differently.

I think this adds functionality without breaking anything for people not 
using it.

Best

Eike

[1] https://github.com/qutebrowser/qutebrowser/issues/818
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Adds-the-window_role-qutebrowser_background-for-back.patch
Type: text/x-patch
Size: 2118 bytes
Desc: not available
URL: <https://listi.jpberlin.de/pipermail/qutebrowser/attachments/20180413/662778e8/attachment.patch>