search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.91k stars 1.23k forks source link

Enable Keybase in Finder doesn't work in macOS Big Sur 11.0.1 #24366

Closed jburnett closed 3 years ago

jburnett commented 4 years ago

After upgrading to macOS Big Sur 11.0.1, Keybase client is not working with Finder, and enabling does not work. In main app, select Files tab; "Enable Keybase in Finder?" should show at the top. Click to accept "I understand that closed source...", and push "Yes, enable" button.

Result: After working for a few seconds, nothing changes and "Yes, enable" button is enabled again. Attempting to navigate to any keybase managed files gives permission denied.

Keybase client for macOS 5.5.0-20200526170801+139bb348af (installed via brew). kbfuse version is 10.11 with symlinks for higher versions.

❯ ll /Library/Filesystems/kbfuse.fs/Contents/Extensions/
total 0
drwxr-xr-x@ 3 root  wheel    96B May 26 13:19 10.11/
lrwxr-xr-x  1 root  wheel     5B May 26 13:19 10.12@ -> 10.11
lrwxr-xr-x  1 root  wheel     5B May 26 13:19 10.13@ -> 10.11
lrwxr-xr-x  1 root  wheel     5B May 26 13:19 10.14@ -> 10.11
lrwxr-xr-x  1 root  wheel     5B May 26 13:19 10.15@ -> 10.11
chris01b commented 3 years ago

It's just a temporary fix but following this Reddit post, updating the to newest pre-release of Fuse, and creating symlinks for sudo ln -s 10.11 10.16 and sudo ln -s 10.11 11.0 seemed to work for me. I don't think you have to do all of those steps but this method worked for me.

kolobus commented 3 years ago

Both fixes above give no result on Apple M1 MB, so problem might be somewhere else, ARM- related.

ekingery commented 3 years ago

updating the to newest pre-release of Fuse

It looks like you can now use the latest stable version of macFUSE (currently 4.0.4)

MarcoMartins86 commented 3 years ago

I too was struggling with this for quite some time, I needed to create the symlink with the correct version 11.0.1 not 11.0 cd /Library/Filesystems/kbfuse.fs/Contents/Extensions/ sudo ln -s 10.11 11.0.1 Launch Keybase application and saw the warning to accept the permission on System Preferences -> Security & Privacy -> General and finally, it started to work.

kolobus commented 3 years ago

Did not worked for me with hack from @MarcoMartins86 and macFUSE 4.0.4. I wonder what is the root of problem

adamhsparks commented 3 years ago

Same behaviour in 11.1 as noted by @kolobus. The hack from @MarcoMartins86 with macFUSE 4.0.4 doesn't work with this version either by symlinking 10.11 to 11.1.

jburnett commented 3 years ago

FWIW: I appreciate the work arounds, I prefer to confirm a real fix from keybase dev team.

adamhsparks commented 3 years ago

@jburnett, same here.

jag3773 commented 3 years ago

Likewise, this is affecting my workflow significantly. I can't find a workaround that works on either 11.0.1 or 11.1 :/

NewAlexandria commented 3 years ago

This is affecting a few peoples' workflow now. We don't really want to buy more new machines to head back to the intel-CPU arch. Some official statement would be greatly appreciated, like "we are going to pay-off the macfuse guy, and a fix is coming"

artushin commented 3 years ago

I'm on Big Sur 11.1 and tried the various symlinks as well, without any luck. Ended up with 

drwxr-xr-x   3 root  wheel   96 Jan 30  2020 10.11
lrwxr-xr-x   1 root  wheel    5 Jan 30  2020 10.12 -> 10.11
lrwxr-xr-x   1 root  wheel    5 Jan 30  2020 10.13 -> 10.11
lrwxr-xr-x   1 root  wheel    5 Jan 30  2020 10.14 -> 10.11
lrwxr-xr-x   1 root  wheel    5 Jan 30  2020 10.15 -> 10.11
lrwxr-xr-x   1 root  wheel    5 Dec 27 12:27 11.0 -> 10.11
lrwxr-xr-x   1 root  wheel    5 Dec 27 12:27 11.0.1 -> 10.11
lrwxr-xr-x   1 root  wheel    5 Dec 27 12:17 11.1 -> 10.11

