Open jculpon opened 2 years ago
And just to confirm:
% sudo port uninstall keybase;
Password:
---> Deactivating keybase @5.8.1_0
---> Cleaning keybase
---> Uninstalling keybase @5.8.1_0
---> Cleaning keybase
# reinstalling via dmg...
% which keybase;
/Applications/Keybase.app/Contents/SharedSupport/bin/keybase
peri@ged dotfiles-github % keybase account email list;
[private email elided] (visibility: PRIVATE, verified: true, primary: true)
jculpon+keybase@gmail.com (visibility: PUBLIC, verified: true, primary: false)
peri@ged dotfiles-github % keybase pgp select
You are selecting a PGP key from your local GnuPG keychain, and
will publish a statement signed with this key to make it part of
your Keybase.io identity.
Note that GnuPG will prompt you to perform this signature.
You can also import the secret key to *local*, *encrypted* Keybase
keyring, enabling decryption and signing with the Keybase client.
To do that, use "--import" flag.
Learn more: keybase pgp help select
▶ ERROR No PGP keys available to choose from.
# this error is expected as I have revoked all pgp keys
I'd like to note that since there are many different ways to get GnuPG on macOS, working with the same package manager (macPorts in my case, homebrew for many other users) simplifies debugging if there are actually issues in the underlying GnuPG libraries or the integrations with keybase or macOS tooling.
The macports package for the keybase client is currently on 5.8.1, per https://ports.macports.org/port/keybase/ and the command line port search:
As a macports user, I'd expect that if this is going to be supported at all, keybase would push updates to the port tree so that using the port version of keybase syncs well with other services. Notably, using 5.8.1 causes issues when interacting with the tools for supporting pgp/gpg keys. For example:
If the only supported channel for keybase is directly grabbing the dmg, that's fine, but (imo) the macports package should be marked depricated/removed.