sudolikeaboss: "1Password can't save or fill in sudolikeaboss."
After doing a round of updating on my dev system recently I’m seeing this when trying to invoke sudolikeaboss:
I’ve done cleanup around slab by removing, reinstalling 0.21 from brew, and also dropping in the binary from sudolikeaboss_0.3.0-beta1_darwin_amd64.zip in issue #29.
No dice. Same behavior every time I trigger slab via hotkey.
OS version: 10.12.6
Chrome version: 59.0.3071.115
iTerm2 version: 3.1.beta.5
1Password version: 6.8 (680015) from AgileBits store
1Password Chrome extension version: 4.6.7.90
The environment’s pretty clean and I’ve got sudo to change things if needed. The only real contender for active interference would be the presence of Sophos Central Endpoint (v9.6.3, engine 3.68.0, threat data 5.41) antivirus but its logs are clean of any indications of interference. Normally the real-time monitoring gets quite verbose when it decides to get all up in my grill.
About this issue
- Original URL
- State: open
- Created 7 years ago
- Comments: 45
☝️ Ditto. Instructions here https://github.com/ravenac95/sudolikeaboss/issues/29#issuecomment-278988719 also do not resolve this on 6.8.1 with iTerm 3.0.15 and sudolikeaboss 0.3.0-beta1.
If you unwittingly upgraded to 6.8.1 (like me), downgrading to 6.8 can be done by installing the pkg at this link. The download path is intuitive. Just get the download URL from the official page and change the pkg version to the one you desire.
Looks like an update was released today to the 1Password app (6.8.1) that completely breaks slab. The checkbox for code signing has been completely removed.
I can confirm this behavior as well. slab works fine as long as the main 1Password app is unlocked. Once the lock times out, slab shows the error instead of 1Password mini unlock screen.
I’ve already run the registration process.
I think this started with 1Password 6.8.
$ sudolikeaboss -v sudolikeaboss version 0.3.0-beta1
That is a big “just.”
My experience has been that the dialog pops up if 1P is locked at the time sudolikeaboss is run.
Ben from AgileBits here. We’ve posted a response for this request on our discussion forums:
https://discussions.agilebits.com/discussion/comment/394873/#Comment_394873
@ravenac95 I would suggest that this issue be reopened, or I can create a similar one if preferred. The issue is still present in 0.2.1 and 0.3.0-beta1, but only when 1Password is locked. Prior to 1Password 6.8, the 1Password Mini unlock screen was correctly presented in this case.
@squarecandy From what I read, the thing I’m trying to solve, and in theory slab solved, actually fits the scenario that @brenty was suggesting in that post. I personally do not use local vaults. I’m using the online ones. I’m looking at a solution that effectively implements what the chrome extension does, only in a terminal window.
Something that registers securely with the local application, and then uses the approved methods of communication to get the proper password using the 1Password popups to inject them into the terminal.
To say that is not a viable implementation seems like it is in conflict to the existence of the Chrome/FireFox plugins. It seems to me that as long as it functions in an approved way, and they can ultimately control the code for it, it should fall into the same category.
I can completely understand AgileBits being uncomfortable with the idea of a tool like this being out there that they don’t ultimately control. Because it could, potentially, contain malicious code that could compromise the integrity of your password vault. But if they owned and controlled the code, that seems to mitigate the issue.
Hi Everyone. I’ve written a replacement for sudolikeaboss that should work with 1Password > 6.8.0, by talking directly to the SQLite data file It’s not ideal, as then I require your Master Password, and that’s not the best move security wise, but in light of the recent decisions by 1Password, I do not see many other choices. Luckily everything stays local so that’s a win.
Code repo here: https://github.com/peacetara/slab and the current python implementation and instructions are here: https://github.com/peacetara/slab/blob/master/src/python/README.md
FYI I fixed this issue when you are using 1Password 6.8 (not 6.8.1 😭 ). The fix is available in my fork version 0.3.1.
It is fixable, but it needs someone with the appropriate skillsets (golang, reasonable familiarity with protocol implementation, some crypto) and more importantly some available time to do the work.
What needs doing is a re-implementation of the communications channel back to 1Password, which has previously used Websockets (which 1Password has deprecated as of 6.8.1) to use Chrome Native Messaging.
The guys at 1Password - the contact appears to be @rudyrichter - have some documentation available for this - see comments within issue #29 .
It looks like @brycekahle has some work in place at https://github.com/brycekahle/sudolikeaboss but I do not think he has (started) integrating the Native Messaging support, so that code works with 1Password 6.8.0 as its latest release, and will fail with 6.8.1 onwards.
As ever the problem is that these things are done in people’s spare time - and for example I am going to be very short of available time until the new year (and I am an absolutely newbie at golang).
Ahh, did another remove/reinstall cycle and this time
sudolikeboss registerdid what it should do. Everything’s working again. 😃It looks like https://github.com/ravenac95/sudolikeaboss/issues/29#issuecomment-278988719 from @squarecandy has like the most concise rundown on how to get it done quickly.Hope this helps anyone else who runs into this in the future.edit: Still a problem. See below. 😦I wish I had more time to dive into the items brought up in #41 and elsewhere. But like Ravenac95, I’ve been busy. life is hard. 🤷♂️
Speaking of @ravenac95 - thanks immensely for this little utility. Its at the core of most of my workflows, fun and otherwise, and its saved me innumerable hassles over the last few years.