However, I was finally able to get it working by loading the kext via kextutil as per https://github.com/keybase/client/blob/cac9573e33f472fcb1417c1e6a899bfbba36405c/osx/Fuse/README.md

sudo kextutil -l /Library/Filesystems/kbfuse.fs/Contents/Extensions/10.11/kbfuse.kext

and then allowing via the Security popup.

Who knows what edge cases the creates but basic functionality works.

adamhsparks commented 3 years ago

To add a further complication. Has Anyone have any luck with using sudo kextutil -l /Library/Filesystems/kbfuse.fs/Contents/Extensions/10.11/kbfuse.kext on an M1 Mac?

I'm still sorting mine out after receiving it yesterday, so there may be something obvious that I'm just missing.

Executing: /usr/bin/kmutil load --bundle-path /Library/Filesystems/kbfuse.fs/Contents/Extensions/10.11/kbfuse.kext --load-style start-only
Error Domain=KMErrorDomain Code=71 "Incompatible architecture: Binary is for x86_64, but needed arch arm64e" UserInfo={NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e}
kolobus commented 3 years ago

@adamhsparks I have exactly same error on m1.

jsatk commented 3 years ago

Having the same issue on Intel MacBook running macOS 11.1 Big Sur.

MarcoMartins86 commented 3 years ago

@adamhsparks that is a different problem and the only way to fix it is by compiling the code from scratch and maybe do some in code adjustments for that architecture, M1 is an ARM-based chip that has different opcodes (assembly code) than Intel ones.

24Gosiaczek1982 commented 3 years ago

Polecam

adamhsparks commented 3 years ago

@MarcoMartins86, I understand the differences in architectures. However, it's not an entirely different problem. I still have the exact same issue. I still cannot access my files via Finder.

nehalecky commented 3 years ago

It looks like you can now use the latest stable version of macFUSE (currently 4.0.4)

FWIW, the latest stable release of macFUSE is 4.0.5, and it includes enhancements to macOS 11.x along with Apple Silicon installs.

I've mentioned the same in https://github.com/Homebrew/homebrew-cask/pull/96258, where I'm hoping to see brew updated to this version so scriptable env-building workflows can be sane again.

adamhsparks commented 3 years ago

I see. I was using macFUSE 4.0.4 but this issue still existed. I’ll try 4.0.5 and see if it helps.

On 10 Jan 2021, at 01:43, Nicholaus Halecky notifications@github.com wrote:

 It looks like you can now use the latest stable version of macFUSE (currently 4.0.4)

FWIW, the latest stable release of macFUSE is 4.0.5, and it includes enhancements to macOS 11.x along with Apple Silicon installs.

I've mentioned the same in Homebrew/homebrew-cask#96258, where I'm hoping to see brew updated to this version so scriptable env-building workflows can be sane again.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

jsatk commented 3 years ago

I'm still confused about whatever macFUSE is. Does Keybase on Big Sur now require a new dependency? Are their plans to update it to "just work" as a standalone install on Big Sur?

On 01/09, Nicholaus Halecky wrote:

It looks like you can now use the latest stable version of macFUSE (currently 4.0.4)

FWIW, the latest stable release of macFUSE is 4.0.5, and it includes enhancements to macOS 11.x along with Apple Silicon installs.

I've mentioned the same in https://github.com/Homebrew/homebrew-cask/pull/96258, where I'm hoping to see brew updated to this version so scriptable env-building workflows can be sane again.

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/keybase/client/issues/24366#issuecomment-757341187

leoluz commented 3 years ago

Im running Keybase Version 5.5.0-20200526170801+139bb348af with macFUSE 4.0.5 and I still have the issue. I click "Enable Keybase in Finder" and it takes a few seconds for keybase to return with no Finder integration enabled. I see that I have 2 folders created in /Volumes:

