ravenac95 / sudolikeaboss Goto Github PK

1Password 6: Version 6.3.BETA-3 (630003)

I'm so used to sudolikeaboss transparently working that I was certain I had some kind of weird Open Directory issue until I realised that it was just that the 1password popup wasn't appearing.

Looks like Agile are beefing up the protocol in the latest betas.

I get the following in system.log:

Apr  7 14:50:30 red 2BUA8C4S2C.com.agilebits.onepassword4-helper[545]: 630003 [EXT:(Secondary Thread 0x7f9bc6093ed0):<OP4ExtensionHTTPConnection: 0x7f9bc6151cb0>] M webSocketForURI: | [ES4] Extension connected Chrome-Extension 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk / (null)'
Apr  7 14:50:30 red 2BUA8C4S2C.com.agilebits.onepassword4-helper[545]: 630003 [EXT:(Secondary Thread 0x7f9bc149a5a0):<OP4ExtensionClient: 0x7f9bc6026e70>] S didOpen | [ES4 0x7f9bc6026e70] Connected 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:51119'
Apr  7 14:50:30 red 2BUA8C4S2C.com.agilebits.onepassword4-helper[545]: 630003 [EXT:(Secondary Thread 0x7f9bc6093ed0):<OP4ExtensionClient: 0x7f9bc6026e70>] E findExtensionProcessForPort: | Failed to find extension process for 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:51119', my PID: 545, invalid output: '545
    23918
    ', apps found: (
    )
Apr  7 14:50:30 red 2BUA8C4S2C.com.agilebits.onepassword4-helper[545]: 630003 [EXT:(Secondary Thread 0x7f9bc6093ed0):<OP4ExtensionClient: 0x7f9bc6026e70>] E findExtensionProcessForPort: | Stopping connection since no PID was found to validate the other side of the connection.
Apr  7 14:50:30 red 2BUA8C4S2C.com.agilebits.onepassword4-helper[545]: 630003 [EXT:(Secondary Thread 0x7f9bc6093ed0):<OP4ExtensionClient: 0x7f9bc6026e70>] S findExtensionProcessForPort: | [ES4 0x7f9bc6026e70] Connected chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:51119: (null) launched (null)
Apr  7 14:50:30 red 2BUA8C4S2C.com.agilebits.onepassword4-helper[545]: 630003 [EXT:(Secondary Thread 0x7f9bc1775f50):<OP4ExtensionClient: 0x7f9bc6026e70>] S didClose | [ES 0x7f9bc6026e70] Disconnected 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk' ((null))

sudolikeaboss no longer works for me.

I've recently upgraded iTerm2 to 3.0 and 1Password to 6.3.1.

This is from the 1Password helper log:

08/06/16 10:56:46,929 2BUA8C4S2C.com.agilebits.onepassword4-helper[2524]: 631006 [EXT:(Secondary Thread 0x7ff77ee25160):<OP4ExtensionHTTPConnection: 0x7ff77ee8c940>] M webSocketForURI: | [ES4] Extension connected Chrome-Extension 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk / (null)'

08/06/16 10:56:47,008 2BUA8C4S2C.com.agilebits.onepassword4-helper[2524]: 631006 [EXT:(Secondary Thread 0x7ff77ee25160):<OP4ExtensionClient: 0x7ff77eea3190>] E findExtensionProcessForPort: | Failed to find extension process for 'chrome-extension://aomjjhallfgjeglblehebfpbcfeobpgk:63185', my PID: 2524, invalid output: '2524 27055 ', apps found: ( )

08/06/16 10:56:47,008 2BUA8C4S2C.com.agilebits.onepassword4-helper[2524]: 631006 [EXT:(Secondary Thread 0x7ff77ee25160):<OP4ExtensionClient: 0x7ff77eea3190>] E findExtensionProcessForPort: | Stopping connection since no PID was found to validate the other side of the connection.

It'd be great if I could autofill passwords from Server records in 1password. Right now it looks like only Login records are supported.

Pressing the shortcut displays a dialog requiring the user to update the browser extension.

Updating the extension in Firefox, Safari and Chrome did not solve the problem.

Using 1Password

6.5.2

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.

I installed the workaround, following your instructions. But even when I configure the logins to "sudolikeaboss://local", ssh into a mashine and try to use the fill function from 1pw, it won't get copied in my clipboard, or entered into iTerm 2 correctly.
Like it just issues and empty iTerm command.

Is there any solution for this?

edit: I just noticed that it only does not work for "passwords". It work's for items marked as "login". Any idea what causes this?

I've been beta testing 1P 6.5 and on sudolikeaboss Coprocess from iTerm it requests and update on the browser extension.

I have raised this issue on the agilebits forums and they've asked me to create a bug report so they can provide you with additional documentation to keep this working.

Cheers

getPasswordFromResponse seems to be dead code.

Is this expected to work with 1password 3?

Please could you create binaries for release 0.2.1 as the links still point to 0.2.0 files. Thanks.

I get the following error when trying to choose a password to fill from 1Password, hot-key'd from iTerm2 and co-processed with sudolikeaboss:

"Failed to launch browser for the url: sudolikeaboss://local"

The URL for the password is set to sudolikeaboss://local and the 1Password Mini pops up when I hit the hot key, but I get that error every time. Is there some type of URI handler that needs to be installed, or I suppose sudolikeaboss should get passed that from 1Password right?

What am I doing wrong here?

sudolikeaboss was working great for me for a while but it seemed to break recently. Can anyone confirm whether 1Password 6.3.1 is supported and working? I figure it may be possible that 1Password 6 changed something in their API that blocked off using this tool.

I'm on:
1Password 6.3.1 (latest)
iTerm 2 3.0.0 (latest)
Mac OS X 10.11.5 (El Capitan)

