search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

OS X: kbfs fails when /keybase is not owned by my renumbered uid #3018

Open nopdotcom opened 6 years ago

nopdotcom commented 6 years ago

Recently I renumbered uids. This usually involves chown -R username ~username. I discovered I had to change the ownership of /keybase for the kbfs mount to succeed. Strange error messages spammed me until I did this.

I believe this is the single-user case of #2322.

In this case, my problem would likely be solved if /keybase were a symlink to ~/Library/Application Support/Keybase/fs or somewhere else kbfs is mounted in $HOME--that’s the only place users can really count on being writable.

Note that placing the real root somewhere private in $HOME (or $XDG_RUNTIME_DIR aka /run/user/{uid}) simplifies the problem of “I don’t want /keybase, put it in ~/keybase please.” #2306

nopdotcom commented 6 years ago

Now that I have made a useful bug report, let me separately plead for /opt/keybase. It’s available on every Unix we care about. And you can always ln -s /opt/keybase /keybase...

sfkleach commented 5 years ago

Can I specifically plead against both /keybase and /opt/keybase. MacOS is a multi-user system and these locations are not suitable for MacOS or UNIX-like systems - unless they are partitioned into separate user sub-directories. (However, /opt should not be used for dynamically changing data, /var is the right location.)

strib commented 5 years ago

@sfkleach we no longer mount user directories at /keybase. They are mounted at /Volumes/Keybase (localUserName). /keybase is a global redirector that takes the user who makes the request to their specific mountpoint.