Package Details: keybase-bin 5.6.1_20210125164223+f3b21527b9-1

Git Clone URL: https://aur.archlinux.org/keybase-bin.git (read-only, click to copy)
Package Base: keybase-bin
Description: the Keybase Go client, filesystem, and GUI
Upstream URL: https://keybase.io
Licenses: BSD
Conflicts: kbfs, keybase, keybase-git, keybase-gui, keybase-release
Provides: kbfs, keybase, keybase-gui
Submitter: oconnor663
Maintainer: oconnor663 (keybase)
Last Packager: keybase
Votes: 144
Popularity: 2.10
First Submitted: 2016-06-22 16:52
Last Updated: 2021-01-25 19:22

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

nallekarhu commented on 2018-08-06 23:51

Keybase is running, but can't start gui. I see errors in journalctl: [ERRO keybase main.go:90] 001 dial unix /run/user/1000/keybase/keybased.sock: connect: no such file or directory ... keybase.gui.service: Main process exited, code=dumped, status=11/SEGV ... keybase.gui.service: Failed with result 'core-dump' Also in dmesg: [ 662.304095] Keybase[5508]: segfault at b87650 ip 0000000000b87650 sp 00007fff392c1d18 error 15 in Keybase[200000+160c000]

oconnor663 commented on 2018-08-06 00:18

@badpixelbr it sounds like you did a Ctrl-C during a previous install or something like that. Probably (hopefully) not an issue specific to this package. Take a look at the solutions mentioned here: https://bbs.archlinux.org/viewtopic.php?id=220552

badpixelbr commented on 2018-08-05 20:49

cant update keybase. when run makepkg -sriC at the end i have:

resolving dependencies... looking for conflicting packages... warning: could not fully load metadata for package keybase-bin-2.5.0_20180803162902+dee7010d7a-1 error: failed to prepare transaction (invalid or corrupted package) ==> WARNING: Failed to install built package(s).

and previous instalation cant work after try to update. after i remove keybase package and try to install again i have the same error.

axionl commented on 2018-05-30 00:50

keybase-bin E: Missing custom license directory (usr/share/licenses/keybase-bin)

oconnor663 commented on 2018-03-04 20:05

We're working on replacing the "mount helper" entirely with a small root process that will serve symlinks pointing to a user-specific mount under your homedir. That should both avoid some security issues and support the "multiple users on the same system" case properly for the first time. So in short, all of this stuff is in flux. (Folks who prefer to disable all of this, see https://github.com/keybase/client/pull/10724.)

eschwartz commented on 2018-03-04 00:10

@eduard, see https://github.com/keybase/client/issues/10487 and note that the latest git version of keybase will "fix" this by simply running the mount helper as SUID root.

eduard commented on 2018-03-03 07:46

/usr/bin/run_keybase: line 121: 4298 Segmentation fault keybase-mount-helper -user-mount "$mountdir"

gdamjan commented on 2018-02-25 18:03

@Eschwartz I agree completely with you.

eschwartz commented on 2018-02-25 17:53

Currently /keybase is just a pointless symlink to /var/lib/keybase/mount1 which is itself a pointless symlink to ~/.local/share/keybase/fs for the first user account on the computer that used keybase.

This obviously requires something to perform the symlinking. The keybasehelper user and suid binary manage this to ensure that /keybase remains a symlink to wherever your kbfs mountpoint is truly located. This achieves no goal other than to ensure that people can reference /keybase and the filepath will work everywhere... assuming that by everywhere you mean on single-user systems...

So:

1) it doesn't even really work entirely, and maintaining this legacy symlink is inferior to simply using the correct location.

2) It requires having yet another /etc/passwd entry, and on top of that requires running a suid binary -- which is admittedly not so bad considering that it only runs as a restricted user account. https://github.com/keybase/client/pull/10250 Now instead of a world-writable mountpoint directory in root, there is a symlink in root to a symlink owned by a suid binary that points to a mountpoint.

Since I'm the one who is packaging the community package, I'm the one who gets to say I won't implement this, and people should just join the future and use ~/.local/share/keybase/fs or configure their own mountdir via keybase config. ;)

gdamjan commented on 2018-02-25 17:30

What exactly is "suid-keybasehelper-and-extra-system-user shenanigans"?

setting homedir as / for a uid that doesn't do much, is fine