[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-ports
Subject:    Re: UPDATE: security/keepassxc (OpenBSD 6.5?)
From:       Giovanni Bechis <giovanni () paclan ! it>
Date:       2019-03-30 11:56:25
Message-ID: 20190330115625.GA63737 () bigio ! paclan ! it
[Download RAW message or body]

On Sat, Mar 30, 2019 at 10:45:20AM +0100, Rafael Sadowski wrote:
> On Fri Mar 29, 2019 at 07:12:01PM +0100, Giovanni Bechis wrote:
> > On Fri, Mar 29, 2019 at 05:02:27PM +0100, Antoine Jacoutot wrote:
> > > On Fri, Mar 29, 2019 at 03:34:53PM +0100, Rafael Sadowski wrote:
> > > > Below you can find an update to the next keepassxc release 2.4.0.
> > > > Upstream removed KeePassHttp support which means there is no browser
> > > > support in OpenBSD.
> > > > 
> > > > The current/new browser support in keepssxc needs the keepassxc-plugin
> > > > but this plugin uses uses FF native-messaging which is unsupported on
> > > > OpenBSD atm.
> > > 
> > > That will break it only for firefox, right?
> > > 
> > AFAIK Chromium will continue to work (untested), this must be tested before commit
> > anyway
> 
> I guess it's never worked before. I see the same issue as in FF:
> 
> "KeePassXC-Browser has encountered an error:
> 
> Cannot connect to KeePassXC. Check that browser integration is enabled
> in KeePassXC settings."
> 
2.3.4 works iff you disable unveil in Chromium

> > 
> > > > I would like to ask the community. Go in without browser support or wait
> > > > for post 6.5 unlock?
> > > > 
> > I would prefer to wait, at list to find alternives if Firefox it's not easily
> > fixable.
> 
> BTW the old (removed) browser support is horrible. I prefer CTLR+B (copy
> username) + CTLR+C (copy password).
> 
I can survive with it even if I like how it works with FF.

 Giovanni

[prev in list] [next in list] [prev in thread] [next in thread]