Now it prints "password\n", but that "\n" not always needed

KeePassX is open source so easier to integrate :)

Since AgileBits fixed the browser signature verification bug in v5 .1.BETA-1, I was able to work around the issue by:

1. Turning on "Beta updates" in 1Password
2. Updating 1Password (updated to 5.4.BETA-13)
3. Turning off "Verify browser code signature"
4. Using sudolikaboss like a boss, without installing a proxy solution.

Thought you'd want to know.

Is it possible to parse a piece of the terminal (last line for instance) to determine which account to load? And is it possible to chat the password directly from 1pw into the terminal?

For instance I sometimes SSH into a remote server and want to do a git pull one of my private Github repos. I would like to:

me@myserver:~/folder$ git pull
Username for 'https://github.com':

And then hit cmd-\ and then have it show my Github web entry. Then when I choose it that it first enters the username and then the password, preferably depending on what the terminal asks.

Maybe in the beginning this could simply be depending on a few chat script like fields inside the different accounts. For instance by setting 'match_login' as 'git pull', 'match_user' as' Username for 'https://github.com':', etc.. Then it could chat with the terminal directly after I hit cmd-\ and choose the account that I want to use?

OS X 10.10 and 1Password 5.0.1.

Running sudolikeaboss displays the 1Password Mini window, but when I select an item it displays this error message:

Cannot Fill Item in Web Browser
Web Browser is connected but its code signature could not be verified. Filling and other features are disabled until this configuration issue is resolved.

At first I thought maybe I could disable "Verify browser code signature" in the 1Password Preferences. But it didn't make any difference.

So basically whenever I pressed my shortcut once in iTerm2, it won't stop reopening every couple of seconds. Also the coprocess icon in the top right corner of my iTerm2 won't disappear. I'm using OSX El Capitan. The window of 1password keeps appearing.

Starting having an issue today where sudolikeaboss started taking a long time (20-30 seconds) before showing the 1Password window. Running it from the command line issues no errors, but sometimes fails to display the 1Password window at all and exits with error code 1.

Not really sure where to start debugging on this.

Mac OS X 10.12.3
sudolikeaboss 0.3.0-beta1
1Password 6.6.2

With "Broadcast Input" (a feature I've learned to love in this cold and desolate, post-csshx world) is enabled, a password collected by sudolikaboss is only sent to the first pane.

Repo:

1. open a new iTerm2 window
2. open a second pane (command+shift+d)
3. activate broadcasting input (command+option+i)
4. activate sudolikaboss, select password, and hit enter

The password in (cleartext) is only pasted into the first pane.

https://github.com/ravenac95/sudolikeaboss/blob/master/README.rst

The readme says to install 0.1 (if by source) but the workaround didn't work until I uninstalled and re-installed via homebrew and noticed 0.2 was installed instead.

Thanks for this project! It saves me so much time.

I've noticed that it can take quite a long time between releases. I completely understand why, and I'm offering my assistance. At the very minimum, I'd love to help get a version released to homebrew that works out-of-the-box with the latest versions of 1Password.

How best can I assist you?

In README.md, you mention:

linux support? This is a big question mark. If I can get tmux support to work, then presumably doing something similar for linux wouldn't be impossible. However, the other hard part of this is that linux doesn't currently have a GUI for 1password, but I actually have plans to attempt to create a gui using some already built tools

It appears that someone has created a minimal 1password GUI for linux as seen here, and here is how someone was able to get it up and running.

It's been a year since last update of this project, I can't use this awesome software with iTerm2, since 1Password team didn't give me any document on developing iTerm2 extension to communicate with 1Password mini. I can't bear it anymore today, and decided to hack 1Password a little to get the job done.

as u can see, it works with the latest 1Password 6.8.9, but it's really dirty right now... since 1Password force to check signature of browser, I have to inject a dynamic lib into it, to get developer mode on...

Sadly, I don't think it properly to make pull request with sudolikeaboss, the way I achieved to get the job done is to make sudolikeaboss act like Safari browser, which is totally forbidden by 1Password team... I'll make a gist for anyone who interest with this functionality, and thank @ravenac95 for bring us such wonderful software, I love it.

When trying to run sudolikeaboss I get a popup saying

Update the 1Password extension
The 1Password extension requires an update to continue working in sudolikeaboss. To update later, visit 1pw.ca/browser

No passwords filled, no other dialogs shown.

Clicking "Update now" takes me to the browser extension page, which surely does not affect further functioning.

This is reproduced with sudolikeaboss ver. 0.2.1 and 1Password ver. 6.5.2 on macOS Sierra.

First of all thank you SO much for the work you've done so far on sudolikeaboss - it's a truly indispensable tool for me. Given that you seem busy would it be possible to push your code for 0.3.0-beta1 so I and others in the community can update it for the new impending release of 1password?

Dude, you've saved me so much time. How can I donate?

If you try to do:

$ tmux -CC
$ ssh some-address
... after logged in ...
$ sudo -s

For some reason the coprocess doesn't correctly output the data into the tmux session.

Steps to reproduce:

• Add new item in 1p
• Select "password" category (not "login" category)
• Give any random name, and random password
• Set website to sudolikeaboss://local
• Save
• Try to fill in iterm with sudolikeaboss

Expected: Fills the password, followed by <enter>
Actual: No password is filled, followed by <enter>, making it seem as though a password has been filled

To show there isn't anything wrong with the actual item, click the convert to login button in 1p. The password can now be filled as expected.

If this is 1p being strange with security requirements, that's fine but sudolikeaboss should probably throw up some kind of an error if at all possible. If you don't know that this happens, it can be an issue when setting passwords, because you may accidentally set them to nothing (eg an SSH key passphrase is very difficult to distinguish between no password, and a password)