Package Details: keeweb 1.18.7-1

Git Clone URL: https://aur.archlinux.org/keeweb.git (read-only, click to copy)
Package Base: keeweb
Description: Desktop password manager compatible with KeePass databases
Upstream URL: https://keeweb.info
Keywords: kdbx keepass password
Licenses: MIT
Conflicts: keeweb-desktop
Submitter: surefire
Maintainer: petercxy
Last Packager: petercxy
Votes: 16
Popularity: 0.84
First Submitted: 2016-09-26 07:43
Last Updated: 2021-08-13 10:50

Pinned Comments

petercxy commented on 2021-08-13 10:51

This package has been adopted and keeweb-connect support has been fixed. You might need to disable & re-enable the browser connector support in the app in order to update the native messaging configurations.

Latest Comments

1 2 3 4 5 6 Next › Last »

elbowz commented on 2021-08-17 10:41

Works like a charm! Thanks for your work and effort. I'm on Google Chrome v92.0.4515.131

petercxy commented on 2021-08-13 10:51

This package has been adopted and keeweb-connect support has been fixed. You might need to disable & re-enable the browser connector support in the app in order to update the native messaging configurations.

Sherlock-Holo commented on 2021-06-19 03:38

miss file /usr/share/keeweb-desktop/keeweb-native-messaging-host this file is contained in keeweb-desktop-bin

pvdp commented on 2021-05-28 02:52

Getting same error

⠋ Building module: keyboard-auto-type, Completed: 1../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp: In function ‘uint32_t keyboard_auto_type::char_to_keysym(char32_t)’:
../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp:198:40: error: ‘numeric_limits’ is not a member of ‘std’
  198 |             return *found_in_32 & std::numeric_limits<uint32_t>::max();
      |                                        ^~~~~~~~~~~~~~
../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp:198:63: error: expected primary-expression before ‘>’ token
  198 |             return *found_in_32 & std::numeric_limits<uint32_t>::max();
      |                                                               ^
../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp:198:66: error: ‘::max’ has not been declared; did you mean ‘std::max’?
  198 |             return *found_in_32 & std::numeric_limits<uint32_t>::max();
      |                                                                  ^~~
      |                                                                  std::max
In file included from /usr/include/c++/11.1.0/algorithm:62,
                 from ../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp:5:
/usr/include/c++/11.1.0/bits/stl_algo.h:3467:5: note: ‘std::max’ declared here
 3467 |     max(initializer_list<_Tp> __l, _Compare __comp)
      |     ^~~
../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp:206:34: error: ‘numeric_limits’ is not a member of ‘std’
  206 |             return *found & std::numeric_limits<uint16_t>::max();
      |                                  ^~~~~~~~~~~~~~
../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp:206:57: error: expected primary-expression before ‘>’ token
  206 |             return *found & std::numeric_limits<uint16_t>::max();
      |                                                         ^
../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp:206:60: error: ‘::max’ has not been declared; did you mean ‘std::max’?
  206 |             return *found & std::numeric_limits<uint16_t>::max();
      |                                                            ^~~
      |                                                            std::max
In file included from /usr/include/c++/11.1.0/algorithm:62,
                 from ../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp:5:
/usr/include/c++/11.1.0/bits/stl_algo.h:3467:5: note: ‘std::max’ declared here
 3467 |     max(initializer_list<_Tp> __l, _Compare __comp)
      |     ^~~
make: *** [keyboard-auto-type.target.mk:143: Release/obj.target/keyboard-auto-type/keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.o] Error 1

elbowz commented on 2021-05-19 10:11

Error go away simply adding #include <limits> in the src/linux/x11-keysym-map.cpp

I'm wondering, why I'm the only one with this error.

edit: fixed in the main repo https://github.com/antelle/keyboard-auto-type/issues/1

keeweb-connect (browser native extension) still not working

elbowz commented on 2021-05-18 09:20

Getting:

../keyboard-auto-type/keyboard-auto-type/src/linux/x11-keysym-map.cpp:198:40: error: ‘numeric_limits’ is not a member of ‘std’
  198 |             return *found_in_32 & std::numeric_limits<uint32_t>::max();
[...]
An unhandled error occurred inside electron-rebuild
node-gyp failed to rebuild '/home/muttley/.cache/pacaur/keeweb/src/keeweb-native-modules/node_modules/keyboard-auto-type'.
Error: `make` failed with exit code: 2

@dolfinus: thx for the deeply description of issue...any news about a fix for this package?

alfredo.ardito commented on 2021-05-16 09:10

Installs now after last commit

alfredo.ardito commented on 2021-05-15 22:24

Cannot build coz
nodejs-lts-fermium and nodejs are in conflict

dolfinus commented on 2021-05-13 12:15

Before 1.18 release the only way to integrate Keeweb with any browser was to install KeeWebHTTP plugin.

Since 1.18 release KeeWebHTTP become broken and has been removed from the plugin list. But a brand new native browser integration was added instead.

This integration constist of 3 main parts:

  1. "keeweb-native-messaging-host" binary file. Source code is here: https://github.com/keeweb/keeweb-connect/tree/master/native-messaging-host, build file is then copied and packed into the archive (deb, zip, appimage and so on) during Keeweb build step (see https://github.com/keeweb/keeweb/blob/f59b846643fec03d726799bd8f77283d3b2f4ce4/Gruntfile.js#L247).

  2. If browser integration is enabled, Keeweb creates a manifest file (like this one https://github.com/keeweb/keeweb-connect/blob/master/native-manifest.json) with path of that binary file being stored inside (see https://github.com/keeweb/keeweb/blob/f59b846643fec03d726799bd8f77283d3b2f4ce4/desktop/scripts/util/browser-extension-installer.js#L108). Then Keeweb makes it accessible for a browser extension by copying to a user config folder (see https://github.com/keeweb/keeweb/blob/f59b846643fec03d726799bd8f77283d3b2f4ce4/desktop/scripts/util/browser-extension-installer.js#L8).

  3. Browser loads this manifest file (see https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_manifests) and allows browser extension to use this service to securely connect to Keeweb.

It's working perfectly on keeweb-desktop-bin AUR package, but not the current one.

This is caused by:

  1. There is no step of building native messaging binary file in PKGBUILD file, so there is no such file in the resulting package.

  2. Keeweb calls app.getPath('exe') function to get current executable file path (see "keeweb" file in the root of the package https://github.com/keeweb/keeweb/releases/download/v1.18.4/KeeWeb-1.18.4.linux.x64.zip), and then uses it to build a path for "keeweb-native-messaging-host" binary file which is located in just the same directory. But according to current PKGBUILD Keeweb is being started using system Electron package (exec ${_electron} /usr/lib/keeweb/app.asar --disable-updater "\$@"), so this function is returning a path to the Electron itself ("/usr/lib/electron/electron"), not the keeweb executable ("/usr/bin/keeweb").

It looks like the current way of building the package is completely incompatible with this feature.

elbowz commented on 2021-04-27 14:40

LTS version of nodejs solve any issue

Thanks a lot!