drw-------   2 root    wheel    64B 12 Jan 16:58 Keybase
drw-------   2 myuser  staff    64B 12 Jan 16:58 Keybase (myuser)

Are there anyway to check the logs and see what exactly is broken?

Update Jan 13th 2021: I also managed to make it work by running the following command (like suggested in other comments) and allowing "Keybase Inc" to access the filesystem by following on popup windows that shows up:

sudo kextutil -l /Library/Filesystems/kbfuse.fs/Contents/Extensions/10.11/kbfuse.kext
tsujp commented 3 years ago

Hi friends. None of these are going to work on M1 chips since M1 requires ARM64 (and the emulation for x86_64 via Rosetta2 isn't applicable here I think). I would not recommend any of the symlinking hacks here unless you have a redundant backup of everything on the machine you're using this on, both stuff on Keybase and local storage too. See this comment for more information there: https://github.com/keybase/client/issues/17796#issuecomment-520189673

Unfortunately since Zoom has acquired Keybase development (that we can see) has stopped, see this link showing the commit history; guess when Zoom acquired Keybase: https://github.com/keybase/client/graphs/commit-activity

Now onto my own speculation. This project is likely dead now -- they haven't addressed any meaningful issues or support tickets like these for instance -- and so I'd recommend probably looking to NextCloud or Syncthing for DYI storage.

RIP.

fxlemire commented 3 years ago

I inspired myself from @leoluz's instructions and replaced kextutil by kmutil since the former is now marked as deprecated. Here are the steps that fixed it for me:

jeffbyrnes commented 3 years ago

On the flip side, there's keybase/keybase-issues#3990, which seems to mean on Big Sur that the integration cannot be disabled, which I would like to do, as I don’t use it.

Any tips from y’all?

foss- commented 3 years ago

5.6.2-20210202191343+d72cc00cd3 is out. Sadly no GitHub release available yet. But a screen informing about a macFuse update adding KBFS support on Big Sur + M1 macs. This probably closes this bug here along with https://github.com/keybase/keybase-issues/issues/3990. Can someone confirm?

bigsur
heqian commented 3 years ago

Version 5.6.2 actually broke the soft link I used to fix the issue on macOS 11.2.

elyalvarado commented 3 years ago

Version 5.6.2 worked for me on macOS 11.1 👍

foss- commented 3 years ago

5.6.2 and macOS 11.2 worked as expected here. Should this issue be closed? Ping @jburnett

domq commented 3 years ago

5.6.2 and macOS 11.2 worked as expected here. Should this issue be closed? Ping @jburnett

Same here, except I had to brew install macfuse (to 4.0.5) separately.

jburnett commented 3 years ago

Version 5.6.2 (5.6.2-20210202191343+d72cc00cd3) on macOS v11.2.2 is working correctly now. I did not create symlinks or use brew to manipulate this machine, so Keybase updater seems to have corrected things.

rjurney commented 3 years ago

This is not fixed in v11.2.3 and latest Keybase Version 5.6.2-20210202191343+d72cc00cd3 (5.6.2-20210202191343+d72cc00cd3).

DAMN.

rjurney commented 3 years ago

Version 5.6.2 (5.6.2-20210202191343+d72cc00cd3) on macOS v11.2.2 is working correctly now. I did not create symlinks or use brew to manipulate this machine, so Keybase updater seems to have corrected things.

I don't understand. I am just upgraded to 11.2.3 and 5.6.2. I removed all traces of anything related to MacFUSE and Keybase from my machine. I remove the /Volumes directory for Keybase. I do the install again. Nothing. It has this bug no matter what I do.

ryanmckaytx commented 3 years ago

I have the same versions as @rjurney and am experiencing the same problem.

nilsi commented 3 years ago

Cant get it to work either.

brendonrapp commented 3 years ago

This is still very much broken on Big Sur 11.3.1.

rjurney commented 3 years ago

I think this feature is abandonware.

mkmik commented 3 years ago

To be fair, apple is not making it easy to use FUSE and kernel extensions. That said, I'd be really grateful I'd somebody at keybase could dedicate a little bit of their time to fix this.

JPry commented 3 years ago

I ran into this problem after upgrading from Catalina to Big Sur. It started working again after brew install macfuse and then confirm in Security Settings.

Southclaws commented 3 years ago

Still got this issue with Version 5.7.0-20210622193735+e3826b703a (5.7.0-20210622193735+e3826b703a)

None of the above solutions worked.

davisonja commented 3 years ago

FWIW I'm using 5.7.0-20210622193735+e3826b703a and a brew install macfuse, enable in settings and a reboot brought it all to life for me.

Southclaws commented 3 years ago

Ah I didn't try a reboot, will give that a shot later.

nilsi commented 3 years ago

For me I click "enable finder integration" then "yes enable". It spins for a bit then the spinner stops. No error message or anything. Have done brew install macfuse multiple times and rebooted.

rjurney commented 3 years ago

Upgrading to the latest OS X magically resolved the problem for me. Or was it the new key base?

Southclaws commented 3 years ago

Updated my OS and restarted, same issue

image
domq commented 3 years ago

Updated my OS and restarted, same issue

image

I had this once, and for some reason rebooting once more seemed to help. Attempting to use sshfs prior to that reboot, may or may not have contributed. (I got the “blocked system extension” popup, but couldn't find the corresponding validation task in System Preferences — Strange...)

Southclaws commented 3 years ago

Ah that one extra restart solved it, thanks!

FrancYescO commented 2 years ago

Same for me, As today i'm still not able to enable finder extension with keybase 5.9.0 in Monterey 12.1 .. brew install macfuse did not help. brew install sshfs gives: Error: sshfs has been disabled because it requires closed-source macFUSE!

soriyath commented 2 years ago

this should work without upgrading the os. i fear programmed obsolescence. my laptop works fine as it is.

dushan566 commented 2 years ago

You don't need to have any workarounds.

All you have to do is change startup Security Utility to set the security policy to Reduced Security and select the “Allow user management of kernel extensions from identified developers” checkbox.

Please follow the below steps.

  1. Upload a sample file in your private folder in keybase app
  2. Enable the option "Open in Finder" in the top right corner.
  3. Then it will prompt you to enable the security Extention in the kernel "System Preference >> Security and privacy"
  4. Once you unlock the padlock and tick the box, it will ask you to power off your mac.
  5. Then press and hold the power button to enable security extension in the MacOs kernel
  6. You will see the Recovery assistant window
  7. Select your user and type your password.
  8. Select the 2nd option in the security Extention window (Allow user management of kernel extensions from identified developers” checkbox)
  9. Once the Extention is applied select the apple logo in the top right corner and restart.
  10. Open keybase app, it will again bring you to System Preference >> Security and privacy
  11. Again tick the box it's asking.
  12. Your mac will need to restart
  13. Finally you will see your files in /Volumes/keybase
Goddamit44 commented 2 years ago

Thanks bud. I No very little about this stuff. And by the way I wouldn’t be doing this if I didnt have very good reason to do so. Thanks again On 13 Oct 2022, at 6:58 am, Dushan Wijesinghe @.***> wrote: You don't need to have any workarounds. All you have to do is change startup Security Utility to set the security policy to Reduced Security and select the “Allow user management of kernel extensions from identified developers” checkbox. Please follow the below steps.

Upload a sample file in your private folder in keybase app Enable the option "Open in Finder" in the top right corner. Then it will prompt you to enable the security Extention in the kernel "System Preference >> Security and privacy" Once you unlock the padlock and tick the box, it will ask you to power off your mac. Then press and hold the power button to enable security extension in the MacOs kernel You will see the Recovery assistant window Select your user and type your password. Select the 2nd option in the security Extention window (Allow user management of kernel extensions from identified developers” checkbox) Once the Extention is applied select the apple logo in the top right corner and restart. Open keybase app, it will again bring you to System Preference >> Security and privacy Again tick the box it's asking. Your mac will need to restart Finally you will see your files in /Volumes/keybase

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>